Before moving a website, ask the new host what they need and what they will handle. Clear answers prevent downtime and missing data.
Ask What Is Included
Will they migrate files, databases, email, DNS records, cron jobs, redirects, and SSL settings, or only the website files?
Ask About Testing
Can you preview the migrated site before DNS changes? This is important for WordPress, shops, and custom applications.
Ask About Email
Email is often separate from website hosting. Make sure MX, SPF, DKIM, and DMARC records are preserved.
Ask About Rollback
Keep the old hosting available until the new site is confirmed working.
A good migration starts with questions, not file transfers.
Ask What Access They Require
Find out whether the migration team needs a control-panel login, SFTP access, a backup archive or database credentials. Use a temporary or restricted account where possible and agree when it will be removed. Never send passwords through an ordinary email if a secure ticket or credential-sharing method is available.
Ask How Current Data Stays Current
A brochure site can often be copied once. A shop, forum or membership site may receive orders and user changes while the first copy is being tested. Ask whether there will be a final database sync, a maintenance window or a content freeze, and who decides when it begins.
Ask About Compatibility and Limits
Confirm supported PHP and database versions, required extensions, storage, upload limits, cron jobs, rewrite rules and any server modules the application needs. Ask whether backups begin immediately on the new service and whether the first successful backup will be checked before the old host is cancelled.
Agree the Cutover and Verification
Clarify who changes DNS, how long the old service remains online and what constitutes a successful migration. The test list should cover HTTPS, forms, email, login, uploads, scheduled jobs and commercial workflows. Keep a rollback route until the new site has operated normally through propagation.
Ask About Cost and Responsibility
Free migration may cover a standard website but not mailbox history, custom software or emergency work. Ask what is included, what may incur a charge and which tasks remain yours. Written scope prevents both sides assuming the other is handling a critical dependency.
