Switching to Falix doesn't mean rebuilding from scratch. The Importer copies your files straight off your old host — worlds, plugins, configs, an entire bot project — over SFTP or FTP, and drops them onto this server. Open Importer from your server menu to run it.
| At a glance | |
|---|---|
| You need | A Falix server to import into, and your old host's file-access details (address, username, password) |
| First | Take a backup of this server if it already has anything on it |
| Time | Ten minutes, plus transfer time |
What you'll enter
The Importer connects to your old host as a file-transfer client and pulls everything across. Fill in:
| Field | What to enter |
|---|---|
| Protocol | SFTP (recommended) or FTP |
| Host | Your old host's address |
| Port | 22 for SFTP, 21 for FTP |
| Username and Password | Your old host's file login (not your Falix login) |
| Source directory | The folder on the old host to copy from — start at the file root so you get everything |
| Destination directory | Where the files land here (the server root is usually right) |
| Delete existing files before importing | Optional; clears the destination first for an exact copy. Leave off unless you want a clean slate — it's destructive |
🎯 Good to know: The Importer only connects to real, public hosts — localhost and private addresses are rejected.
What happens during import
The server stops while it imports, so nothing is being written underneath the copy. Large transfers take a few minutes. When it finishes, start the server again and check your files landed where you expected.
🎯 Good to know: The Importer only ever reads from your old host — it copies files off, it never changes or deletes anything there. So your old server stays exactly as it was, and a failed or half-finished import can always be retried without risk to the original.
Per-host notes
- Coming from another Minecraft host — copy everything: world folders,
plugins,server.properties, configs. The Importer moves files, not the server software, so afterward pick your software and version in the Version Changer — see Choose your Minecraft software and version. Your world and configs carry over. - Coming from another bot or app host — copy the whole project folder. Then set the Main file variable to your entry file in Settings so Falix knows what to run — the Node.js and Python guides show which entry file each application expects.
Troubleshooting
- "Authentication failed" / can't connect — the username or password is wrong, or the port doesn't match the protocol (22 for SFTP, 21 for FTP). Use your old host's file credentials, and confirm SFTP vs FTP with them.
- It connected but copied nothing (or the wrong things) — the source directory is off. Point it at the old host's file root so you capture everything, not an empty subfolder.
- Import finished but I don't see my files — check the destination directory you chose; the files are there, just not where you were looking. The File Manager opens at the server root.
- It won't accept the address — private and localhost addresses are blocked; you can only import from a real public host.
- The import failed or stopped partway through — no harm done. Your old host is untouched (the Importer only reads from it), and whatever landed here so far is just files. Fix whatever caused it — usually the credentials, the port, or the source path — and run the import again. If you'd rather start clean, restore the backup you took first, then retry.