Quick answer: Before migrating, take a full backup, document your stack (PHP, database, web server versions and settings), clean up unused files and databases, lower your DNS TTL, and schedule the move for your lowest-traffic window. Good preparation is what makes the actual transfer fast and boring — in the best sense.
Overview
Most migration problems are discovered during the move but created before it: unknown dependencies, oversized junk data, forgotten cron jobs. An hour of preparation typically saves several hours of debugging on migration day and reduces the downtime window dramatically.
Before you start
- Access to your current hosting (SSH or control panel) and your DNS management.
- A recent, tested backup stored somewhere other than the server being migrated.
- Your new Cloud2Y server provisioned and reachable.
Step-by-step guide
- Inventory the stack: note web server (Nginx/Apache), PHP version and extensions, database engine and version, cron jobs, queue workers and SSL certificates.
- Take a full backup: files plus database dumps, and verify the archive actually opens — see how restores work.
- Clean up: remove unused plugins, old backups inside the webroot, log bloat and abandoned databases — less data means a faster copy.
- Lower DNS TTL to 300 seconds at least 24 hours before the move, so the final switch propagates quickly.
- Freeze changes: schedule a content/code freeze for the migration window so nothing is written to the old server mid-copy.
- Plan the window: pick your lowest-traffic hours and tell stakeholders when the switch happens.
Common issues
- Backups that never restored: an untested backup is a hope, not a plan — do a test restore first.
- Hardcoded configuration: absolute paths, old IPs or server-specific settings in config files break on the new host — note them during inventory.
- TTL left at hours: a 24-hour TTL means some visitors see the old server a full day after cutover.
When to contact support
If the inventory reveals anything you are unsure how to move — custom daemons, very large databases, licensed software — describe it in a free migration request and we will plan it with you.
Frequently asked questions
Why should I lower the DNS TTL before migrating?
TTL controls how long resolvers cache your old IP. Lowering it to about 300 seconds a day ahead means the final DNS switch reaches visitors in minutes instead of hours.
Do I need a backup if the old server stays online?
Yes. A tested, independent backup protects you against copy mistakes, surprises on the source host and anything that happens between the snapshot and the switch.
What gets forgotten most often when moving a site?
Cron jobs, SSL certificates and mailboxes are the classic three. Inventory them before the move so each one is explicitly re-created or migrated on the new server.
Related articles
- Migration checklist
- How to avoid downtime during migration
- How to migrate databases
- How the Cloud2Y migration process works
Ready to move? Order a VPS at Cloud2Y →
