Help us design the Kannel ➡️ Sendium Migration Tool

[DimitriosPetrakis]

Hey everyone! As part of our mission to make Sendium the most seamless, high-performance open-source alternative to Kannel, we are building a tool to help you migrate legacy configurations over to Sendium's ecosystem (smsg.properties and credentials.yml).
Since Sendium is fully headless, we want to build a utility that fits perfectly into your workflow. We are deciding between a few different execution paths and would love your feedback on what you'd actually use:

Option 1️⃣: A Standalone CLI Transpiler
A terminal utility (e.g., a Go binary) where you run a command like sendium-migrate -f kannel.conf. It parses the file locally and spits out your mapped Sendium configuration files.
Best for: Running locally in the terminal, scriptability, and integration into existing DevOps or deployment pipelines.

Option 2️⃣: A Web-Based GitHub Page Converter (Pure Client-Side)
A simple, browser-based UI hosted right on GitHub Pages. You drop your kannel.conf text into the browser, and it instantly shows a side-by-side visual diff of your new Sendium files, complete with warning/error highlights for unsupported legacy Kannel parameters.
Best for: Visual clarity, zero installation, instant error debugging, and security (your data never leaves your browser).

Option 3️⃣: Other (Tell us your idea!)
Neither of these fit how your team manages infrastructure? Let us know what your ideal migration workflow looks like in the comments below!

👇 Which approach fits your workflow best?

Vote Option 1, 2, or 3 in the comments, and let us know if there are any specific configuration pain points you want this tool to solve!