A migration aims to align files, database, email, and domain in the new environment — and cut over with a rollback path. Organised in a common order so you can align with the provider.
Inventory content and access first
List site files, databases, scheduled jobs, third-party integrations, and access paths such as control panel / FTP / SSH. If you use a CMS or plugins, note versions and dependencies so you can verify after restore on the new host.
After backups complete, keep a copy locally or over a secure private channel; do not send passwords, private keys, or full database connection strings by ordinary email . When exchanging credentials, use the provider’s secure method or reset first. If you are comparing new Shared Hosting or higher-tier plans, also ask whether they help with imports.
Schedule DNS, email, and SSL together
Confirm where DNS is managed today and which A/CNAME (or nameserver) records will change. If email uses the same domain, do not ignore MX and related records — or the site may cut over while mail breaks.
On the new host, finish SSL/HTTPS setup and test-URL checks first; before production cutover, use hosts file or a test domain to verify pages, login, and payment callbacks.
Test, cut over, and roll back
Agree a low-traffic window for DNS cutover and note TTL: shorter TTL often propagates faster, but real speed still depends on caches — not a fixed guarantee. After cutover, keep checking home, forms, checkout, and admin.
Keep the old host for an observation period and prepare rollback (restore DNS or re-point). Details vary by platform — if unsure, start via Contact and describe the current setup and preferred cutover time.