The Structured
Migration Approach
A framework built for learning
Naming these patterns is advantageous. Having an approach to avoid them is critical to the migration's success. The Structured Migration Approach (SMA) is a five-phase framework designed to address each of the patterns described in Part One, while maintaining the pace and momentum that large migration programmes require.
The SMA is not a waterfall methodology. It does not ask you to resolve all unknowns before you begin. Instead, it creates the conditions for organic, wave-based progress - where each phase builds on real learning from the last, and the programme grows in confidence and capability as it moves forward.
Guiding principle
A migration is a learning programme with a destination, not a logistics programme with a deadline. The destination is fixed. The route is discovered.
The five phases
1. Align
Establish a shared understanding of what the migration is for, and why it matters.
Before any technical work begins, the organisation must align on strategic intent. This means educating stakeholders on what the migration involves, articulating the business case clearly, and ensuring that every leader who will be asked to support the programme understands what success looks like. This phase is not about producing a detailed plan - it is about creating the conditions for good decisions throughout the programme.
Risk check: Conflicting priorities among senior stakeholders will surface as fragmented ownership later. Address disagreements here, not on the programme.
2. Scope
Select a test set and build the case for it.
Rather than planning the full migration upfront, this phase focuses on identifying the right candidate assets for a deliberate, bounded test migration. This means choosing a small set of workloads, datasets, or processes that are representative enough to generate real learning - typical enough to surface the problems you will encounter at scale - but limited enough that the consequences of mistakes are recoverable. Think of it as choosing what to test before you test it.
A total cost of ownership analysis and business case are developed here, giving leadership the confidence to commit resources. The output of Scope is not a migration plan. It is a test design.
Risk check: The temptation to expand the test set at this stage is a precursor to All-or-Nothing Planning. A larger test set feels like more progress. It is actually less learning at higher risk.
3. Pilot
Execute the test migration, learn from what happens, and embed those lessons before scaling.
The Pilot is where real migration work begins. It is deliberately limited in scope - not because ambition is lacking, but because a smaller surface area means unexpected problems are recoverable and the learning is cleaner.
The goal is not simply to move the first set of assets. It is to learn how this particular organisation migrates. Treat it explicitly as a discovery phase: before the first asset moves, surface and document the assumptions made during Align and Scope - about data quality, system behaviour, governance complexity, and stakeholder expectations. Many will not hold. Every assumption that breaks in the test set is one that would have broken at scale, at far greater cost.
Bring subject matter experts and end users in during the Pilot, not after it. People articulate what they actually need far more accurately when responding to something concrete than when asked to describe it in the abstract. A working migration of real assets (even a small, imperfect one) will surface requirements, edge cases, and constraints that no requirements document would have captured.
That learning only generates value if the programme has the agility to act on it. Build explicit review points into the transition from Pilot to Scale. The question is not only "what did we learn?" but "what are we changing as a result, and how will we know it worked?"
The people who run the Pilot carry institutional knowledge that no handover document can fully transfer. Invest in upskilling them during this phase, not just managing them through it.
Risk check: Governance structures often react to the pace of a well-run Pilot by adding controls. This is the point at which the Control Instead of Enablement pattern typically emerges - watch for it, and address it structurally rather than working around it.
4. Scale
Apply the lessons from the pilot to successive waves, growing capability and coverage organically.
With a proven approach and a team that has learned through doing, the migration expands. This is not a big bang - it is a series of increasingly confident waves, each building on the last. New teams are brought in and upskilled. A Centre of Excellence or equivalent knowledge-sharing structure is established to prevent fragmentation as the programme grows. Governance is redesigned for the new environment, replacing manual controls with automated safeguards wherever possible.
Risk check: As success attracts attention, stakeholders who were previously disengaged will seek to impose their own governance requirements. Maintain alignment with the original strategic intent and resist scope distortion.
5. Improve
Treat the migrated estate as a product, not a completed project.
Migration does not end when the last workload is moved. The organisations that realise the most value from transformation are those that continue to improve after migration - identifying what was done under pressure that can now be done properly, and maintaining the discipline of continuous improvement. Teams should be empowered to flag and address technical debt rather than accumulating it. The programme should remain connected to business objectives, not drift into a purely operational mode.
Risk check: The four patterns can re-emerge at this stage - particularly lift and shift habits as other parts of the business seek to replicate the migration approach without the underlying rigour. Protect what was built.
Quick reference: patterns & responses
A final note
The four patterns in this guide are not signs of organisational failure. They are signs of organisational pressure: the pressure to move fast, to show progress, to manage risk. Every one of them makes sense in the moment. The problem is what they cost over time.
The Structured Migration Approach does not eliminate that pressure. It creates a structure that absorbs it - a way of moving fast without losing direction, of managing risk without stifling the people doing the work.
The organisations that navigate migrations well are not the ones with the best plans. They are the ones that learn the fastest and adjust accordingly. The SMA is designed to make that possible.
ABOUT ICP
Too many companies face too many limitations when trying to build consistent brand experiences. ICP helps global companies get control of their content operations.
We guide the world's top brands with solutions across data & automation, creative operations, production, content management & logistics and digital shelf enablement so our clients can achieve a frictionless flow of content through all their systems and channels.
It's time to content confidently. And to do that, you need three things: more insight with disruptive thinking, more capabilities for everything to do with making, managing and delivering content, and a flexible approach to open up more possibilities.
The world's most beloved brands from Coca-Cola to Unilever to NBCUniversal all rely on us to guide and support their content operations. Our clients are seeing impressive results, like increasing speed to market by 20%, saving $10 million annually in legal fees and efficiencies, and improving profits through more consistent and higher quality brand communication. Learn more about our story