Quick answer: A complete migration covers ten things: inventory, backup, target server prepared, files copied, databases moved, config and cron re-created, SSL issued, email handled, testing via hosts file, and a planned DNS cutover with the old server kept as fallback. Print this list and tick it off — every skipped line is a classic incident.
Overview
This is the condensed, do-not-forget version of everything in the Migration Center. Each line links to the detailed guide. It works for a single WordPress blog and for a ten-site agency server alike.
Before you start
- Your new Cloud2Y server ordered and reachable (order guide).
- Access to old hosting, DNS and (if relevant) mail admin.
Step-by-step guide
- Inventory — sites, databases, versions, cron jobs, certificates, mailboxes (preparation guide).
- Backup everything and test-restore one item (restore guide).
- Prepare the target — stack or control panel installed, firewall open on 80/443.
- Copy files — rsync/SFTP; plan a delta re-run near cutover.
- Move databases — consistent dumps, verified imports (guide).
- Re-create the invisible parts — cron jobs, environment variables, queue workers, log rotation.
- Issue SSL on the new server before the switch.
- Handle email — migrate mailboxes or move to a provider (guide); update SPF/DKIM/PTR.
- Test via hosts file — full click-through under the real domain (guide).
- Cut over — TTL lowered a day ahead, write freeze, final delta, DNS switch, old server kept running (guide).
Common issues
- Skipping the inventory: the source of every "we forgot X" — it is step 1 for a reason.
- Treating email as an afterthought: mail breaks loudest; decide its destination early.
- No rollback plan: know in advance how you would go back — see rolling back.
When to contact support
Use this checklist as your ticket template: paste it into a free migration request with your answers per line, and our engineers can take over from any step.
Frequently asked questions
What are the essential steps of any site migration?
Inventory, tested backup, prepared target, file copy, database move, cron and config re-creation, SSL, an email plan, hosts-file testing, and a TTL-prepared DNS cutover with the old server kept alive.
What is the single most skipped step?
The inventory. Almost every migration incident traces back to something nobody listed at the start: a cron job, a certificate, a mailbox or a background worker.
Can I hand this checklist to Cloud2Y and let you run it?
Yes. Paste the checklist with your answers into a free migration ticket and our engineers take over the technical steps, reporting back as each stage completes.
Related articles
- Post-migration checklist
- How to prepare your website for migration
- Common migration issues
- How the Cloud2Y migration process works
Ready to move? Order a VPS at Cloud2Y →
