Website Content Migration: A Plan for Small Businesses

Website content migration means moving your text, images, files and page structure from your old website to a new one without losing what already works. Done well, you keep your search rankings, your best pages and your customers’ trust. Done badly, you lose all three in a weekend. The difference is almost always the plan you make before anyone touches the new site.

This guide walks you through that plan in the order we would do it for a small business: audit, decide, map, move, test, launch and monitor.

TL;DR

• Content migration is moving pages, media and structure to a new site or platform. A full website migration can also change the domain, design or hosting.
• Audit first. Decide page by page whether to keep, update, combine, redirect or retire.
• Build an old-to-new URL map before you migrate, and use permanent server-side redirects for every URL that changes.
• Change one major thing at a time where you can, keep staging out of search results, and crawl the new site on launch day.
• Expect some ranking movement while Google recrawls. Monitor Search Console for the weeks that follow.

Table of Contents

• What website content migration actually means
• Build the plan before you move anything
• Audit your content and decide what moves
• Plan the new structure and map every URL
• The migration steps, in order
• Migrate without losing your search rankings
• Time and cost: what moves the number
• Our perspective
• How we can help
• FAQ
• Sources

What website content migration actually means

Content migration is the act of moving your content from one place to another: pages, blog posts, images, PDFs, metadata and the way they connect. It is one piece of a broader website migration.

Search Engine Land describes a website migration as a project where the structure or content hierarchy of a site changes significantly. Common examples are a domain change, a redesign, a consolidation or a move to a new platform. Google sorts site moves into two groups in its site moves guidance: moves where URLs stay the same but the infrastructure changes, and moves where the protocol, domain name or URL paths change.

Why does the distinction matter? Because it tells you how much risk you are taking on. Moving your pages to a new theme on the same domain with the same URLs is a smaller job than changing platform, domain and page paths at once. Know which one you are doing before you plan anything else.

Build the plan before you move anything

A content migration plan is short. It answers who does what, what moves, in what order and how you will know it worked. A good plan covers scope, owners, timeline, risks, approvals and success measures before launch, as laid out in this content migration plan guide.

Assign owners

Even a three-person business needs named owners. One person can wear several hats, but each job should have a name next to it:

• Content decisions: who decides what stays, changes or goes.
• URL mapping and redirects: who owns the old-to-new map.
• Implementation: who moves or rebuilds the pages.
• Project management: who keeps the schedule and approvals.
• Subject-matter review: who confirms services, pricing language and legal wording are still correct.

That split follows the recommendation in the same guide to assign separate owners for content decisions, URL mapping and redirects, migration work, project management and expert review. If you hire a studio, the studio takes the implementation and project management roles, and you stay the final voice on what your business says.

Separate three kinds of questions

A useful way to think about it comes from Deane Barker, who frames migration as three different problems: the editorial question of what changes, the functional question of how content works in the new system, and the procedural question of how and when the data moves. Moving the files does not guarantee the content stays useful or behaves correctly in its new home. A pricing table that looked right in the old editor can break in the new one. A form can stop sending leads to your inbox. Plan for each of those questions on its own.

Set success measures

Pick a few numbers you can check after launch: organic visits to your top ten pages, form submissions, phone-call clicks, and the number of pages Google reports as indexed. Record the numbers before the move so you have something to compare against.

Audit your content and decide what moves

The audit is where a migration is won. Most small business sites carry old service pages, thin posts, duplicate pages and files nobody has opened in years. A new site is the best chance to clean that up.

Build the inventory

Start with a spreadsheet. One row per URL. A thorough inventory, as suggested in the migration plan guide, records the current and new URL, title, content type, place in the sitemap, metadata, H1, canonical and indexability status, links, backlinks, traffic, conversions, owner, approval, decision, redirect status and QA status.

For a small site you can trim that list. At minimum, keep:

• Current URL and planned new URL
• Page title and meta description
• Monthly visits and any leads the page produces
• Decision (keep, update, combine, redirect, retire)
• Redirect done (yes or no) and QA done (yes or no)

Find every URL

Do not rely on your navigation menu to tell you what exists. A complete URL list can combine a live crawl with analytics, Search Console, CMS data, log files, sitemaps and backlink tools, according to Screaming Frog’s migration tutorial. The same page notes that if you cannot map every URL right away, you should prioritize the high-value ones. For a small business that usually means your home page, service pages, location pages and any blog post that brings in steady traffic or backlinks.

Decide page by page

For each URL, choose one outcome:

Use quality, performance and SEO value as your criteria. If a page has no traffic, no links and no purpose, let it go. If you want a content-by-content review list, our website content checklist for small business covers what each page should contain.

Plan the new structure and map every URL

Let your business priorities shape the new site, not the old menu. Ask what you most want a visitor to do: call, book, request a quote. Then give those pages a short path from the home page. If you are still deciding how the new site should be organized, our guide to planning a website redesign project walks through sitemap and page planning.

The URL map

The URL map is the most important document in the project. Google’s site move guidance says to map old URLs to their new destinations, update canonical and hreflang annotations, internal links and the sitemap, and use server-side permanent redirects for changed URLs. It also says not to redirect unrelated old pages to the homepage. The guide on content migration planning agrees that the map should exist before migration begins, so it can drive both the redirects and the internal-link updates.

A simple example for a landscaping company:

If you want a second explanation of why a redirect map protects rankings during a redesign, this write-up on keeping rankings with a redirect map is a good companion read.

Keep the URLs you can

The safest URL change is no URL change. If an old address is clean and sensible, keep it. Every address you keep is one less redirect to maintain and one less thing that can go wrong.

The migration steps, in order

1. Freeze the old content. Agree on a date after which nobody edits the old site, or keep a change log so late edits reach the new one.
2. Back up everything. Take a full copy of files and the database before any work starts.
3. Set up staging. Build and load content on a private copy of the new site. Keep that copy out of search engines. Screaming Frog recommends restricting staging sites from crawling and comparing a staging crawl with a live-site crawl to spot unexpected changes.
4. Choose automated or manual migration. The CMS Critic best-practice guide lists this as a core decision. A site of 30 pages is often faster to rebuild by hand. A large blog may need an import tool.
5. Move and clean the content. Check headings, links, image alt text, embedded forms and file attachments as you go. Not everything exports cleanly. Our piece on moving from Squarespace to WordPress shows how much can be left behind on an export.
6. Carry over metadata. Titles, meta descriptions, canonical tags and image descriptions are easy to forget and costly to lose.
7. Test. Check how pages display across browsers and devices, run every form, and click every menu item. The CMS Critic guide lists cross-browser and device testing as part of the plan.
8. Install the redirects from your URL map on the live server.
9. Launch, then crawl the new site right away.

For the final check before going live, use our website launch checklist for small business.

Change one big thing at a time

Google recommends changing one major variable at a time where practical, for example separating a domain move, a CMS change and a layout change, because it makes problems easier to diagnose. If you can keep your domain while you change platform and design, do. If you must change several at once, expect a longer troubleshooting list.

Move everything at once

Google says small or medium sites should generally move all URLs at the same time, while large sites may move in sections so monitoring is easier. For a small business, that means one clean launch, not a slow trickle of pages.

Migrate without losing your search rankings

Your rankings are the part of the old site that is hardest to rebuild, so protect them on purpose.

• Use permanent redirects. Google recommends server-side permanent redirects such as 301 or 308 when URLs change, with each old URL sent directly to its final, relevant destination. Avoid chains where A goes to B goes to C.
• Update what points at your pages. Internal links, canonical tags and your XML sitemap should all use the new URLs.
• Prepare launch rules. Make sure your robots rules and noindex tags on staging do not carry over to the live site. This is a common cause of a site vanishing from search after launch.
• Crawl at launch. Screaming Frog suggests crawling the new site at launch to check crawlability, indexability, robots directives, noindex and nofollow rules, titles and canonicals.
• Watch Search Console. Google says permanent redirects do not lose PageRank, but rankings can fluctuate while pages are recrawled and reindexed. A small dip in the first weeks is not a reason to panic. A sudden cliff is a reason to check your redirects and robots rules.

If something does look wrong after launch, this guide to migration testing and troubleshooting can help you work through the common causes.

Time and cost: what moves the number

Nobody can quote a fair price for a migration without seeing the site. Three factors drive the workload, as described in The Web Project Guide: how much content there is, how much of it must be transformed, and whether the migration is automated or manual.

In practice:

• Volume. Fifteen pages and 400 blog posts are different projects.
• Transformation. Content moving between similar platforms needs little reshaping. Content moving into a new layout, new page types or a new design needs hands-on work.
• Cleanup. Every “update” and “combine” decision in your audit adds writing and review time.
• Testing and redirects. These are small on a tiny site and significant on a large one, but they are never optional.

The practical tip: do your audit first. A clear inventory and a clear set of decisions turns a vague estimate into a defined scope, and it is the single best way to keep a migration on budget. If you are weighing whether the whole project is worth it, read about updating an outdated small business website.

Our perspective

I have seen the same mistake many times: a business treats migration as a copy-and-paste job at the end of a redesign. Then launch week arrives, the old URLs are gone, the best-performing page is missing and nobody can say why the phone has gone quiet.

We build the other way around. Every project is bespoke, with no templates, so the content plan starts with your actual business: which pages bring in customers, which ones explain what you do, and which ones are just taking up space. The strategy comes first, and the design and the move follow from it.

You also work directly with me, the creative director, from the first audit to launch day. The person who decides what stays and what goes is the person who builds it, so nothing gets lost in a handoff.

And everything we create for you is yours. There are no ongoing licensing requirements and no vendor lock-in, so you can take your content and assets wherever your business goes next.

Charles

How we can help

If you would rather not manage a spreadsheet of URLs, redirects and QA checks on your own, that is the kind of work we do for small businesses. We handle the content audit, the new structure, the build and the launch, with direct access to the creative director throughout.

See how our website redesign services work, or learn more about web design and development. You can also start from our home page and tell us about your site.

We will look at what you have, tell you what is worth moving, and build a plan that fits your business.

FAQ

How long does a website content migration take?

It depends on the amount of content, how much needs rewriting or reformatting, and whether tools or hands do the moving. A small site with a clean audit can move in a few weeks. Larger sites with many posts, files and redirects take longer, and testing time should be added to any estimate.

Will I lose my Google rankings when I migrate?

You should not lose them if the migration is handled carefully. Google says permanent redirects do not lose PageRank, though rankings can fluctuate while it recrawls and reindexes the new pages. Map every old URL, use 301 or 308 redirects, and monitor Search Console after launch.

Should I move all my content or just the best pages?

Move what serves your customers and your business. Decide page by page whether to keep, update, combine, redirect or retire each URL. Pages with no traffic, no backlinks and no purpose can be retired, which gives the new site a cleaner start.

What is the difference between content migration and a website redesign?

A redesign changes how the site looks and is organized. Content migration is the work of moving the existing text, media and structure into that new site. Most redesigns include a migration, which is why the two should be planned together.

Who should be involved in a migration at a small business?

At least one person who decides what the content says, one who owns the URL map and redirects, and one who builds or moves the pages. A single owner can hold several of these roles, but each job needs a name. A studio can take on the build and project management.

Sources

• Making site moves easier, Google Search Central Blog
• Site Moves and Migrations, Google Search Central
• Website migrations: a plan to keep your traffic and SEO safe, Search Engine Land
• Website Content Migration Plan, SlickPlan
• How To Use The SEO Spider In A Site Migration, Screaming Frog
• Best Practices: Migrating Content to a New CMS, CMS Critic
• Migrate and Populate the Content, The Web Project Guide
• Website Redesign SEO: Keep Your Rankings With a Redirect Map