How to Migrate Your Website to Chapter22 Hosting

A clean migration is backup → restore → preview → DNS. Skipping preview is how you discover PHP or path issues in production.

1. Inventory

Site files (public_html / web root)
Databases and users
Cron jobs, .env / wp-config.php secrets
Email if it lives on the same host (treat as a separate project)
Current DNS (A, AAAA, MX, TXT)

2. Back up at the old host

Export a full file archive and a SQL dump. Verify the archive opens locally before you cancel anything.

3. Create the destination

In Chapter22 web hosting: create the domain/subdomain, databases, and DB users. Note the new DB name/user/password.

4. Upload and import

Upload files via File Manager, SFTP, or a one-shot pull if support assists.
Import SQL in phpMyAdmin or CLI.
Update connection strings for the new DB credentials and any hardcoded old paths/URLs.

5. Preview without changing DNS

Map the domain to the new IP in your local hosts file, browse key pages, forms, and admin login. Fix 500s and missing assets here.

6. Cut over

Lower TTL ahead of time when possible.
Final file/DB sync if the site kept changing.
Point DNS with the domain guide.
Issue Let’s Encrypt SSL.
Keep the old host available for several days.

7. Post-cutover

Watch error logs, confirm cron, update SPF/DKIM if mail moved, and only then cancel the previous provider.

Frequently Asked Questions

Will you migrate the site for me?

Open a ticket from the client area with current host details and we will tell you what self-serve steps versus assisted migration look like for your stack.

When do I change DNS?

Only after files, database, and a hosts-file preview look correct. Lower TTL the day before.

Need help?

If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.

Build the server. Grow the community. Start your next chapter.