The migration that went perfectly and fixed nothing
The migration launched on time and within budget, with steering committee approval. Six months later, the content team continued facing the same issues as before, now on a faster and more expensive platform.
Nothing went wrong technically. That is the point.
(This example reflects a common pattern we observe, not a single client.)
Migration readiness is a programme condition
Most disappointing migrations do not fail due to technology. They fail on scope.
Organisations often migrate what exists rather than deciding what should exist. This results in a technically successful migration that transfers content debt, governance gaps, and operating model limitations to a faster, more expensive platform.
These issues are both predictable, and they are avoidable. Neither switching platforms nor migrating content resolves them.
Here’s what that looks like in practice. Across the programmes we’ve delivered, a content audit before migration typically removes 40 to 60% of the content teams assumed they had to move. That’s cost, time and technical debt you never carry across.
Four conditions that must be true before anything moves
These are not sequential steps but four simultaneous conditions. All must be met before migration tooling can begin.
1. A rationalised content library.
Each item is designated to migrate, be redesigned, or be retired. This classification occurs before migration, not during or after.
Common issues include duplicate content, outdated campaign pages, and regulated content that has not been reviewed for relevance.
2. A standardised content model.
Migration tooling maps content to templates and fields. Inconsistent models produce inconsistent results, and manual corrections at scale are costly.
In multisite implementations, global templates often drift as they are adapted for specific needs. This is usually hidden on the current platform but becomes apparent when migration tooling is run.
3. A defined governance framework.
What can AI generate without review? Where can it assist if human approval is required? What are off limits?
Often, there is no governance framework in place, and the time required for multifunctional alignment is significantly underestimated.
4. An established delivery baseline.
Modern SaaS platforms are generally deployed via pipelines only, with no direct server access.
Typically, strong engineering teams rely on practices such as direct server access for deployment and debugging, which gradually become unavailable.
Why the least exciting job pays the most.
Pre-migration work focuses on preparation, while migration emphasises progress. Prioritising progress over preparation is often the costliest mistake in large programmes.
- Auditing the component library before rebuilding typically reduces the scope of component rebuild by 35 to 40%.
- Identifying delivery or configuration gaps during migration, rather than beforehand, typically results in a loss of 2 to 6 weeks mid-delivery.
Pre-migration work is the most effective way to control cost and time.
Test yourself in two minutes.
Answer yes or no based on your own knowledge. If you would need to ask someone, count it as a no.
- Could someone in your organisation tell you today how much of your digital content is out of date, duplicated or unused?
- Do your business-unit teams all structure the same kind of content the same way, or has each adapted its own?
- Could your legal, risk and marketing leads agree in a single meeting on what AI is and isn’t allowed to publish?
- When something breaks on your live platform, is it fixed through a controlled release process, or does someone go in and change it directly?
Scoring
(Count a yes for Q1 if someone could tell you, for Q2 if all teams work the same way, for Q3 if they could agree, and for Q4 if fixes go through a controlled release.)
4 yes: You’re better placed than most. The conversation is about sequence.
2 or 3 yes: You are aware of the gaps. It is better to address them now than to encounter them during delivery.
0 or 1 yes: You can still achieve a successful outcome, but not by starting with the platform.
Migrate with intent, not with default
The default approach is to move existing content. An intentional approach focuses on building what is needed. For large organisations with complex content and compliance requirements, only the latter is viable.
Next in the series (Part 2):
You now know where you are exposed, Part 2 covers the sequence: what to fix first, what to defer, and why order matters more than budget.
If you have a migration planned for your 2027 roadmap and would like to assess your readiness, book a readiness conversation →