Migration & Modernization: Move workloads in tested waves, with a way back
From an on-premises data center or another cloud to AWS, Azure or Google Cloud, one small wave at a time. Then we modernize what is worth it.
Where you start, and where you land
On-premises data center to any cloud
| You land on | Servers | Databases |
|---|---|---|
| AWS | AWS Transform MGN | AWS Database Migration Service |
| Azure | Azure Migrate | Azure Database Migration Service |
| Google Cloud | Migrate to Virtual Machines | Google Database Migration Service |
Plan for Network plans and licenses come first. Colocation counts as on-premises.
How a move runs
Nothing to move? Start at stage 2
- Stage 1: AssessYou holdA dependency map and a path for each workload
- Stage 2: Build the foundationYou holdA landing zone you own, as code
- Stage 3: Move in wavesYou holdWorkloads live, with the rollback tested
- Stage 4: ModernizeYou holdA ranked list, delivered one workload at a time
- Stage 5: OptimizeYou holdA cost baseline and an operations handover
Inside every wave
- CopyData replicates while production runs
- TestChecked on the new side
- RehearseThe cutover, end to end
- Cut overA short window, sometimes none
- WatchThe old side stays ready
- RetireSwitched off once proven
Way back
What happens to each workload
Does anyone still use it?
Retire
Switched off
How much changes: 0 of 3No traffic for 90 days
Can it move now?
Retain
Stays for now
How much changes: 0 of 3Can it run as it is?
Rehost
Same servers, new home
How much changes: 1 of 3Does one part need to change?
Replatform
One part changes
How much changes: 2 of 3Everything else
Refactor
The code changes
How much changes: 3 of 3After the move, not during
How much changes
The foundation comes first
Every move lands on the same base, written as code in your repository. With nothing to move, we build it from scratch.
Your on-premises data center or other cloud
Direct Connect or VPN
AWS Organizations
Shared platform
Network hubTransit Gateway
IdentityIAM Identity Center
Central logsLog Archive and Audit accounts
Workloads
Production organizational unit
Non-production organizational unit
New workloads are added from a template: Account Factory
GuardrailsControl Tower controls
Pipelines as code, monitoring and backups from the first day
A modern cloud, optimized and up to date
Move first, modernize after. It keeps the move on its date.
- ModernManaged services or containers, where they pay off.
- OptimizedSized to measured use, tagged, committed.
- Up to dateSupported versions, upgraded on a schedule.
- ArchitectureContainers and serverless that scaleScales with load
- DataManaged databases, automatic backupsLess to run
- DeliveryInfrastructure as code, automated releasesRepeatable releases
- OperationsMetrics, logs and tracesProblems seen early
- SecurityLeast-privilege roles, encryptionSmaller blast radius
- CostRight-sized, tagged, budgetedSpend you can explain
- VersionsSupported versions, on a scheduleNo extended-support fees
Customer work
- 1,000 to 6,000+ ordersE-commerce company in BangladeshE-commerce, BangladeshRead the story: E-commerce company in Bangladesh (opens in a new tab)
- Zero downtimeFast-growing enterpriseRead the story: Fast-growing enterprise (opens in a new tab)
- A smoother booking processBus booking platformBus travelRead the story: Bus booking platform (opens in a new tab)
Questions before you plan a migration
How long does a migration take?
It depends on how many workloads you have and how tangled they are. The assessment gives you a dated plan before you commit.
Why not use the clouds’ migration tools alone?
We use them, and the route map names them. The work around them is ours: the plan, the waves, the testing and the way back.
Will there be downtime?
Usually a short window at cutover, sometimes none. Data replicates while production runs, and we rehearse the cutover.
What does modernizing mean, and can it wait?
Managed services, containers or serverless where they pay off, and current versions. It can wait: moving first meets your date.
Do we pay to move data out of our cloud?
Usually not if you leave for good: each cloud waives data transfer fees for a full exit it approves. A partial move pays normal rates.
What usually comes next
- Managed ServicesAfter the last wave, we can run what we moved, from the runbooks written during the move. (opens in a new tab)
- Audit & ComplianceA review before the move shows what to fix first, and what to retire. (opens in a new tab)
- Cloud Build & LaunchNothing to move? The same foundation, built for software that is new. (opens in a new tab)