Importing Existing Servers

← All guides · GET STARTED

---

Use Add Server → Import Existing Server when you already have a supported dedicated-server installation.

Importing registers that installation. It is different from installing into a new folder and different from importing a whole Synix transfer package.

Before importing

• Make a backup of the existing server and any saves stored outside its folder.
• Stop it through its current manager and disable competing scheduled launchers while testing.
• Locate the actual server installation root, not a shortcut, downloaded archive, or ordinary game-client folder.
• Record its game version, ports, loader, custom launch arguments, and required credentials.

Import workflow

1. Choose the existing server folder.
2. Let Synix inspect it for supported executables.
3. Select or confirm the matching profile and edition.
4. Give the entry a unique name and review the detected settings.
5. Finish importing, open Configure, and check anything that was not detected. Complete the current step 3 Review before saving any setup changes.
6. Open Readiness, then perform a controlled first launch through Synix.
7. Confirm the expected world/session, players' connection details, and backups.

Importing is designed to leave the installation in place without reinstalling or overwriting its configuration. Detection is not guaranteed to understand every custom wrapper, modpack, argument, password, or external save path. Later explicit configuration, repair, update, or restore actions can change files.

Synix rejects registering the same installation folder twice. If it is already listed, use that existing entry.

Minecraft

Choose the correct Java/Bedrock edition and, for Java, the existing loader and compatible versions. Back up before changing a modpack or switching loader families. See Minecraft Server Guide.

When detection fails

Check the installation root and executable named by the selected profile. Do not rename an unrelated binary just to satisfy detection, and do not run an arbitrary downloaded script to make the import pass.

If the installation is a customized layout that Synix does not support, report the game, layout, and redacted startup requirements through GitHub Issues.

Configuration and add-ons after import

Import does not prove that every shared field or add-on was identified. Use the Configuration Editor to review/save mapped common settings, and Mod & Plugin Manager to inspect supported installed content.

Previously installed files do not automatically acquire a Synix rollback record. Keep the original backup before applying a new runtime, pack, or configuration repair.

Moving an entire Synix setup

Use Settings → Backups and the transfer workflow for a Synix package. A folder import does not transfer all app settings or Windows-protected credentials.