[email protected]
0333 050 1245

Content Migration Plan: A Practical Guide for UK Business Owners

  1. Home
  2. »
  3. Blog
  4. »
  5. Content Migration Plan: A Practical Guide for UK Business Owners

A content migration plan is a written strategy for moving your website’s pages, images, documents and data to a new site or platform without losing search visibility, customers or compliance along the way. The short version: audit what you have, decide what deserves to move, map every old URL to a new one, test before launch, then watch closely for the first few weeks. This guide walks you through each step, with the UK-specific checks that generic checklists tend to skip.

Kukoocreative
Bring Your New Website to Life
Kukoocreative creates websites and designs that build brand recognition and help business owners connect with the people who matter most.

TL;DR

  • Audit first. Move only content that still serves a customer need, and retire or merge the rest.
  • Build a URL map in a spreadsheet: every old address points to its closest new equivalent, using permanent server-side redirects.
  • Test accessibility and your cookie consent tool on the new site before launch, not after.
  • Keep redirects live for at least 180 days and check Search Console daily for the first two weeks.
  • Treat migration as a chance to clear out technical clutter, not simply to copy it across.

Table of Contents

What a content migration plan actually covers

Most owners think of migration as a technical cutover: one weekend, one switch. In practice the switch is the smallest part. The real work is deciding what content exists, what it is for, where it will live and how people (and search engines) will find it afterwards.

A sound plan has six parts:

  1. Goals and scope. Why are you moving? New design, new platform, new domain, or all three?
  2. Content audit. A full inventory of what you have and what it earns.
  3. Structure and mapping. The new site layout and a one-to-one map from old to new.
  4. Build and transfer. Moving the content, manually or by script.
  5. Testing. Links, redirects, forms, accessibility, tracking, consent.
  6. Launch and aftercare. Monitoring, fixing and tidying up.

Google splits site moves into similar stages in its own site move documentation: prepare the new site and test it thoroughly, prepare a redirect map, then launch and monitor. The detail below follows that rhythm, and adds the parts a Leeds or wider UK business will want to cover.

Step 1: Set the goal and the scope

Write down, in two or three sentences, what the migration must achieve. “Move to a faster platform and keep our enquiry volume” is a goal. “Redo the website” is not.

Then note which of these apply, because each changes the risk level:

Type of move Typical risk to rankings What to plan for
New design, same URLs and domain Lower Content parity, speed, mobile layout
New platform, URLs change High Full redirect map, sitemap, monitoring
New domain Highest Redirects, Search Console change of address, long redirect lifespan
HTTP to HTTPS Medium Redirects, canonical tags, updated internal links

Google notes that a move without URL changes, such as a new hosting platform or CMS where addresses stay identical, is considerably simpler. If you can keep your URLs, keep them.

Also set a baseline now. Export last quarter’s organic traffic, top landing pages, enquiry numbers and rankings for your ten most valuable search terms. Without a baseline you cannot tell whether the move helped or hurt.

Step 2: Audit your content before you move it

The cheapest page to migrate is the one you decide not to. A content audit is a spreadsheet with one row per URL and a decision against each.

Build the inventory

Crawl your site with a crawling tool and combine the list with your sitemap, Google Search Console and analytics. Include non-page assets: PDFs, downloadable brochures, images, videos, and any landing pages that are only reachable from adverts or email.

Useful columns:

  • URL and page title
  • Page type (service, blog, location, legal, landing page)
  • Organic visits and enquiries over the last 12 months
  • Inbound links from other sites
  • Last updated date
  • Decision: keep, improve, merge, remove

Ask what each page is for

Government content designers distinguish between a proposition audit, which asks what should exist at all, and a content audit, which asks where each piece belongs. The principle is sound for any business: start from the customer need, not from the old site tree. A service page that wins enquiries stays. A 2017 news post about an office move probably does not.

A quick rule of thumb many teams use:

  • Keep pages that earn traffic, links or enquiries.
  • Improve pages with decent demand but thin or dated content.
  • Merge several weak pages on the same subject into one strong one.
  • Remove pages with no traffic, no links and no purpose, and redirect them.

This step is also where an audit of the wider site pays off. If you want a structured method, our guide on how to conduct a website audit covers the checks in more depth, and why website audits matter for UK SMEs explains what they typically uncover.

Step 3: Design the new structure and map every URL

This is the step that decides whether your rankings survive.

Plan the new structure

Sketch the new navigation and page hierarchy before touching the CMS. Group content by what customers want to do, not by how your company is organised. If you are redesigning at the same time, our piece on planning a website redesign shows how structure and conversion goals fit together.

Build the redirect map

Create a two-column sheet: old URL, new URL. Every old URL that has traffic, links or a purpose needs a row. Rules to follow:

  • Map to the closest equivalent. Send visitors to the page that serves the same need, even if the wording and layout differ.
  • Never dump everything on the homepage. Mass redirects to the home page confuse visitors and are treated by search engines as weak signals.
  • Avoid chains. Redirect old URLs straight to their final destination. Google’s redirect guidance recommends keeping chains short, under five hops, and ideally pointing directly to the end page.
  • Use permanent redirects. Server-side 301 or 308 responses tell search engines the move is permanent.

If you want a second, SEO-focused walkthrough of mapping every address, this site migration SEO guide goes into the mechanics of keeping rankings during the process.

Do not use archive pages as a shortcut

It is tempting to replace retired content with a static “archive” link. The GOV.UK team advises against this: a successful transition means users can still find what they were looking for, so redirect to the most relevant live page instead. The same logic applies to a small business site.

Step 4: Move the content

With the audit and map done, the transfer itself is largely mechanical. Decide early whether you will move content by import tool, script or by hand. For sites under about 100 pages, hand-moving and rewriting often gives the best result because you edit as you go.

Whatever method you use, keep these in view:

  • Metadata. Page titles, meta descriptions, canonical tags and image alt text must travel with the content.
  • Internal links. Update links inside your content to point to the new URLs directly, rather than relying on redirects.
  • Structured content. If your new platform uses a different content model, such as custom fields for team members or case studies, document how old fields map to new ones.
  • Media. Check image sizes, file names and formats. Migration is a good moment to compress and rename.
  • Forms and integrations. Enquiry forms, booking tools and CRM connections break silently. List each one and test it.

Use the move to clear technical debt

Google’s guidance on moves without URL changes points out how migration can remove old problems, such as pages blocked in robots.txt or JavaScript routing that search engines struggle to read. Do not copy those faults to the new site. A “lift and shift” preserves every flaw you already had.

Step 5: Test before you launch

Run the new site on a staging address that search engines cannot index (password protection is safer than relying on a noindex tag alone). Then work through this checklist.

Pre-launch checklist

  • [ ] Every row in the redirect map tested, and redirects go straight to the final page
  • [ ] No broken internal links or missing images
  • [ ] Page titles, descriptions and headings carried over
  • [ ] XML sitemap ready, listing only live canonical URLs
  • [ ] Robots.txt does not block the new site (a staging block left in place is a classic launch-day disaster)
  • [ ] Analytics and conversion tracking firing correctly
  • [ ] Forms, phone links and checkout tested on real devices
  • [ ] Mobile layout complete, with the same content as desktop, since Google uses mobile-first indexing
  • [ ] Speed checked on a mid-range phone, not just a fast office laptop
  • [ ] Accessibility and cookie consent tested (see below)

The UK checks most checklists miss

Accessibility

Moving content often exposes old accessibility problems, especially in documents. WCAG 2.2 is the current W3C recommendation, and UK public sector bodies are expected to meet its AA level. Private businesses are not held to the same regulation in the same way, but the Equality Act 2010 expects reasonable adjustments for disabled customers, and AA is a sensible target.

PDFs are the usual culprit. The NHS service manual says creating a new PDF should be a last resort, with an HTML version always provided. When you move your brochures, price lists and guides, ask whether each one should become a normal web page instead.

Brochure content reshaped as structured web page

If you are unsure what a formal audit involves, see our breakdown of UK accessibility audit costs and price bands.

A new site often means new scripts, a new analytics setup and a fresh cookie banner. In the UK, the ICO’s guidance on managing consent in practice makes clear that non-essential storage and access technologies, including tracking scripts and pixels, need consent under PECR and UK GDPR, and that people must be able to refuse as freely as they accept.

Practical consequences for your migration:

  • Check that non-essential scripts stay blocked until a visitor consents. Our walkthrough on cookie banner design that blocks scripts before consent shows how.
  • If you add a new tool or purpose, review your consent wording.
  • Test the banner with a keyboard only. The DWP accessibility manual for developers is a useful reference for the kind of work a front-end build should cover, and a banner that traps keyboard focus makes the site unusable before anyone reads a word.

For wider obligations such as privacy notices and business details, see our guide to UK website legal requirements. If you are not sure whether your current wording is compliant, check with a data protection adviser or the ICO’s own guidance before launch.

Step 6: Launch and monitor

Pick a quiet trading period. Avoid your peak season and avoid Friday afternoons, when nobody is around to fix problems.

Launch day

  1. Switch the live domain or deploy to the new platform.
  2. Turn on the redirects and spot-check your top 50 URLs.
  3. Submit the new sitemap in Google Search Console. If you changed domains, use the Change of Address tool.
  4. Confirm that the robots.txt file is correct and no noindex tags remain from staging.
  5. Re-test forms and tracking on the live site.

The first two weeks

This is when most problems surface. The GOV.UK transition guidance for agencies stresses ongoing review after a move, including fixing mappings where visitors hit dead ends. For your own site, check each day:

  • Search Console coverage and crawl errors
  • 404 pages that are receiving visits
  • Organic landing page traffic against your baseline
  • Enquiry volume and form submissions
  • Page speed and server errors

Some fluctuation in rankings is normal after a move. A sharp, sustained fall on key pages is a signal to check the redirect map first.

How long to keep redirects

Google’s Change of Address tool help says to maintain redirects for at least 180 days, and longer if you still see traffic arriving through them. In practice, if old URLs have inbound links from other sites, keep the redirects indefinitely. They cost almost nothing.

Our website migration SEO checklist sets out a 60-day monitoring routine, and our guide to SEO best practices for UK small businesses helps you build on the new site once it is stable.

A sample timeline for a 50-page business site

The schedule below is an illustration of how the work might be sequenced, not a promise of any particular duration. Your own timeline depends on content volume, approvals and platform.

Stage Indicative time Output
Goals, baseline, inventory Week 1 Scope and spreadsheet
Audit decisions Week 2 Keep, improve, merge, remove list
Structure and redirect map Week 3 Sitemap and URL map
Build and content transfer Weeks 4 to 6 Staging site
Testing and fixes Week 7 Signed-off checklist
Launch Week 8 Live site
Monitoring Weeks 8 to 16 Weekly reports, redirect clean-up

Common mistakes to avoid

  • Forgetting non-page content. PDFs, images and old landing pages carry links and traffic too.
  • Changing URLs without need. Every change adds risk. Keep what works.
  • Redirecting everything to the homepage. Map to relevant pages.
  • Launching with staging settings. A blocked robots.txt or noindex tag can remove you from search.
  • Skipping the content owner. Someone in your business must approve what stays and what goes. If nobody owns it, nothing gets cut.
  • Switching off the old site too early. Keep old hosting and domain registration running through the redirect period.

Our view: migration is a brand decision, not just an IT task

We have spent more than a decade helping business owners build logos, brand identities and websites, and the pattern is consistent. The migrations that go well are the ones where the owner treats the move as a chance to sharpen the message, not just relocate it.

Three things we would tell any owner before a move:

  1. Cut hard in the audit. A smaller site with clear pages usually serves customers better than a large one nobody maintains.
  2. Keep design and technical delivery in the same conversation. When the people who shape the look and the people who handle redirects and data work together, fewer things fall into the gap between them. That single-partner approach is how we work.
  3. Expect to refine. We build in revisions and rapid iteration, because the first version of a new site rarely survives contact with real visitors untouched.

If your logo and visual identity are dated, a migration is also the natural moment to update them, so the new site launches with a coherent brand rather than an old one in a new frame.

— Kukoo

Planning a move? We can help

If you would like a partner who handles both the creative and technical sides of a site move, take a look at our web design and development services. If your site is slow and you suspect it is holding back the move, our £25 Website Speed Improvement is a low-cost place to start. Refreshing your brand alongside the move? See our logo design and visual identity packages.

FAQ

What are the steps in a content migration?

The core steps are: set goals, audit content, design the new structure, map old URLs to new ones, transfer the content, test, launch and monitor. Teams often group these into pre-migration, migration and post-migration phases. The audit and the URL map are the two steps that most affect your search performance.

How long does a website content migration take?

It depends on the number of pages, the complexity of the platform and how quickly you approve decisions. A small business site can often be planned, built and tested in a matter of weeks, while larger sites take longer. Allow monitoring time after launch on top of that.

Will I lose my Google rankings when I migrate?

You may see short-term movement, and nobody can promise zero change. You reduce the risk by keeping URLs where possible, redirecting every old address to its closest equivalent, and fixing problems quickly after launch. Google’s site move documentation sets out the recommended process.

Do I need to redirect pages I am deleting?

If a page has traffic, inbound links or a close equivalent, yes: redirect it to the most relevant live page. If it has none of these, a standard not found response is acceptable. Avoid sending every deleted page to the homepage.

Sources