Website Strategy

Website Migration Checklist: What to Prepare Before Switching Platforms

Prepare the content, access, URL decisions and launch ownership a migration needs. Use this checklist to identify blockers before switching website platforms.

Before switching website platforms, prepare six things: an inventory, a destination plan, access to the relevant systems, a content package, baseline measurements and a release checklist. Give every critical task an owner and an acceptance condition.

This checklist is for the preparation stage. It helps a marketing lead assemble a brief that a designer or migration partner can execute. The technical implementation will depend on your existing platform and the chosen destination.

1. Define what the migration is meant to improve

Write the business reason in concrete terms. Examples include making campaign updates easier, replacing a fragile publishing process or bringing the website into an agreed design system.

Separate three possible projects: changing platforms, redesigning the experience and rewriting the content. They can happen together, but each adds decisions and review work.

Record what must remain stable. This might include the main domain, high-performing page paths, a booking journey or customer access to documentation. Identify the launch window and any campaign or seasonal constraints.

Your acceptance condition: the team can explain why it is moving and what the release must preserve.

2. Inventory content and URLs

Combine the current sitemap, a crawl where available, CMS exports and knowledge from the team. A sitemap alone may miss files, campaign pages or routes that are not intended for search.

Include ordinary pages, CMS entries, important downloads, language versions and destinations used in ads or email. Record where relevant traffic and external links arrive if you have that data.

Use these columns in your working register:

  • Existing URL and content type.

  • Current purpose and business priority.

  • Proposed destination.

  • Decision: retain, rebuild, consolidate or retire.

  • Content owner.

  • Implementation status.

  • Test evidence and unresolved issue.

Do not guess at missing traffic data. Mark it as unavailable and use other evidence, such as sales-team use, to identify critical pages.

Your acceptance condition: every important old destination has an explicit decision.

3. Document what the website does

List the workflows that sit behind visible components. Forms, calendars, search, payments, gated resources, accounts and CRM connections all need attention.

For each workflow, record the trigger, required inputs, destination, notification and success state. Add what happens when it fails. Identify subscriptions and the person who owns each account.

A practical test brief might read: “Submitting the demo form creates the agreed CRM record, notifies the sales inbox and displays a confirmation. A failed request shows a recoverable error.” That is much clearer than “Move the form.”

Your acceptance condition: every essential workflow has a tested replacement or an explicit decision to keep it elsewhere.

4. Assemble content and permissions

Collect approved copy, original images, logos, font licences, videos and downloadable files. Record ownership and usage permissions where relevant.

Identify content that is being kept, rewritten or removed. Give new copy a responsible approver. Define a freeze point so the old website does not accumulate untracked changes during migration.

Keep a final change log for anything published after the first export. Without it, the new site can launch with an outdated price, missing article or obsolete team information.

Your acceptance condition: the builder can identify the current approved version without searching through several contradictory folders.

5. Confirm access and release responsibility

Prepare access to the old CMS, destination workspace, domain registrar, DNS management, analytics, Search Console and required integrations. Use invitations with appropriate permissions rather than sharing passwords in a project document.

Name who can authorise launch, who changes DNS and who verifies the website afterwards. These may be different people. Include a backup contact for the release window.

Also record domain email dependencies and other services that must remain intact. A website change should not become an accidental email outage.

Your acceptance condition: the people needed for launch have verified access and know their responsibilities.

6. Capture a meaningful baseline

Record recent organic traffic, relevant landing pages, enquiries and known conversion definitions. Where appropriate, compare with a similar previous period to understand seasonality.

Save the list of priority queries and URLs rather than relying only on a sitewide total. Note current tracking gaps. A broken baseline should not be presented as precise evidence.

Document representative mobile behaviour and any known issues that the migration is intended to fix. This creates a clearer before-and-after review than a visual preference alone.

Your acceptance condition: the team can distinguish an existing problem from a new release issue.

7. Agree the search and routing plan

For changed URLs, define destinations before launch. Google’s site-move documentation recommends keeping redirects for as long as possible, generally at least a year. Include their continued operation in the handover.

Keep a separate list of pages intentionally excluded from search. Review canonical URLs, metadata and language relationships as part of implementation. Confirm that the new site’s important pages remain discoverable through internal links.

The same care supports discoverability in Google’s AI search features: its guidance emphasises ordinary search eligibility, accessible content and useful links rather than special AI files.

Your acceptance condition: the release has an explicit routing and indexability plan, with no unexplained destination changes.

8. Write launch gates that can pass or fail

Avoid a vague “QA complete” checkbox. Define checks that produce evidence.

  • Priority pages contain the approved content and metadata.

  • Old priority URLs reach the intended destination.

  • Forms and other critical workflows pass end-to-end tests.

  • Mobile and keyboard journeys remain usable.

  • Production analytics capture the agreed actions once.

  • Public pages have the intended search settings.

  • Domain and certificate checks pass.

  • The launch owner accepts remaining non-critical issues.

Decide which failures block release. A decorative alignment issue and a broken contact form should not have the same severity.

9. Prepare recovery and follow-up

Keep recoverable exports and backups, and document the conditions that would trigger rollback or a forward fix. Restoration is not always immediate, so verify what the recovery process actually involves.

Schedule a release-day check, an early follow-up and a later review appropriate to the site’s risk and traffic. Assign ownership of errors, missing content and tracking discrepancies.

Do not cancel old services before confirming that they are no longer required for media, routing, email or recovery.

Your acceptance condition: someone owns the site after launch and knows what evidence to review.

Frequently asked questions

Before approving the final scope. The inventory and dependency review can reveal work that changes the budget or makes a proposed platform unsuitable.

No. Use evidence and business purpose to decide. Consolidation or retirement should be deliberate, with appropriate handling of the old destination.

No. It reduces preventable omissions. Search performance can change, and implementation quality still needs verification.

Turn preparation into a scoped project

Bring the inventory, key workflows and business goal to SXDSTUDIO’s Switch to Framer service. Those inputs make it possible to scope the move around the website you actually operate.

Your design + build partner

Product, websites, and brand, designed and shipped by one senior team for funded B2B companies.

Your design + build partner

Product, websites, and brand, designed and shipped by one senior team for funded B2B companies.