How to Migrate a Pterodactyl Node to New Hardware
Move all game servers from one Pterodactyl Wings node to another with minimal downtime by transferring files, configs, and database records.
When to Migrate a Pterodactyl Node
Hardware eventually ages out. Maybe you found a better deal, need more cores, or want to move closer to your players. Whatever the reason, you can migrate a Pterodactyl node without rebuilding every server from scratch. The process involves setting up Wings on the new machine, transferring server data, and updating the panel's database.
Preparation
- Provision the new server and install Docker, Wings, and any required runtimes.
- In the panel, create a new node entry pointing at the new machine's FQDN and configure its allocations.
- Verify the new node shows as connected (green indicator).
- Notify your players about the maintenance window.
Step 1: Stop All Servers on the Old Node
Shut down every server gracefully so world saves complete and no files are mid-write. You can do this from the panel or with a mass power action via the API.
Step 2: Transfer Server Files
The fastest method is rsync over SSH. From the old node:
rsync -avz --progress /srv/daemon-data/ root@new-node:/srv/daemon-data/This copies every server's files, including volumes. Depending on your data size and network speed, this can take minutes or hours. Compression (-z) helps on slower links.
Step 3: Update Server Records
You need to reassign each server to the new node in the panel database. Open Admin > Servers, edit each server, and change the Node and Allocation to match the new machine. For many servers, you can script this with the Pterodactyl API:
curl -X PATCH "https://panel.example.com/api/application/servers/SERVER_ID/build" -H "Authorization: Bearer API_KEY" -H "Content-Type: application/json" -d '{"allocation": NEW_ALLOC_ID}'Step 4: Fix Ownership
On the new node, make sure file ownership matches what Wings expects:
chown -R pterodactyl:pterodactyl /srv/daemon-data/*Step 5: Start and Verify
Start each server from the panel and verify that worlds load correctly, plugins initialize, and players can connect. Check the Wings log for permission or path errors.
DNS and IP Changes
If the new machine has a different IP, update your DNS records and any SRV records that players use to connect. Propagation can take up to 48 hours, so keep the old node reachable during that window.
After you migrate a Pterodactyl node successfully, decommission the old machine and remove its entry from the panel. For ongoing protection of your new setup, configure automated backups right away.
See a professionally hosted server: Astroworld MC, IP play.astroworldmc.com, Java + Bedrock.