Migrating from Pterodactyl, TCAdmin or Multicraft

Moving to a new control panel is the kind of project most hosts put off indefinitely — usually because it means moving the files. GameDash is designed to avoid that wherever it can: it coexists with the infrastructure you are already running.
What carries over
- Instance configuration and startup parameters
- Player-facing files and world data, left exactly where they already sit
- Network and port allocations
What that means per panel
Multicraft servers stay at their existing paths: an instance carries a directory override, so hundreds of gigabytes never move. Pterodactyl is a runtime integration rather than a one-way import — GameDash speaks the panel and egg protocol, so it can manage the nodes you already have. TCAdmin is supported as a game-configuration source, with its XML exports converted into service modules.
What none of them do is move your customers for you. Accounts, billing records and access levels are rebuilt rather than imported. We would rather tell you that here than in a support ticket.
A migration nobody notices is a migration done right.
Building GameDash at Schokker IT — the game server control panel we always wished existed. Writes about infrastructure automation, the SDK and running game servers at scale.