# Move your Minecraft server from Nodecraft

> Get your world and plugins out of Nodecraft, import them here in one step, and switch the address without losing players.

Source: https://fadehost.com/docs/move-from-nodecraft/

Moving is three steps: get the files out of Nodecraft, put them here with the importer, point your players at the new address. Your world, plugins or mods and configs come along; nothing is retyped.

## 1. Get the files out of Nodecraft

Nodecraft's NodePanel keeps FTP switched off until you ask for it: open the instance's **Overview** page and click **Enable FTP**, and the host, port, username and password appear for the importer. The connection is FTPS with a self-signed or Cloudflare certificate, so a desktop client warns you once. Nodecraft has you stop the server before taking the world, then download the world folder from **Server Files**, **Files**, zipping it first if the panel asks; check `level-name` in `server.properties` for its real name and take `DIM-1` and `DIM1` with it. A plan runs one instance at a time, so if the server you are moving has been archived, deploy it again before the import.

## 2. Bring them here

1. Create the server on FadeHost with the same software and Minecraft version as the old one. Do not start it yet.
2. **More for this server**, **Import from another host** (also under **Settings**, **Import**).
3. Choose SFTP or FTP and enter the old host's details, or upload the zip you downloaded. Pick what to pull: the world, plugins or mods, configs.
4. Start the server and read the console. A plugin that stored the old address or an absolute path needs a config edit.

## 3. Switch the address

Players take the new address from the server page, or from the join page you share. A custom domain moves by changing its SRV record, or by connecting the domain in **Settings**, **General**, **Your own domain**. Keep Nodecraft for a day while people switch, then cancel it from your subscription controls; a payment reminder arrives seven days before autopay. Do not press **Destroy** to end things, because that deletes the instance and everything connected to it, backups included.

## What is different here

- A second server for a different game is another slot in the same RAM pool, not a swap and not a second plan.
- A server you are not using can sleep instead of being archived: it stops when empty and the next join wakes it. See [Server hibernation](/docs/hibernation/).
- Backups are automatic and restores, clones and per-file downloads are one click.

See also [Move from another host](/docs/move-from-another-host/) for the general steps and databases.