Moving a WordPress website to new hosting can look like a simple copy-and-switch job. For a small business, however, the website is often connected to enquiry forms, email, analytics, appointment tools, payment systems and local search visibility. A migration that loads the home page but breaks one of those connections is not really complete.
This WordPress hosting migration checklist is designed for Canadian small businesses that want a controlled move with a clear recovery path. The goal is to reduce avoidable risk, test the new environment before customers reach it and make every important step reversible.
What changes during a hosting migration?
If the domain name and page URLs stay the same, visitors may see no obvious difference after the move. Behind the scenes, the WordPress files, media library and database are copied to another server. Configuration, security certificates, caching, scheduled tasks and DNS may also need attention.
WordPress’s official migration guidance says that when the database and URLs remain the same, a move can generally be completed by copying the files and database. If the database name, user or host changes, the corresponding settings in wp-config.php must also be updated. That simple summary is useful, but a business website needs broader operational testing too.
1. Inventory the website before touching anything
Start with a written inventory. This prevents a forgotten integration from becoming a surprise after launch. Record:
- the domain registrar and current DNS provider;
- all DNS records, including website, email and verification records;
- the current WordPress and PHP environment;
- active themes, plugins and any must-use plugins;
- forms and the addresses that receive their notifications;
- analytics, consent tools, Search Console and tag-manager connections;
- CDN, firewall and caching services;
- payment, shipping, booking, CRM and newsletter integrations; and
- scheduled jobs, licence keys and services restricted by IP address.
For an Ontario service business, follow one real customer journey from a local search result to a quote request. For an online store, follow a product from search or category page through cart, checkout and confirmation email. These journeys become your acceptance tests later.
2. Create a recovery point you can actually use
Back up both parts of the site: the database and the files. The database contains posts, pages, users, settings and much of the store or form data. The files include WordPress, themes, plugins and uploads. WordPress documentation specifically advises backing up the WordPress directory, images, plugins, other files and database before moving servers.
Store a copy somewhere independent of both the old and new host. Confirm the backup opens, has a plausible size and includes the expected database export and uploads. For a higher-risk site, test the restoration in a private environment. A backup is valuable only if it can be found and restored.
Keep the old hosting account available during validation. It is your fastest rollback option if a business-critical function fails.
3. Prepare the destination before the switch
Confirm that the new environment supports the site’s WordPress, PHP and database requirements. Check storage, memory, SSL, scheduled tasks, outbound email and any server-level caching. Install the certificate before public traffic is directed to the new server.
Copy the website to the new host and preview it privately using the host’s staging method or a local hosts-file entry. Avoid making a public duplicate that search engines can index, and ensure temporary staging settings do not carry over to production.
Review the WordPress update safety checklist. Do not combine a hosting move with unnecessary theme, plugin or design changes. Fewer moving parts make problems easier to isolate.
4. Test the copied website privately
Go beyond the home page. Test pages and every revenue or communication path:
- log in to WordPress and save a harmless draft;
- open key pages on desktop and mobile;
- confirm images, fonts, menus and downloadable files load;
- submit each form and verify both the on-screen response and delivered email;
- check phone, email, map and appointment links;
- test search, filtering, account and password-reset functions;
- for WooCommerce, use an approved test method to check cart, checkout, taxes, shipping and notifications;
- confirm analytics and consent behaviour; and
- review browser console and server logs for recurring errors.
If the site accepts live orders, bookings or user-generated content, plan how new data will be handled between the initial copy and final cutover. A final database synchronization or a short maintenance window may be needed so records are not left behind.
5. Plan the DNS cutover carefully
DNS tells browsers and other services where to find your website. Its time-to-live, or TTL, controls how long resolvers may cache a record. Cloudflare’s DNS documentation notes that a longer TTL can delay how quickly record changes reach users. If your provider allows it, review the TTL before the move and allow time for the earlier value to expire; there is no single propagation time that applies to every provider and network.
Take a complete record export or screenshot before editing DNS. Copy required mail and verification records as well as the web records. A website can appear healthy while email stops because an MX or TXT record was omitted.
Choose a quieter business period for the final synchronization and switch. Avoid moving the domain registration at the same time; changing several systems together makes rollback harder.
6. Protect URLs and search visibility
A hosting move does not require new page addresses. Keeping the same domain and URL structure is usually the cleanest approach. Check that HTTPS, preferred hostname, permalinks, canonical tags, XML sitemap and robots directives match the live site.
If URLs must change, create a one-to-one redirect map before launch. Google’s current Search documentation treats server-side permanent redirects such as 301 and 308 as strong signals that the destination should be canonical. Redirect each old URL to its closest equivalent rather than sending every page to the home page. Test the map and avoid chains where one old URL redirects through several stops.
After the switch, confirm the sitemap in Google Search Console and watch for indexing, crawl and 404 issues.
7. Validate the live site after DNS changes
Once traffic reaches the new server, repeat the critical tests on the public domain. Check from more than one network or DNS resolver if possible. Confirm:
- the certificate is valid and all HTTP versions redirect correctly to HTTPS;
- important pages return the expected status and do not redirect unexpectedly;
- forms, email, payments and webhooks work on the live environment;
- WordPress can run scheduled actions;
- caches and the CDN serve current content;
- analytics records a test visit or event;
- backups are running at the new host; and
- performance is measured after caches have been populated.
Keep a dated migration log with the old and new DNS values, backup location, cutover time, test results and any fixes. This makes support faster if an issue appears days later.
A concise WordPress hosting migration checklist
- Inventory hosting, DNS, email and integrations.
- Back up and verify files and database off-host.
- Prepare the new server, SSL and configuration.
- Copy the site and test it privately.
- Plan final data synchronization and rollback.
- Preserve URLs or prepare exact permanent redirects.
- Copy every required DNS record and make the cutover.
- Retest customer journeys on the public domain.
- Monitor errors, email, orders, indexing and backups.
- Retire the old host only after validation is complete.
Frequently asked questions
Will moving WordPress hosting cause downtime?
It does not have to cause a long outage. Preparing and testing the destination first, synchronizing late changes and keeping the old server online during DNS transition can reduce disruption. The exact experience depends on DNS caching, the website’s data and the migration method.
Can a hosting migration hurt SEO?
A server move with unchanged URLs can be low impact when pages remain accessible, fast and crawlable. Risk rises when URLs, redirects, canonicals, robots rules or content change unintentionally. Preserve the existing structure where practical and monitor Search Console after launch.
Does migrating the website also migrate business email?
Not automatically. Website hosting and email may be provided by different companies, even when they use the same domain. Inventory and preserve the mail-related DNS records, and confirm where each mailbox is hosted before changing anything.
When should the old hosting be cancelled?
Only after the new site is serving traffic consistently, business-critical tests pass, current backups run and the rollback window has closed. There is no universal number of days; base the decision on the site’s traffic, DNS configuration and operational risk.
Make the move with a documented plan
The safest migration is a small project with an owner, checklist, test evidence and rollback decision—not an improvised late-night copy. If your small business needs help assessing hosting, moving WordPress or managing the site after launch, explore Web Design Mate Inc.’s hosting and maintenance services.
Call 437-227-3938, email saqib@webdesignmate.ca or contact Web Design Mate Inc. to discuss a migration plan for your Canadian business website.
