Move an existing server to uniz.host — bring the whole world with you
Last updated November 13, 2026
The order that works is: create the new server to match the old one (same game, same version, same server type), then **stop it completely**, bring the world in, and only then start it. A whole Minecraft world goes through the Worlds page as one .zip; other games and folders the Worlds page does not cover go through the Files tab. Never upload over a running server — the game holds its files in memory and writes them back over yours when it shuts down. Bring the world folder from the old server, with its Nether and End folders if they sit beside it, plus the config and player-list files if you want those preserved, and if the old server ran mods you must install the same mods at the same versions before it will boot. Uploads are capped by the new server's storage and require the account owner to have made at least one real top-up.
- Create the new server to match the old one
- Stop the new server before touching any files
- Upload the world folder
- Start it and watch the console from the first line
On this page · 6 sections
If you already run a server — on a PC at home or rented somewhere else — there is no reason to start a new world. A world folder is ordinary files, and a server on uniz.host will take yours directly. The whole job comes down to order. Get the order wrong and your upload vanishes silently, with nothing on screen to warn you.
First: collect everything from the old server
Go to the old server, shut it down, and only then copy the files out. Copying a world folder while the server is running risks half-written files that will not open.
What to take:
| Bring | Leave behind |
|---|---|
the entire world folder, plus any folders next to it with the same name ending in _nether and _the_end | the game's own program files, including anything installed by Steam |
| the game's config file | the logs folder |
| player-list files — whitelist, operators, bans | temporary and cache files |
| a note of your mods and their versions | anything belonging to the old operating system |
Write down two things in particular, because you need them to match: the game version and the server type the old one was running.
The migration
Create the new server to match the old one
Create a server as normal, matching three things:
- Same game — self-evident
- Same version — match it or go newer; a world from a newer version cannot open on an older one
- Same server type — a world built on a modded server needs the same kind of server to open at all
If the old server ran mods, install the same mod set and confirm the server boots with an empty world before you bring the world across. It looks like a detour and it saves time: bring both at once and a failure leaves you unable to tell whether the mods or the world caused it.
Stop the new server before touching any files
Press "Stop" on the Overview tab and wait for the badge to settle on stopped.
This is the step people skip and then lose a day to. A running game holds world data in memory and writes its own files back out when it shuts down. Upload a world into a running server and, the moment it stops, it overwrites what you put there — with no error anywhere. What you experience is "the upload succeeded but the world did not change".
A stopped server still opens the Files tab normally; the first load may take ten to thirty seconds.
Upload the world folder
A whole Minecraft world goes through the "Worlds" page, a sub-tab of the "Content" tab. Zip the world folder, one .zip per world, because a zip holding more than one world is refused. On the "Worlds" page, press "Choose a file" under "Upload your own file", fill in the "World name" field, and press "Upload". The name world is refused, because the server keeps that folder for itself, and the field says why, so a world called world at home needs a new name here. Keep the page open while the file goes up. After that the copy onto the server runs without the page. When its row becomes a world, switch to it, and the switch applies on the next start.
Check the folders next to your world. If there are folders with its name ending in _nether and _the_end, put them in the same zip, or the Nether and End start empty and nothing tells you. If there are none, there is nothing extra to add: recent Paper, for one, keeps both inside the world folder. The exception is a Vanilla, Fabric, Quilt, Forge, NeoForge or modpack server, which refuses a zip holding those extra folders.
Config and player-list files still go through the Files tab, at the top folder.
For other games, and folders the Worlds page does not cover, open the "Files" tab and look at the structure that is already there. Your job is to put your world folder in the same place the new server keeps its own. Match what you can see; do not guess.
- Minecraft without a Worlds page — the world folder sits at the top folder, alongside
server.propertiesand the player-list files - Palworld — do not add a second world folder. The server makes its own the first time it boots and keeps loading that one, so let the first boot finish before you stop it; if you stopped it sooner, start it again and let it finish. Then open
Pal/Saved/SaveGames/0/and go into the folder with the long id that is already there. Delete itsPlayersfolder first, or the old player files linger beside yours. Send yourLevel.savandLevelMeta.savwith "Upload files", and yourPlayersfolder with "Upload folder". Do not uploadWorldOption.sav: it would override the Settings tab, so the server sets it aside at boot anyway, and the old values belong in that tab instead. Do not uploadLocalData.savor thebackupfolder either: they belong to the game on a player's machine, and the server does not use them - Other Steam-installed games — your data is usually under a server-data folder kept separate from the game's program files
Navigate to the destination folder before pressing "Upload folder", because everything lands in the folder you currently have open, and the folder you pick becomes the first folder at the destination.
A counter shows progress while it runs, with a "Stop" button beside it. A file that fails does not stop the batch: it is listed with its reason at the end, and you can retry the failed ones. The batch stops by itself only when every file would get the same answer, or after 3 files in a row fail because the server did not answer or broke while handling them. Everything already uploaded stays. You can switch to another tab of the dashboard while it runs, but closing or reloading the page ends it.
A single file through the web page has a ceiling of about 100 MB, because the page passes through Cloudflare, and we measured its limit at 100 MiB (about 105 MB) on 2026-11-06. SFTP does not pass through Cloudflare, so use it for a bigger file. For a large folder, one route is to zip it, send the .zip over SFTP, and press "Extract here" on it in the Files tab. Extraction runs on the server, it is limited by the free storage left, and it asks before replacing existing files. Wait for it to finish before you start the server, because starting ends the job.
Two conditions cause most failed uploads: the file must not exceed the new server's storage, and the account owner must have made at least one real top-up. Coupon and referral credit do not count. The top-up condition applies on the Worlds page too.
Start it and watch the console from the first line
Press "Start" and leave the Console tab open. The first boot after a migration is the one most worth watching.
- If it comes online, join and go stand where your base was, to confirm you got the right world rather than a new one that looks similar. On Minecraft, also go through a portal, because a Nether or End left out of the zip starts empty with no warning
- If it boots and dies, read the server won't start guide. The number one cause after a migration is a missing mod or a version mismatch
The other route: if you already have one of our files
The Restore points tab also has an Import file button, but it accepts only the format our own system produces — .tar.zst. Anything else is rejected outright.
That makes it genuinely useful in two cases: you downloaded a file or an old backup from here earlier, or you are moving between two servers within uniz.host. The second is very clean — export a file from a restore point on the old server and download it, import it on the new one, and restore from it within its 3 days.
For a world coming from anywhere else, use the Worlds page for Minecraft, or the Files route above.
Per-game traps
Minecraft — the most straightforward. Watch two things only: the server type has to support the same mods or plugins, and if the old world came from a newer version you must create the server on that version or newer.
Palworld — the world and everything built in it moves, but if the save came from a self-hosted co-op game, player characters usually do not reattach, because the player identifiers recorded there are a different set from the ones a dedicated server uses. The map and bases are intact while everyone has to create a character again. If that happens, contact support. Do not use the identifier-conversion formulas found online; several of them produce the wrong value and leave the save worse off.
Every Steam-installed game — do not upload the game's own files over the new server's. It installed its own; add only your data.
After the move
Two things to do immediately:
- Take one restore point while everything is known good, so you have a way back you trust
- Send players the new address. The old server's address has nothing to do with this one, and if you have your own domain that pointed at the old server, repoint it
And do not delete the old copy until you have confirmed everything works.
Read next
- Server file manager — the upload rules and every limit in detail
- Server won't start — if the first boot after the move fails
- Restore points — moving within uniz.host as a single file
- Create a server — building the new server to match the old one
Frequently asked questions
What do I need to bring from the old server?
At minimum the world folder, which holds the map and everything built on it, plus any folders next to it with the same name ending in `_nether` and `_the_end`, which hold that world's Nether and End. To make the new server truly identical, bring the config file and the player-list files too — whitelist, operators and bans. What you should not bring is the game's own program files or the logs; the new server has its own and uploading over them only breaks things.
Can I upload while the server is running, to save the downtime?
You can upload, but not world files. A running game holds world data in memory and writes it back over whatever you just put there when it shuts down, so your upload disappears with no error message at all. There is exactly one safe order — stop it fully, upload, then start.
Do the versions have to match exactly?
They must match or be newer. A world created by a newer version cannot be opened by an older one, and trying usually means the server will not boot or the world is damaged. The safe path is to create the new server on the same version as the old one, get it running, and treat upgrading as a separate step afterwards.
My old server had a lot of mods. How does that move?
The mod set and their versions have to match on both sides or the server boots and dies immediately. Set the new server to the same mod-capable type, install the same mods, and confirm it boots with an empty world first. Then stop it and put the world in. Doing both at once leaves you unable to tell whether the mods or the world broke it.
Can I bring a Palworld save from a game we hosted ourselves?
The world and everything built in it comes across, but player characters usually do not reattach, because a self-hosted save records a different set of player identifiers than a dedicated server uses. What you see is the map and bases intact while everyone has to create a character again. If that happens, contact support and say where the save came from — we have fixed this for customers before. Do not use the identifier-conversion formulas floating around online; several of them produce the wrong value.
My files are too big and the upload fails.
The ceiling is the new server's storage, so if the old world is larger you need a plan with enough storage first. A single file sent through the Files tab also has to stay under about 100 MB, because the web page passes through Cloudflare; use SFTP for anything larger, and the Worlds page for a whole Minecraft world. The other frequent cause is an upload that stops because the account owner has never made a real top-up, which is a condition of bringing world data in. Coupon and referral credit do not count.
Related guides
Would you rather skip all of this?
A server on uniz.host is up in minutes. You pay by the hour only while it is online, and the smallest top-up is ฿20.