Move your sites to a new server

Outgrowing your current box, or switching providers? The goal is a clean move with no lost data and minimal downtime. The trick is to set up the new server fully before you touch DNS.

1. Stand up the new server

Install OrbixPanel on the new box (same supported OS). Don’t point any domains at it yet.

2. Move each site’s files + database

For every site:

• Files — copy the site folder to the new server (zip + upload/extract, or rsync/scp over SSH).
• Database — dump on the old, restore on the new.
• Recreate the website entry, database + user, and update the app’s DB credentials.

If you keep encrypted offsite backups, restoring them onto the new box is the fastest path.

3. Recreate email, cron, and config

Set up mailboxes, DKIM/SPF/DMARC, and cron jobs on the new server.

4. Test before cutover

Test each site against the new server without changing public DNS:

• Edit your local hosts file to map the domain to the new IP, or
• Use a temporary subdomain pointed at the new server.

Fix anything broken now, while the old site still serves real visitors.

5. Cut over DNS (the low-downtime part)

1. A day ahead, lower each record’s TTL (e.g. to 300s) on the old DNS.
2. At cutover, repoint the A/MX records to the new server.
3. Request fresh SSL on the new box.
4. Because TTL is low, visitors move over within minutes.

6. Keep the old server briefly

Leave the old server running for a few days to catch stragglers (slow DNS caches, late email). Confirm the new server is handling everything, then decommission.

---

Running OrbixPanel? Encrypted backups make server moves a restore, not a rebuild. OrbixPanel.com → — the free, self-hosted, AI-powered hosting control panel.