Content Migration: How to Keep Digital Clutter Out of Your New Website

Packing for a move forces a decision about every single object. Does this deserve a spot in the new place, or has it been taking up room because throwing things out is a chore? The broken chair finally goes to the curb. The duplicate kitchen gear gets donated. What arrives at the new house are the things worth carrying.

If a migration is on your calendar, a content cleanup is probably already somewhere in the plan. The question is how far it goes. In a light pass, someone deletes dead pages and fixes broken links before launch. In a full audit, someone decides whether every page deserves a spot on the new site at all. Skip the full audit and the new design launches wrapped around the same digital clutter the old site had.

This article covers content migration as a chance to clean house. It makes the case against moving everything, then walks through a six-step cleanup to run before your content enters the new content management system (CMS).

1. What is content migration?
2. Why you shouldn’t migrate every page to the new site
3. How to audit and clean your content before a migration
4. Why a Drupal migration is the right time for a content cleanup
5. How to keep the new site clutter-free after launch
6. Planning a migration? Where a Drupal partner fits in

What is content migration?

Content migration is the process of moving your content, meaning pages, files, images, and their metadata, from one website or CMS to another. It comes up in three common situations: 

1. A website redesign on a new instance of the same platform
2. A platform switch such as a WordPress to Drupal migration
3. A non-trivial version upgrade, like leaving Drupal 7 or a legacy Sitecore installation

There are two ways to approach it. A lift and shift copies everything over exactly as it is or a migrate-and-improve approach audits the content first and moves only what earns its place. 

The first can be faster to plan and more expensive to live with; the rest of this article makes the case for the second and shows you how to run it.

One scope note before we start. This article assumes the move is already decided. If you’re still deciding whether to migrate, that question has its own considerations, from platform costs to integration needs, and we’ve covered it separately.

Why you shouldn’t migrate every page to the new site

Every page you migrate costs money twice. Once during the migration, when someone has to move it and check it. And again after launch, when someone has to keep it accurate for as long as it stays live. The cheapest page in a migration is the one you delete before it starts.

How much is there to delete? We once audited a nonprofit website that had grown past 400 pages, and two thirds of it could be eliminated or combined. 

That ratio won’t hold for every site, but it gives a sense of how much a website can accumulate in a few years without anyone deciding to keep it.

The extra weight causes three problems.

1. Outdated and duplicate content weakens your search rankings

Search engines assess a site as a whole, and thin or duplicated pages drag on that assessment.

Three near-identical service pages split their ranking signals three ways instead of concentrating them in one strong page, and a large share of stale, low-value pages affects how crawlers treat the pages that matter. 

Migrate that content unchanged and the penalty transfers to the new site, which turns a design project into a search engine optimization (SEO) problem.

2. Cluttered navigation makes it harder for visitors to find what they need

Every stale page competes with the useful ones. On-site search returns the 2019 version of a program page next to the current one, and menus grow extra levels to accommodate sections that stopped mattering years ago. A government site that carries four versions of the same form leaves visitors guessing which one is current.

3. Every migrated page adds cost, during the migration and after it

Migration effort scales with volume. More pages means more URL mapping and editorial review, and on a Drupal migration, more content modelling decisions. A 2,000-page site costs meaningfully more to move than an 800-page site that serves the same audiences better.

Every page that survives the move needs an owner and updates when facts change. Content nobody maintains goes stale on the new site the same way it did on the old one.

How to audit and clean your content before a migration

The cleanup runs in parallel with design and development, so it doesn’t have to extend the migration timeline. Here are the six steps, in the order they should happen.

Step 1: Build a content inventory of every page, file, and asset

Start by listing everything the site holds. A site crawler gets you the pages, and a CMS export fills in what crawlers miss, like unpublished drafts and files sitting in the media library. For each item, capture the title, content type, owner if one is known, and the last updated date.

An inventory and an audit are different things. The inventory is the quantitative record of what exists. The audit, which begins in step 3, is the qualitative judgment about what deserves to survive the move, and you need the first to do the second.

Step 2: Add performance data to the inventory

Now layer evidence onto the list.

• Analytics: Pageviews, entry rates, and conversions over the past twelve months.
• Google Search Console: Which pages earn impressions and clicks, and for which queries.
• SEO tooling: Which pages hold backlinks worth preserving.

This turns “we think no one reads this” into a column you can sort by. It also sets the benchmark you’ll measure the new site against after launch.

Step 3: Flag ROT content (redundant, outdated, trivial)

ROT stands for redundant, outdated, and trivial, and it’s a useful lens for a content audit.

Redundant content says the same thing as another page, like three overlapping service descriptions or a policy that lives in four departments’ sections. Outdated content was accurate when it went up, and the event page from 2022 or the bio for someone who has left both qualify. Trivial content never carried its weight in the first place, like the post announcing that the website has a new look.

Tag each inventory row with its ROT status. The flagged rows become the shortlist for the next step.

Step 4: Decide what to keep, rewrite, consolidate, archive, or delete

Every row gets one of five verdicts:

• Keep: The page is accurate, performs well, and has a clear audience. It migrates as-is.
• Rewrite: The topic earns its place, but the content is stale or thin. It migrates after an update.
• Consolidate: Several weak pages cover one topic. They merge into a single strong page.
• Archive: The content has record-keeping or compliance value but no active audience. It moves out of navigation and search, into an archive section or offline storage.
• Delete: No one reads it and nothing requires you to keep it. It doesn’t come along.

The decisions on what to delete or consolidate can meet pushback from page owners, because merging or removing a section can look like a department losing its place on the new site. When that happens, go through the inventory with the owner and look at the past year of traffic together. If the pages drew almost no visits, the evidence suggests the page can be deleted. 

If the owner knows something the numbers miss, like a legal requirement or a small audience the organization is obligated to serve, change the verdict to keep or archive and note the reason in the inventory.

Step 5: Map redirects for every URL you remove or merge

Redirect mapping is a spreadsheet with two columns: every URL that won’t exist on the new site, and the page that should answer for it. Build it from your step 4 verdicts, before launch rather than after the traffic dips. Consolidated pages point to the merged page, deleted pages point to the closest relevant parent, and any changed URL structure gets mapped page by page.

Plan to keep the redirects live for at least 180 days, longer if the old URLs still draw search traffic. A mid-sized site takes a few weeks to settle in Google’s index after a move, so hold judgment on the traffic numbers until it does.

The redirects are also what makes consolidating and deleting safe for search. A permanent redirect passes a page's ranking value to its destination, so a merged page keeps what its parts earned. Rankings drop when pages disappear with no redirect behind them.

Step 6: Assign an owner and review date to every page you keep

The final step adds two more columns to the inventory. Who owns this page, and when does it get looked at next? A page with an owner and a review date is governed content. A page without either is future clutter, whatever shape it’s in today.

This is also where the inventory stops being a migration document and becomes an operating document. Keep it alive after launch.

Why a migration is the right time for a content cleanup

A platform move forces content decisions whether you plan them or not. The new CMS has its own content types and templates, so someone has to work out how each kind of page gets rebuilt in the new system. Since that thinking is happening anyway, deciding what deserves to be rebuilt costs little extra, and it saves migration budget on every page you leave behind.

Sometimes the platform itself sets the deadline. Drupal 7 reached end of life in January 2025, and legacy versions of other systems, Sitecore among them, are in the same position. Staying put means running without security patches, so these sites face a decision between extended support, a rebuild, or a switch to a different CMS. The second and third mean redefining the content model from scratch.

A switch between platforms raises the same question. Every post and page has to be restructured into the new system's content types, either manually or through a migration script someone has to configure. Each page you migrate is a page someone touches, and each page you retire is one less to pay for.

Whatever your starting point, attention and budget are already on the site, and there is no better time to run the audit.

How to keep the new site clutter-free after launch

The audit fixes the symptom. Content governance prevents the relapse, and it’s cheapest to set up while the migration has the organization’s attention. Without it, the new site accumulates clutter at the same rate the old one did, and the next redesign starts from the same place. Three practices cover the essentials.

Set publishing workflows and content ownership

Every content type gets a named owner and a defined path from draft to published. Drupal supports this natively through roles, permissions, and editorial workflows, which matters on sites like a university’s, where dozens of editors publish across departments. When publishing requires an owner, orphaned content stops at the door.

Create an archiving policy with expiry dates

Time-sensitive content should carry its expiry date from the day it’s published. Give news posts and campaign landing pages a review-or-remove date in the CMS, so retiring them is routine rather than a rescue project years later. Drupal can automate much of this with scheduled unpublishing.

Schedule recurring content audits

The first audit is the expensive one because it starts from zero. Keep the inventory current and the follow-ups get cheap. A yearly or twice-yearly pass re-sorts the list by traffic and flags new ROT, and a maintained inventory turns the next migration, whenever it comes, into a checklist instead of an excavation.

Planning a migration? Where a partner fits in

The content decisions in this article belong to your team, because your team knows the audiences and the history behind each page. A partner handles everything around those decisions, from the migration engineering to the judgment calls about what to automate.

Our migration services include planning which content migrates automatically, which moves by hand, and how legacy URLs stay preserved through redirects. 

If you’re heading into a migration and want help scoping the content side, get in touch. We’re happy to look at the site with you and help figure out how much of it deserves the trip.