What’s included
What’s included
Discovery and dependency mapping
An inventory of applications, data and integrations, with the dependencies that decide what has to move together.
Built with
- AWS Transform
- AWS Pricing Calculator
- AWS Control Tower
- AWS Well-Architected Tool
Why it matters
Why it matters.
Most migrations stall on sequencing, not on technology.
Moving the wrong workload first costs months and the business’s confidence.
A dependency map and a costed business case turn the migration into a decision leadership can fund, not a leap of faith.
Every workload gets a clear path, from rehost to retire, so modernisation effort goes where it pays.
What’s included · how it runs
Discover. Assess. Plan. Present.
Step 01
Discover
Interview stakeholders, collect the inventory and map application dependencies.
What’s included
Discovery and dependency mapping
An inventory of applications, data and integrations, with the dependencies that decide what has to move together.
Step 02
Assess
Score every workload and choose its migration path.
What’s included
Portfolio assessment
Each workload scored on value, complexity and risk, with its path: rehost, replatform, refactor, retain or retire.
Step 03
Plan
Design the landing zone, group workloads into waves and cost the move.
What’s included
Business case
Run cost on AWS against today’s estate, including licensing, effort and what modernisation saves.
Step 04
Present
Walk leadership through the business case, the roadmap and the first wave.
What’s included
Migration roadmap
Wave plan, landing zone design, and the team, timeline and budget to deliver it.
What you walk away with
- Application and dependency inventory
- A migration path for every workload
- Costed business case
- Wave plan and roadmap
Case studies
Customers we’ve delivered this for.
Draft · pending Repurpose.io approval
Case studyRepurpose.io
A platform that scales with demand.
We moved Repurpose.io to containerised workloads on Amazon ECS with AWS Fargate, modernised the database on Amazon Aurora and automated delivery with CI/CD and infrastructure as code.
- Industry
- SaaS, content automation
- We moved
- Amazon ECS on AWS Fargate, Amazon Aurora
- Availability
- 99.9% SLA
Case studyLyrebird Health
[Outcome headline, pending client approval].
[How the client got the outcome: what Assembly built and where it runs. One sentence.]
Talk to an engineer[Client logo][First Last][Role]
Case studyDistro.io
Ship features faster on AWS.
How Distro.io modernised the platform behind its web applications on AWS: containers, automation and a scalable core, so new features reach customers about 70% faster.
Read the case studyAWS Migration Services Competency
Assess. Mobilise. Migrate.
We migrate on the AWS Migration Acceleration Program (MAP) method, with the AWS Migration Services Competency through our partnership with Ingram Micro. Three phases, each with a clear exit before the next begins.
Migration Services Competency
Run on the AWS Migration Acceleration Program (MAP) method
* Via Ingram Micro
Assess
Readiness, portfolio and a costed business case: what moves, in what order, at what cost.
Our service
Migration strategy and readinessYou are here
Mobilise
Landing zone, migration plan and a pilot wave that proves the runbook.
Our service
Migrate and modernise
Waves delivered with rehearsed cutovers, then modernised onto managed AWS services.
Related beyond migration