Umiji

Bring your users over from another panel.

One menu option moves every user from Marzban, PasarGuard, Marzneshin, 3x-ui, Remnawave or Hiddify, with their traffic, limits and expiry dates. Their apps keep updating from the old links.

  • 6 panels
  • About 10 minutes
  • Nothing changes on the old panel
01
Five minutes

Before you start

The move reads the old panel through its API, the same way its own web page does. No database exports, nothing to copy by hand, and the old panel keeps running while you check everything.

What you need

  • Umiji's panel and sub page, installed with the setup guide. You don't need to set up anything else in it.
  • The old panel's address and admin login. For Remnawave, an API token instead. For Hiddify, the admin link it gave you.
  • The Umiji server can open that address. If the old panel only lets in certain IPs, add the Umiji server's.

What comes over

Every user, with their passwords and UUIDs, traffic used and limit, reset period, expiry date, status, note, Telegram ID and email. Users keep the same keys, so their connections don't change.

FromInboundsGroupsHostsOld links
MarzbanYesYesYesWith the secret
PasarGuardYesYesYesWith the secret
MarzneshinYesYesYesYes
3x-uiYesYesYesYes
RemnawaveYesYesYesYes
HiddifyNo, see whyNoNoYes

Inbounds land in a config profile named after the old panel. Groups (Marzban's inbound sets, PasarGuard's groups, Marzneshin's services) become internal squads, so each user can use what they could before.

What doesn't come over: the old panel's admins and resellers, and its servers. Users made by another admin keep Owner: name in their note, so you can find them. VMess and SOCKS inbounds stay behind, since Umiji doesn't run them; their users keep their other protocols.

02
On the old server · Marzban and PasarGuard only

Copy the secret

Marzban and PasarGuard sign every subscription link with a secret they keep in their database. Their API doesn't show it, so this is the one thing you copy by hand. With it, apps keep updating from the old links. Without it, everything else still moves, but you send each user their new link.

Log in to the old server and print it:

cd /opt/marzban && docker compose exec -T marzban python3 -c "import sqlite3;print(sqlite3.connect('/var/lib/marzban/db.sqlite3').execute('select secret_key from jwt').fetchone()[0])"
cd /opt/pasarguard && docker compose exec -T pasarguard python3 -c "import sqlite3;print(sqlite3.connect('/var/lib/pasarguard/db.sqlite3').execute('select secret_key from jwt').fetchone()[0])"

That's for the default database, SQLite. With MySQL, MariaDB or PostgreSQL, run SELECT secret_key FROM jwt; in it. The answer is a long line of letters and digits.

Keep the secret private. Anyone with it can make a working link for any user.

03
On the Umiji server

Run the move

  1. Log in to the Umiji server as root and run:
    bash <(curl -fsSL https://raw.githubusercontent.com/therewasluna/umiji/main/install.sh) migrate
    It always runs the newest version, and adds Migrate to the umiji menu for next time.
  2. Pick the old panel, then paste its address, like https://old.example.com:8000. For 3x-ui, include its secret path.
  3. Type its admin username and password. The password doesn't show while you type, and neither is saved anywhere.
  4. It reads the old panel and shows what it will make. Nothing is changed yet. Read the Worth knowing lines: they say what's different in Umiji, and for how many users.
  5. Press Enter to move them. It backs up the database first, updates the panel and sub page, then moves the users, six at a time.
  Which panel are the users on?
    1  Marzban
    4  3x-ui            2.x or 3.x
  …
  3x-ui at old.example.com
    Users        412 to move
                 398 active, 9 limited, 5 expired
    Profiles     3x-ui (3 inbounds)
    Squads       3x-ui, 3x-ui 2
    Hosts        3

  Move them now? [Y/n]
  [1/7] ✓ Database backed up 2s
  [5/7] ✓ Users moved 41s
  [6/7] ✓ Sub page knows the old links 9s

Safe to run again. Users who are already here are skipped, so after a failure, fix what it says and run it again. Users added to the old panel since then come over too. To undo everything, restore the backup it made: umiji, then Restore.

After the move, make changes in Umiji only. A second run skips users who are already here, so renewals, top-ups or disables made on the old panel afterwards don't come over.

05
Each old server

Move the servers

The users' keys came over, but their traffic still runs through the old panel's servers. Move each server when you're ready. Its users notice a short break, then they're on Umiji.

  1. Stop the old panel's node on that server, so its ports are free. With 3x-ui or Hiddify, that's the old panel itself.
  2. In Umiji, open Nodes and add it with Automatic install (the server's IP and SSH password), as in the setup guide. Pick the profile the move made.
  3. Check that the node shows online, then that one user can connect.

When every server is moved and the old domain points here, you can switch off the old panel. Keep its server for a few days in case you need to read something from it.

✓

Good to know, per panel

Marzban, PasarGuard
Users waiting for first use (on hold) start counting their days on the day of the move: Umiji has no such state. A yearly traffic reset becomes none. Reseller admins aren't made as brokers.
Marzneshin
Inbounds come from each node's Xray config, and services become squads. A user waiting for first use starts counting on the day of the move.
3x-ui
A client in several inbounds under one subscription ID becomes one user with all of them. Auto-renew and hourly traffic resets have no match in Umiji, so they're dropped, and the plan says for how many users. Version 2.x and 3.x both work.
Remnawave
Make the token in Remnawave under Remnawave Settings, API Tokens. Profiles, squads and hosts copy one to one. External squads don't, so users in one get the default subscription settings.
Hiddify
Hiddify's API doesn't give its inbounds, so first make a config profile and an internal squad in Umiji that match them. The move asks for the squad's name and puts every user in it. VLESS keeps the old UUID. Trojan and Shadowsocks get new passwords, since Hiddify's are longer than Umiji allows; the user's link brings the new ones.

Tested with Marzban, PasarGuard, Marzneshin and Remnawave as of November 2026, 3x-ui 2.6 and 3.11, and Hiddify 14.2. Something didn't come over right? See Common issues, or open an issue on GitHub with the plan it printed.