Migration
The migration center (Admin → Migration) imports servers from other panels with tracked jobs: test first, run, then pause, resume, retry, or cancel per step.
Process
Section titled “Process”- Inventory the source. List every server, its game, disk use, databases, and custom config. Note anything exotic (custom images, sidecars) — those need manual handling.
- Prepare Catalyst. Nodes with enough free capacity, matching templates (import eggs first — importing eggs), allocations, and raised limits for the migration window.
- Test the connection from the migration center before starting anything.
- Migrate one pilot server. Full cycle: import → install → start → join → backup. Fix the template from what you learn.
- Migrate in batches, biggest risk first, during low-traffic windows.
- Verify each batch with owners before moving on.
Per-server checklist
Section titled “Per-server checklist”- Files and worlds intact (compare sizes and spot-check).
- Databases moved and plugins connecting.
- Startup variables and schedules recreated (tasks).
- Backups running on the new side before DNS/addresses switch.
- Old server kept (stopped) until the owner confirms — the rollback is “turn the old one back on”.
Migration jobs expose step-level status with retry — a failed step does not mean a failed migration. Work the steps, do not restart blindly.