Picked the wrong region when you created your server, or your players moved continents? You don't have to start over. Transferring moves your whole server — files, worlds, settings, everything — to a Falix node in a different location, so players get lower ping. It's a premium feature, and it comes with a short, planned downtime. You start it from the Settings page, under Operations.
| At a glance | |
|---|---|
| You need | A premium server |
| Plan | Premium only |
| Time | 5–10 minutes of downtime, run when it suits you |
What a transfer is
A transfer relocates your existing server to a node in another region. It's not a copy and it's not a reinstall — it's the same server, picked up and set down somewhere else. Falix archives your entire server directory, ships it to the target node, and switches your server over to it.
Regions you can transfer between include the US, Canada, Belgium (EU), France, Singapore, Australia, and Brazil. The page checks availability live, so a region that's currently full shows as unavailable — pick another or try later.
🎯 Good to know: Transfer is premium only. On a free server the option is there but locked behind an upgrade prompt. It's also rate-limited — you can't transfer again for a few minutes after one completes.
What comes with it, and what changes
Everything that makes the server yours travels with it:
| Travels with the server | Changes on arrival |
|---|---|
| All files and worlds | A new IP address and port |
| Player data and stats | DNS is repointed automatically |
| Server settings and variables | The server needs a start afterwards |
| Installed plugins and mods |
The one thing to plan around is the new address. Because the server lands on a different node, it gets a fresh IP and port. Falix handles the DNS for you — your Falix subdomains and verified custom domains (including the Minecraft SRV records) are rewritten to the new address automatically. So players who join by your subdomain notice nothing but better ping. Anyone using the raw IP:port, though, has an old address now — point them at your subdomain instead.
Your managed databases, sub-users, backups, and permissions all stay attached to the server — they aren't recreated, because it's the same server record simply living on a new node.
How it goes
- Open Settings → Operations → Transfer Server and pick a region.
- Confirm. The panel stops your server and begins the transfer.
- Wait — expect 5 to 10 minutes of downtime while your data ships across. It runs in the background; you don't have to sit on the page.
- When it's done, the server is on the new node with its new address and DNS already updated. Start it and you're live again.
💡 Tip: Take a backup before you transfer. Transfers are reliable, but a backup is cheap insurance before any big move, and it's good practice generally.
Should you transfer?
The deciding factor is where your players are. Ping is dominated by physical distance, so a server close to your community feels noticeably snappier. If most of your players are in Europe and your server is in Singapore, a transfer is worth the ten minutes. If your players are spread worldwide, pick the region nearest the most of them — there's no location that's fast for everyone at once.
If you only wanted a second server elsewhere rather than to move this one, that's a different tool — see Cloning a server.
Troubleshooting
- The transfer option is locked — it's premium; the server needs an active premium plan or subscription.
- My region isn't available — that node is full right now; the page shows availability live, so try another region or check back later.
- Players can't join after the transfer — if they used the old IP:port, it changed. Have them join by your subdomain instead, which was repointed for you. Then start the server if it isn't running.
- "Please wait before transferring again" — there's a short cooldown between transfers; give it a few minutes.