HEXACRAFT / MIGRATION PLANNER
Bring your world.
Keep your progress.
Build a clear migration checklist and a support request before moving files. Stop the source server, keep a backup and test before switching players over.
Plan the move
Your answers stay in this page. No passwords, API keys, SFTP credentials or private logs are needed. A support request is only sent when you submit it in billing.
Your migration checklist
Sign in to billing, paste the request and submit the ticket. Migration scope, timing and any charges must be confirmed by support; this form does not schedule a transfer.
A careful Minecraft transfer
- Inventory: record the software build, Java requirement, world folders, plugins/mods, configuration and database dependencies.
- Stop and back up: shut down the source cleanly. Keep a separate copy before touching the destination.
- Transfer with SFTP: use the exact host, port and username shown by your server panel. Do not assume the port is 22. Never publish the credentials.
- Check compatibility: confirm the startup settings, Java version, file permissions and database configuration. Do not copy a provider-specific startup script without reviewing it.
- Test: join privately, inspect logs and test player data, plugins and permissions. Keep the source backup until the new service is verified.