Migration Engine
6R assessment, rehearsed waves & rollback for cloud migration.
The Migration Engine industrialises entry, movement and exit: on-premises workloads discovered by the Edge Agent are auto-classified, scored with a 6R assessment for cost, effort and blockers, and planned into rehearsable waves with rollback and Whale AI guidance. Assessment and wave planning are live; execution hooks are in progress.
- 6R
- Rehost · replatform · refactor · repurchase · retire · retain, scored
- Waves
- Dependency-aware planning with rollback
- Exit-ready
- The same engine rehearses regulator-mandated exit plans
Capabilities
What Migration Engine does
Auto-classification
Discovered workloads are classified by type, dependencies and data gravity, so the assessment starts from facts rather than interviews.
6R assessment
Each workload gets a recommended strategy with estimated target cost, effort and blockers — and the evidence behind the score.
Wave planning with rollback
Waves are cut along dependency boundaries, rehearsed, and carry a rollback plan; Whale AI drafts the sequence and flags risks.
Execution hooks (in progress)
Handoff to tooling for the move itself, with status flowing back into the wave board and ITSM changes.
How it works
3 steps, from first connection to steady state
Discover
Edge Agents inventory the source estate and map dependencies.
Assess
6R scoring with cost, effort and blockers per workload.
Plan waves
Sequence, rehearse, approve; execute with rollback when the hooks land.
Where it fits
One module of one platform
Shared platform
Capabilities
- Auto-classification of on-prem workloads
- 6R assessment with cost, effort & blockers
- Rehearsed waves with rollback — entry, movement and exit
- Whale AI migration guidance
Included in
Solutions that use it
Industries that rely on it
Also in Migration & Discovery
Questions
Questions teams ask before turning it on
Scope, permissions and maturity — answered the way we answer them in an evaluation.
01Does it move the workloads?
Assessment and wave planning are live today. Execution hooks — handing the move to tooling and tracking it back on the wave board — are in progress; until then teams execute with their existing tooling against the plan.
02Can it help with a regulator's exit-plan requirement?
Yes — the same engine turns an exit annexure into a dependency-mapped, rehearsed plan with drill evidence, which is how BFSI customers use it today.
03Which targets are supported?
Any connected estate: the six public clouds, private and virtualised platforms via the Edge Agent, and on-premises for repatriation.
See it on your data
Migration Engine, on your own estate — in one working session.
Bring one cloud account or one on-prem site. We connect it read-only during the call, walk the module on your real resources, and leave you with the export.