Migration & Modernisation
A structured, de-risked path from on-prem to AWS.
Most cloud migrations derail on the same three things: scope that wasn't understood upfront, costs that emerged after contracts were signed, and timelines that slipped once real dependencies surfaced. The Migration Acceleration Program is the AWS-endorsed methodology built to prevent all three. We run every migration through it because the structure isn't bureaucracy — it's what keeps delivery on track.
Sound familiar?
The conversations that usually bring people to us.
"We've been talking about migrating for two years. Nothing has moved because nobody could give us a real scope, a real risk assessment, or a real number."
"Our last quote was based on a spreadsheet. When discovery actually started, the number was very different. We need someone who assesses before they quote."
"The board wants a business case with a real cost, a real timeline, and a clear plan — not a range, not a theory. We don't have that yet."
Before MAP Assess
Not sure what AWS will fund?
A 30-minute Migration Funding Review determines your MAP eligibility and gives you the full funding picture — how much MAP Assess support you qualify for, and what that unlocks in Mobilise and Migrate. No cost, no obligation.
The MAP framework
Three phases. Each one gates the next.
Nothing moves to production until the prior phase is complete. That sequencing — enforced, not optional — is what keeps MAP migrations on track when ad-hoc migrations aren't.
Phase 01
Assess
- Rapid discovery & inventory
- Application dependency mapping
- Migration Readiness Assessment
- TCO & business case
- Briefings & immersion days
- Portfolio scoring (7Rs)
Phase 02
Mobilise
- Discovery & migration planning
- Landing Zone & account structure
- Security & compliance baseline
- Operating model design
- Skills & centre of excellence
- Pilot migration (non-critical)
Phase 03
Migrate & Modernise
- Wave-based migration execution
- Cut-over & rollback management
- Post-migration validation
- Operate & optimise
- Modernise in-flight (7Rs applied)
- On-prem decommission
What each phase delivers
Not just activities — tangible outcomes at every gate.
Phase 01
Assess
Typically 2 – 4 weeks
We map your entire environment before a number is quoted. Discovery is tool-assisted, not spreadsheet-driven — dependency mapping, readiness scoring, and cost modelling happen in parallel, not sequence.
You walk away with
- A prioritised migration portfolio sequenced by dependency and risk
- A board-ready business case with a real cost range and timeline
- A Migration Readiness Assessment — gaps documented before they become surprises mid-project
- A fixed-scope proposal for the phases ahead, priced on what we found — not what we assumed
Phase 02
Mobilise
Typically 4 – 8 weeks
We build the cloud environment that receives your workloads — account structure, security baseline, network topology, operating model — before anything production moves. Teams that skip this phase spend the rest of the migration retrofitting governance.
You walk away with
- A Landing Zone — multi-account structure, guardrails, and security controls before anything production moves
- A tested migration factory: the repeatable runbook every wave follows
- A pilot migration on a non-critical workload to surface integration issues before they're on the critical path
- A sequenced wave plan with owners, timelines, and cutover windows locked in
Phase 03
Migrate & Modernise
Wave-based execution
Workloads move in planned waves. Each wave: plan, execute, test, cut over, stabilise, retire on-prem. We apply the right strategy per workload — rehost, replatform, refactor, or retire — rather than lifting everything identically.
You walk away with
- An AWS environment your team owns, understands, and can operate without calling us for every change
- On-prem costs declining wave by wave as dual-running infrastructure is decommissioned
- Applications right-sized for the cloud — treated with the right strategy per workload, not lifted identically
- Documentation, runbooks, and diagrams produced throughout the engagement, not on the last day
Why Nuvrix for MAP
Where most migrations fail — and what we do differently.
Most migration risk doesn't come from technical complexity — it comes from misaligned expectations, underestimated dependencies, and teams that understand the technology but not the business behind it. We bring engineering, delivery, operations, and commercial depth together in one engagement.
Architecture & engineering depth
Our team has designed and delivered cloud infrastructure at scale — not advised on it. Landing Zones, security baselines, migration factories, operating models: we've built them. That means we know where things break in practice before they break on your project.
Operational background
We've run cloud operations post-migration — which means we design migrations with the operational team in mind from the start. Runbooks, monitoring, escalation paths, and documentation aren't afterthoughts. They're built in because we know what happens when they're not.
Business and commercial understanding
A migration that delivers technically but can't demonstrate business value to the board has failed. We scope every engagement around measurable outcomes — cost reduction, risk reduction, operational headroom — and we build business cases that hold up to scrutiny, not just ones that win initial approval.
AWS partner ecosystem fluency
We know how the AWS partner ecosystem operates — including where and how MAP funding flows, how to engage AWS account teams effectively, and how to access the right AWS resources at each phase. We work alongside MAP-credentialed partners where the engagement benefits from it.
De-risked scope and delivery
We assess before we quote. The fixed price for Mobilise and Migrate is set after the Assess phase — not before. Scope is based on what we found, not what we assumed. That's the mechanism that keeps migrations on budget.
Honest about fit
If MAP isn't the right approach for your situation — or if the timing isn't right — we'll say so. We'd rather have that conversation upfront than run an engagement that isn't set up to succeed.
Ready to scope your migration properly before committing to it?
A 30-minute conversation is usually enough to understand your situation, identify the real risks, and tell you whether MAP is the right framework. You'll hear back from someone who's done this before.