Free migration means a provider offers some transfer work without a separate migration charge. It does not define which files, mailboxes, applications or follow-up fixes are included. Get the scope in writing before canceling the existing service.
Agree on what moves
- Website files, databases and uploaded media.
- Mailboxes, mail routing and any local address books that need separate handling.
- Scheduled jobs, background workers and application integrations.
- Domain and DNS changes, including records that belong to services outside the hosting account.
- Expected downtime, the final data-sync method and who can approve the switch.
For example, copying a WordPress installation does not automatically transfer a mailbox hosted elsewhere. A shop may also receive orders after the first copy, so the plan must account for new writes.
Keep a usable recovery path
Take an independent backup of the relevant files and data. Confirm it can be read and that the person responsible knows how to restore it. Keep credentials inside an agreed secure access method, rather than placing passwords in a normal ticket or document.
Test the destination before changing DNS
Use a provider-supported preview method that tests the real hostname and HTTPS behavior where possible. Check the homepage, a representative article or product, login, images, forms and required integrations. A temporary preview URL alone may not exercise cookie, certificate or redirect behavior correctly.
For a site that accepts transactions or user submissions, arrange a controlled test and cleanup process. Do not assume a successful homepage load proves the complete application works.
Switch and watch
- Complete the agreed final synchronization or maintenance window.
- Change only the required DNS records. Preserve unrelated email and verification records.
- Verify HTTPS, page routes and the actual user workflow through the public hostname.
- Check for new errors and make sure scheduled work runs on the intended server.
- Keep the old environment available for the agreed rollback period.
DNS caches do not all expire at once. The exact transition depends on existing record lifetimes and resolver behavior; a blanket promise of instant propagation is not a migration plan.
Before ordering a transfer, use our hosting requirements checklist to confirm the destination supports the application and recovery needs.