A website migration checklist lists every step that gets your content, URLs, and integrations onto a new platform and keeps them working after launch. This is the site migration checklist our delivery team runs on every migration, refined over 50+ projects. Copy it as a Google Sheet, free and without signing up.
Your website has its own content model, integrations, and quirks, and the plan bends around them. The order of the stages stays the same, because each one depends on the one before it. Skip ahead and you end up filling content into components that don't exist yet, or testing redirects for the first time on launch day.
Each step is a task for the project team, whether that's yours, ours, or both. Steps only you can do, like approvals, say so.
The decisions you make in the first weeks shape everything after them. Get these answered before anyone builds a single template.
Build the house before you move the furniture in. Content migration only starts once every component it needs exists and you've approved it.
This is the part a CMS migration checklist usually covers on its own. We don't copy and paste. We fill the content, spot-check it by hand, then compare every page with the source by script. Then we fix and recheck until the script finds nothing left.
Six checks protect your rankings on launch day. The reasons behind each one, and how to diagnose what goes wrong, live in the full guide.
A form that stops sending leads is the quietest bug in any migration. Nobody notices until sales asks where the pipeline went.
A calm launch day is mostly decided in the week before it. By the go/no-go meeting, every item here is done.
Launch day itself should be boring. If you're making decisions today that you could have made last week, go back one stage.
Going live isn't the finish line. The first three days tell you if anything is broken, and the first week tells you if it's stable enough to retire the old site.
Your old site stays live and reachable until the new one has proven itself. Before launch, we agree on what would make us switch back, so nobody has to make that call under pressure.
A core journey breaks: the site is down, or people can't complete the main form or checkout. This applies whether it happens at minute 10 or hour 20.
Traffic, conversions, or indexing fall below your baseline. This usually shows after 24–72 hours, once there's enough data to compare.
A core journey is broken: the site is down, or checkout or the main form fails.
A secondary flow is broken but has a workaround, like a secondary call to action or a tracking gap.
Cosmetic issues, like styling errors or minor UI bugs, go to the post-launch backlog.
Whoever hosts your site makes the switch, and we're on hand to help. We handle the code and the CMS. You approve the decision and tell your stakeholders.
All 66 steps in one Google Sheet, with columns for owner, status, and notes. Make a copy, fill it in, and share it with your team. You don't need to sign up.
The same checklist, run on these migrations and many more.
Audit and decide, set up the new platform, migrate content, carry over SEO, reconnect integrations, prepare the launch, launch, and monitor. This checklist breaks those eight stages into 66 tasks.
Get access to the current site, audit the content, and decide what happens to each page. Record performance on your most important pages, too, so you can compare the new site against the old one.
Fill it by script or by hand, spot-check a sample, then run a script that compares every page with the source. Fix what's off, run the script again, and sign off on staging.
Pages with no traffic, no links pointing to them, and no business reason to stay. Merge or archive them and redirect their URLs to the closest page. The website migration SEO guide covers when to let a URL go for good.
Keep the old site live until the new one has proven itself. If a core flow breaks, point the domain back to the old site right away. If traffic or indexing drops over the following days, point the domain back, turn off the redirects, hide the new site again, and restore tracking on the old site.
A CMS migration checklist covers the content: models, scripts, and validation. A website migration checklist adds everything around it, from URLs and SEO to integrations, launch, and rollback. This page covers both.
We’ll find out what your team needs, together. Book on Calendly.
Send us a message or schedule a call.
Discuss your needs in a 25 min free call.
Get a quote from us within 3 days.
You can also e-mail us at sales@notum.cz or book a meeting directly in our calendar.
.png)
