How to Prepare for a Website Migration Without Losing Emails, Files, or Sales
A web migration without data loss requires an inventory, backups, pre-migration validation, DNS management, email management, and testing before the final switch.
Web migration without losing data Start before copying any files. To move a site safely, you need to identify which components are present, what changes frequently, and which services depend on the domain. WordPress, databases, email, DNS, certificates, and scheduled tasks may require different validations.
In a nutshell
- A secure migration begins with an inventory and verifiable backups, not with changing the DNS.
- The website, database, email, domain, certificates, and integrations should be reviewed separately.
- The final change must be made after the site has been validated in the new environment.
- A migration window and a fallback plan minimize the impact if a problem arises.
Preparation reduces two risks: forgetting information and causing an unnecessary interruption during the transition.
Take inventory before migrating
- Primary domain and additional domains.
- Site(s) installed.
- Databases and related users.
- Email accounts and approximate size.
- Certificates and special redirects.
- Scheduled tasks or automations.
- External integrations: payments, forms, APIs, or email services.
- Administrative access rights required for validation.
Define what information changes throughout the day
A news site can remain virtually unchanged for hours. An online store, on the other hand, may constantly receive orders and update its content. The more dynamic a website is, the more important it is to coordinate a short window between the last copy and the final update.
For e-commerce businesses, avoid migrating without a plan for orders that might come in during the transition.
Do not change your DNS settings before validating the destination
The new site should be set up and tested before pointing the domain to it. Check pages, forms, the login page, images, links, outgoing email, and critical features. If you're using a test environment, this phase can be carried out without affecting the public.
To understand the DNS change, see How to Point a Domain Using A and CNAME Records.
Email deserves its own plan
If the email is associated with the same domain, check where the accounts are hosted and which DNS records the service uses. A website migration does not always involve migrating email, and combining the two processes unnecessarily can increase the risk.
If you're setting up a new email account, check SPF and DKIM for Corporate Email.
Keep a separate copy
Before you begin, keep a copy that is independent of both the source and destination servers. This allows you to review files or data even if either environment becomes unavailable during the process.
Regular backups are important, but a migration calls for a specific backup prior to the change.
Check connections and routes after the transfer
When you change your domain, protocol, or folder structure, old paths may remain within WordPress. Check images, buttons, downloadable files, and internal links. Also check for redirects if a URL has changed permanently.
Check the website while you're logged out
It’s not enough to just view it while logged in as an administrator. Open an incognito window, test it from your phone, and perform the actions a customer would take. On an online store, test the shopping cart and checkout; on a service website, test the form and WhatsApp; on a blog, test navigation and the search bar.
Keep the source for a reasonable period of time
Do not immediately remove the previous environment. First, verify that DNS has propagated, that email is working, and that no data is missing. The time required depends on the scenario and the conditions of the source service.
A successful migration means validating, not just copying
One Web migration without losing data It is considered complete when the new site is up and running, the dependent services have been verified, and a recovery plan is in place. UNEMPRENDE offers Free website migration in the applicable plans; prepares access points and inventory in advance to reduce time and risk.
Recommended Steps for a Web Migration
- Take inventory of the site, database, email, DNS, domains, and integrations.
- Create and verify backups before making any changes to the current environment.
- Copy the site and test it in the new environment without changing the public domain just yet.
- Validate forms, payments, access, links, images, and scheduled tasks.
- Prepare for the DNS change and minimize content changes during the transition.
- Check the website and email after the change and keep the previous environment in place for a reasonable period of time.
Common Mistakes to Avoid
- Do not cancel the previous service before verifying the migration.
- Don't forget email accounts or DNS records that don't belong directly to WordPress.
- Do not make any structural changes to the site while migrating.
Frequently Asked Questions
When should I change my DNS settings?
After the destination site has been copied and validated, changing the DNS settings before testing the new environment may direct visitors to an incomplete installation.
Does a website migration automatically include email?
Not always. The website and email may be hosted by different providers or run on different infrastructures. First, identify where each service is hosted, and migrate only what is necessary.
You might also be interested in Tutorials
Resources and Support
We offer a variety of resources to help you become familiar with and understand your resources and opportunities, and to enjoy the benefits of having a digital infrastructure. In addition, we have social programs to support startups and projects with exclusive benefits.