Migrations
Website migration for beginners: what to expect before, during, and after
A migration is mostly about creating a second working copy before directing visitors to it. Beginners often imagine the website physically “moves” all at once; in practice the data is copied, tested, synchronized and then traffic is redirected.
Before the move, preserve the source
Take a backup and inventory the current setup. Know the domain registrar, DNS provider, host, email provider, database and any third-party services.
During the move, build a parallel destination
Copy files and databases, configure the application and test it without changing public DNS if possible. This keeps troubleshooting away from live visitors.
At cutover, change only what is necessary
Update the relevant DNS records or nameservers and keep the old service running. Cached DNS means visitors can reach different environments during the transition.
After the move, test business functions
Verify HTTPS, forms, logins, checkout, email and scheduled jobs. Keep the old host until you are confident the new environment has everything you need.
Define a finish line before the move starts
A migration is complete only when the production domain reaches the new site, HTTPS works, forms and logins work, mail is accounted for and the old host is no longer receiving traffic you still need. Write those checks down before cutover.
Keep the source service until the validation period is over. Cancelling early removes the simplest rollback option and can also destroy files or mailboxes you did not realize were still in use.
Common questions
When can I cancel the old host after a migration?
After DNS has settled, the new site and email paths are verified, and you have confirmed no required data or services remain on the old account. Keeping a short overlap is safer than cancelling immediately.