Back to Blog

Website Migration Checklist: Ottawa Edition

Website Migration Checklist: Ottawa Edition - article cover illustration

Before You Cancel Your Old Host: The Website Migration Checklist

Most website migration checklists stop at the hosting steps. Copy the files, move the database, point the domain, done. Then the phone calls start. A customer’s discount code does not work. A member cannot log in. An order from launch week is gone. Nobody moved those records, because no checklist included them.

This website migration checklist covers the records and workflows the generic lists omit: the gap between export and switch, order history, member access, course progress, community profiles, email flow, redirects, and cache warm-up. It is the acceptance work we run before any client cancels an old host. Planning a move? Start with our WordPress migration service. Doing it yourself? Work every check below before you send the cancellation email.

A quick scope note. This is written for Ottawa service business websites: contractors, trades, home services, anyone whose site holds real business records. If your next step after the move is a bigger rebuild, see web design for contractors or our lead-gen website service. This piece is about one thing only: getting from the old box to the new box with the business records intact.

Why Most Migration Checklists Stop Too Early

Most checklists are written for simple brochure sites. A few pages, a contact form, no customer records. That describes fewer and fewer service business websites every year. If you sell online, run a membership, deliver courses, or host a community, your website is a system of record, not a brochure. Orders and transactions. Membership access. Course progress. Community profiles. Discount codes. Those records are the expensive part of a migration, and they are exactly what the hosting-only checklists skip.

There is also a timing trap nobody warns you about. A migration is not a single instant. Content gets frozen and exported, the new environment gets built and tested, and the DNS switch happens days later. Work does not stop on your side while that happens. The gap between the export cut and the switch is where silent loss lives, and it is where this checklist starts.

Diagram of the website migration acceptance flow: snapshot both sides, gap-window check, class-by-class reconciliation, real-account logins, redirect crawl, cache warm-up before sign-off

The Website Migration Checklist: Ten Checks Before You Cancel

Work the checks in order. Each one ends in a pass, a fail, or a written exception. Anything else is a guess.

1. Take the Snapshot Before Anyone Touches Anything

You cannot verify what you never recorded. Before the export cut, capture a snapshot of every data class on the old box: orders, transactions, membership access, course progress, community profiles, discount codes, and user accounts. Store it somewhere that is neither server. That snapshot is your source of truth for every check that follows, and the thing you reconcile against when something looks missing. Write down the exact date and time it was taken, because the gap-window check depends on that timestamp. Without a snapshot, verification is just opinion.

2. Check the Gap Window First

Anything created after the export cut but before the switch (discount codes, orders taken that day, new signups) can exist on one box only. Check that window first. It is the first silent-loss class because everyone assumes the site was frozen the whole time, and it almost never is. Someone kept selling, kept issuing codes, kept enrolling members. Pull the records from that window on both boxes and compare them against your snapshot. A code created on the old box after the export exists nowhere else until someone recreates it, and no hosting step will ever catch that.

3. Reconcile Each Data Class, One Class at a Time

Reconcile each data class (orders, transactions, membership access, course progress, community profiles) one class at a time against a snapshot taken before the move. Class by class, not everything in one pass. Single-class reconciliation looks slower on paper and runs faster in practice, because each pass ends with a definitive answer: this class is clean, or here is the exact list of what is missing. Mixed-pass checking ends with a feeling. A feeling is not acceptance evidence.

4. Do Not Accept Row Counts as Verification

Equal row counts can hide swapped or missing records. Verification means checking real accounts and real records, not counting rows. A count tells you the orders table has the same number of rows on both boxes. It says nothing about whether those rows point at the right customers, carry the right statuses, or arrived intact. Open actual orders. Open an actual member account. Read an actual progress record. Counts are a smoke test. Real records are the acceptance test.

5. Log In With Real Accounts at Every Access Level

Log in with a real account at each membership level and confirm the right content is released to that account. One login and one check per level. Access mapping is where migrations break quietly: the account exists, the password works, and the gated content is either locked against the member who paid for it or exposed to the whole public. Neither failure shows up in any file count or row count. Only a real login at each level catches it.

Moving a site with orders, members, or course data?

That same acceptance discipline is why our work carries 5.0 stars across our Google reviews. Start with a free website audit to see what your current site is holding.

This reconciliation work is the core of our migration service. Or call (343) 842-4444 and talk through what your move needs to protect.

Submit a real test through every path a customer could use: the contact form, the quote form, the booking form. If you sell online, walk the store checkout with a test product. Check that each entry arrives where it is supposed to arrive, not just that the form renders. A form that fails silently is worse than one that shows an error. It keeps collecting trust while losing the lead, and you find out weeks later when a customer says they filled it in twice.

7. Crawl the Old URL Set

Crawl the old URL set. Every old address should return a 301 to its new home, and the crawl should report zero 404s. Old URLs live on in Google’s index, in customer bookmarks, and in the quote you printed last season. Every address that dead-ends throws away a ranking signal you already paid for. If local search visibility is part of why the site exists, protect it through the move. Our Ottawa SEO work starts with exactly this kind of crawl.

8. Verify Email Flow After DNS Settles

After DNS settles, send a round-trip test: a form notification, a password reset, and one transactional email. Email is the workflow most often forgotten in a migration because it lives partly outside the website. Your mail records (the DNS entries that route email), your sending service, and the new host’s mail stack all have to agree after the flip. When the password-reset email is broken, customers lock themselves out quietly, and the first symptom is a support inbox you no longer receive mail in.

9. Warm the Cache Before You Announce Anything

A full cache purge right after the switch forces every page to render cold, which can make the site slow or appear broken to the first visitors and crawlers. Warm the key pages before you announce anything. Load the home page, your service pages, and your busiest posts yourself, on phone and desktop, and let the cache fill before the world arrives. If the site still feels slow once it is warm, that is a separate speed problem. The fixes live in our Speed Sprint and in this guide to WordPress speed optimization in Ottawa.

10. Sign Off, Then Cancel

Sign off the checklist, then cancel the old host. Keeping the old box paid for one extra week is cheap insurance; a cancelled box with the only copy of a missed record is not. The sign-off should be written: what was checked, against which snapshot, what passed, and which exceptions remain open. That record is what turns a moved site into a verified move, and it is the first document you will want if anything looks wrong next month.

The Verification Table: Object, Method, Pass Condition

Here is the whole checklist compressed into one acceptance table. Print it, work it, attach it to the sign-off.

aria-label="10. Sign Off, Then Cancel"
Object Verification method Pass condition
Gap-window records (codes, orders, signups) Compare both boxes against the pre-migration snapshot for that window Every record exists on the new box or sits on a written fix list
Orders and transactions Reconcile one class at a time against the snapshot Every record present, intact, and attached to the right customer
Membership access Log in with a real account at each level Each level grants exactly the content it should, no more, no less
Course progress Compare real learners’ records against the snapshot Progress matches and is attributed to the right account
Community profiles Open real profiles on both boxes, side by side Profile data and activity present and attributed to the right member
Old URLs Crawl the old URL set Every address returns a 301 and the crawl reports zero 404s
Email Round-trip test: form notification, password reset, one transactional email All three arrive where they should
Forms and store paths Submit real test entries on every customer path Each entry arrives where it should

When a Check Fails

A failed check is not a crisis. It is the checklist working. Document the gap against the snapshot, fix it on the new box, re-run the check, and move on. What you must not do is cancel the old host with a failure still open, or quietly patch around a missing record and mark the class verified. Keep the failure list with the sign-off. It is the honest record of what the migration actually did, and it is worth more than a tidy report that hides a gap.

After the Move: Keep Watching

Acceptance is not the end of the work. The first weeks after a migration are when drift surfaces: a stale cached page serving old content, a form that passed sign-off breaking after an update, rankings wobbling while crawlers digest the redirects. Someone has to watch the dials. If a Barrhaven roofing company’s quote form silently stops delivering after a plugin update, a regular check is what catches it before the lost requests pile up. Our WordPress maintenance guide lays out the monthly loop, and the Care Plan is how we run it for Ottawa businesses. And if this move was step one toward a bigger rebuild, start with Start Here to see how we scope that work.

Website Migration Checklist: Frequently Asked Questions

What is a website migration checklist?

It is the acceptance list you complete before cancelling your old hosting. Beyond the hosting steps, it verifies that business records survived the move: orders, transactions, membership access, course progress, community profiles, discount codes, redirects, email flow, and cache state.

How do I verify no data was lost in a website migration?

Take a snapshot of every data class before the move, then reconcile each class one at a time against that snapshot. Do not rely on row counts. Equal counts can hide swapped or missing records, so open real accounts and real records before you accept the migration.

Should I cancel my old host right after the DNS switch?

No. Complete and sign off the full checklist first, then cancel. Keeping the old box paid for one extra week is cheap insurance; a cancelled box with the only copy of a missed record is not.

Why is my website slow right after a migration?

Usually cold caches. A full purge right after the switch forces every page to render from scratch, so the first visitors and crawlers can see a slow or half-loaded site. Warm the key pages on mobile and desktop before you announce anything.

How do I know email is working after a migration?

Test it instead of waiting. After DNS settles, send a round-trip test: a form notification, a password reset, and one transactional email. When all three arrive where they should, mail has settled for the paths your business depends on.

Moving a Website With Real Business Data?

Orders, members, courses, community. We migrate the records, not just the files, and reconcile every data class against a pre-migration snapshot before anyone cancels anything. See how we scope and verify a move on the migration service page.

Or call (343) 842-4444