Move an existing server to Foxcore

What migration is not

Foxcore has no importer that reads another panel’s backup, pulls a server over the network, or stages files in object storage. There is no one-click transfer and no migration SKU.

World-scale transfer is not available yet either. Files takes one file per upload and caps each file at 256 KB (262,144 bytes), with no folder upload, no SFTP, and no rsync. A world tree, a modpack, and most archives are far larger than that.

Inventory the old server

Write down the game and version, the loader and mod list, the world size, the player slots you actually use, and any custom ports. That inventory is what a future importer would need, and it tells you whether the move is a handful of small files or a whole world.

Match the old server to a Foxcore pack id and size. If the exact modpack is not a pack, the closest base pack is still the right choice — but neither pack choice uploads a world for you.

What you can move today

Create the instance in the region you want and use it for a new world or for files that are 256 KB or less. A config, a whitelist, or a small plugin can move; a populated world cannot.

Keep the old server running for the existing world. Do not cancel it on the strength of a create form, and do not destroy a Foxcore instance that holds the only copy of a world.

1. Inventory version, loader, mods, world size, and ports.
2. Create the closest Foxcore pack and size for a new server.
3. Check whether every file you need is 256 KB or less. A world is rarely that small.
4. Upload only those small files, one at a time, through Files.
5. Keep the old host for the world until a bulk transfer path exists.

VPS migrations

Public create does not offer VPS. A VPS guest is floki with libvirt, and that isolator cannot define a domain yet. Do not plan a VPS cutover on Foxcore until the panel sells and provisions one. A game pack migration is the path that exists today.