Migrating from Marzban: what to check before you start
Most migration problems are visible before you start. What to check yourself, even if a contractor does the move.
1. User inventory
- Total users, and how many are active, meaning they actually connect.
- Expiration dates and data caps: all of it needs to land in the new panel without manual fixes.
- Users on VMess: Remnawave's official migration tool doesn't carry their connections over.
- Users with several devices or shared accounts: the easiest ones to lose track of.
2. Subscription links
The key question: whose link will change. If the link stays the same, the user does nothing. If it changes, they have to get the new one and paste it into their app.
The usual reasons a link changes: VMess connections; usernames the new panel doesn't accept; a different subscription domain.
Your subscription domain is your most important asset. As long as you control it and point it at the new panel, links can be preserved.
Build the list ahead of time and count the people on it. That number tells you how many support requests to expect on switch day.
3. Bot and payments
- How is the bot connected to the panel: API, database, manual steps?
- What happens to a payment made on migration day?
- Will the bot work with the new panel, or does it need replacing too (for example, with Bedolaga)?
4. Nodes
- Which nodes move and which get retired.
- Switch order: one at a time, so most users stay connected throughout.
- Providers and subnets: a migration is a good moment to stop depending on a single supplier.
5. Rollback
Before you start, agree on what condition stops the switch and how to bring a node back. A rollback improvised mid-incident rarely works.
6. Message to users
Write it before the migration:
- what changes and when;
- what users need to do, if anything, in one step;
- where to get help if it doesn't work.
7. After the switch
- Compare active connections before and after.
- Follow up with users who haven't reconnected, using the list from step 2.
- Keep the old panel available read-only until you're sure everything made it across.
Want it done for you? See Marzban to Remnawave migration.