A migration is more than files
Moving a website means moving everything the site depends on. Missing one item is the usual reason a migrated site "works" but loses orders, images, or email.
| Item | Why it matters |
|---|---|
| Files | Application code, themes, plugins, and uploads |
| Database | Content, users, settings, orders, and form entries |
| Configuration | Database credentials, site URL, and environment values |
| DNS | Where the domain points and which records must be recreated |
| Mailboxes, forwarders, and MX/TXT records | |
| Cron and workers | Scheduled tasks that stop silently when moved |
| SSL | Certificates must exist on the new server |
| External integrations | Payment webhooks, APIs, and allowlists that reference the old IP |
Step 1: Prepare the destination
- Create the hosting account and confirm the domain is added in cPanel.
- Create the database and database user on the new account. Do not reuse the old credentials.
- Confirm the PHP version and required extensions match the old environment.
- Check disk space for files, database, and a temporary backup.
Do not change DNS yet. The old site should keep serving traffic while you prepare the new one.
Step 2: Back up the old site
Take a full backup before copying anything. If the migration fails, this is your rollback.
- Download the home directory and the database separately, or generate a full account backup.
- Store the backup off the server.
- Note the current DNS records, cron jobs, and PHP version.
Step 3: Copy files and database
- Upload the site files to the new document root, or extract the archive there.
- Import the database into the new database using phpMyAdmin or WP-CLI.
- Update the configuration file with the new database name, user, password, and host.
- Set file permissions:
644for files,755for directories.
Do not copy the old .htaccess blindly. It may contain server-specific rules or absolute paths that break the new environment.
Step 4: Handle WordPress URLs
WordPress stores the site URL in the database, and many values are serialized. A simple text search-and-replace can corrupt them.
- If the domain stays the same, usually no URL change is needed.
- If the domain changes, use a migration tool or WP-CLI's search-replace, which handles serialized data safely.
- Update
WP_HOMEandWP_SITEURLinwp-config.phponly if you intentionally hard-code them. - Check permalinks after the move and resave them if inner pages return 404.
Take a database backup before any search-replace. There is no undo.
Step 5: Test before DNS changes
Test the new server without moving the domain:
- Temporary URL: many hosts provide one. Some applications generate links based on the configured domain, so the site may look broken even when it works.
- Hosts file: map the domain to the new server IP on one computer. This tests the real domain without affecting anyone else.
- Direct IP with Host header: use
curl -I --resolvefor a quick check. - Check logs on the new server while browsing.
Test logins, forms, checkout, image uploads, and email sending, not only the home page.
Step 6: Switch DNS
- Lower the TTL on the records you will change, at least one TTL period before the switch.
- Change the A record or nameservers to the new server.
- Keep the old server running and unchanged.
- Record the switch time.
Do not cancel the old hosting on the same day. Keep it until the new site has been stable for several days.
Step 7: Verify after propagation
dig +short A example.comreturns the new IP.- The site loads over HTTPS with a valid certificate.
- Forms, logins, and checkout work.
- Email still sends and receives.
- Cron jobs and scheduled tasks run on the new server.
- Search Console shows no new crawl errors after a few days.
Rollback plan
If the new site fails, point DNS back to the old server. The old site is still intact, so service should return after caches expire. Keep the old backup and the old hosting until you are confident. A rollback is faster than debugging a broken migration under traffic.
Related articles
- How to Launch a Website on SysopHost: Step-by-Step
- How to Restore Website Files from a cPanel Backup
- How to Create and Use a Staging Site
- Website Down? Diagnose 403, 404, 500, 502, 503, and 504
- How to Take a Full cPanel Backup (and Restore It)
- cPanel Tutorial for Beginners
If the migrated site works on a temporary URL but not on the domain, contact SysopHost support with the domain, the old and new server details, and the exact error. Do not cancel the old hosting until the new site is verified.