Migrating from Marzban to Remnawave
We move your service from Marzban to Remnawave with a plan, a list of affected users and a rollback path. The service is rolling out with our first clients.
Who it's for
Marzban-based services that want a bot or feature from the Remnawave ecosystem and can't afford to lose paying users on switch day.
What you get
- A list of affected users before we start. Most users keep their subscription link. It changes for users on connections the official migration tool doesn't carry over (VMess) and for usernames the new panel doesn't accept.
- A message for your users: what changes, what they need to do, and where to get help.
- Nodes switched one at a time, with a rollback agreed in advance.
- Follow-up after the switch: we work through the list of users who haven't reconnected.
How the work is done
Remnawave ships an official migration tool for Marzban. We use it as one step: before it comes a full inventory of your service, and after it a check of every affected user. What to look at before the move is laid out in the Marzban migration checklist.
We give you a timeline after the audit.
3x-ui
Moving off 3x-ui is something we discuss case by case after the audit.