Common hosting task

How to move WordPress to a new host

A good migration is a controlled cutover, not a blind copy. Back up first, test on the new host, then change DNS only when the site works.

Use this as a focused checklist for one common hosting task. The larger setup guides still cover full-site and full-server builds.

Difficulty
Intermediate
Time
60 to 180 minutes
Images
5 official examples

1. Back up the old WordPress site

Export the database, copy wp-content, record PHP version, permalink settings, active plugins, cron jobs, email routing, and CDN settings. Do this before installing anything on the new host.

GreenGeeks getting started support page
GreenGeeks getting started: Onboarding docs help identify what has to move: account access, domains, files, email, and site tools.
ScalaHosting SBackup panel
ScalaHosting managed VPS KB: Backup tooling should be confirmed before the migration starts.

2. Copy files and database to the new host

Use the host migration tool when available. For manual moves, copy wp-content, import the database, update wp-config.php database values, and keep the old site unchanged until testing is complete.

GreenGeeks WordPress hosting page
GreenGeeks WordPress hosting: Managed WordPress plans should be checked for migration, backups, cache, SSL, and support scope.
Hostinger official web hosting artwork
Hostinger web hosting: A host with migration help and clear panel tools reduces migration friction for smaller sites.

3. Test the new copy before DNS changes

Admin

Log in, update permalinks, and verify users.

Media

Check image uploads, downloads, and generated thumbnails.

Forms

Submit contact, lead, checkout, and account forms.

Cache

Disable duplicate cache layers until the new site is stable.

4. Change DNS, enable SSL, and keep rollback open

Point the domain to the new host, issue SSL, clear mixed content, and keep the old hosting account active for at least a day. If the new site breaks, switch DNS back while the old site is still available.

Hostinger domain pointing records section
Hostinger domain pointing: DNS cutover should happen after the new copy has been tested.
Namecheap WordPress HTTPS settings steps
Namecheap HTTPS for WordPress: HTTPS and mixed-content checks are part of the migration, not an afterthought.

Official sources checked

GreenGeeks WordPress hosting

Used for WordPress migration and feature checklist context.

Hostinger domain pointing

Used for DNS cutover sequence.

Namecheap HTTPS for WordPress

Used for HTTPS and mixed-content migration checks.

ScalaHosting managed VPS KB

Used for backup workflow context.

© 2026 WebHostWatch. We may earn affiliate commissions from links. Recommendations remain editorially independent.