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
How it shows up
- The assessment is a consultant's spreadsheet that is stale before the first wave.
- Dependencies are discovered during cutover, which is when they cost the most.
- The regulator's exit plan exists on paper and has never been rehearsed.
What the 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.
From discovery to rehearsed waves
- 1
Stage 1
On-prem workloads are discovered via the Edge Agent and auto-classified with their dependencies.
- 2
Stage 2
A 6R assessment scores each workload for cost, effort and blockers.
- 3
Stage 3
Workloads are cut into dependency-aware waves; Whale AI drafts the sequence and flags risks.
- 4
Stage 4
Waves are rehearsed and approved against the unified inventory, with rollback plans attached.
- 5
Stage 5
Execution hooks (in progress) hand each wave to tooling and track it back on the board.
The regulator's exit plan
Banks under RBI outsourcing directions must hold an exit strategy for every material outsourcing. Discovery and dependency mapping turn the annexure into a plan that is rehearsed as a drill, with the evidence filed — the approach two banks in Singapore and Qatar used to move inspection preparation from weeks to days.
Questions from migration programmes
Does 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.
Can 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.
Which targets are supported?
Any connected estate: the six public clouds, private and virtualised platforms via the Edge Agent, and on-premises for repatriation.
Does the platform move the workloads?
Assessment, dependency mapping and wave planning are live. Execution hooks that hand the move to tooling and track it back are in progress; until then teams execute with existing tooling against the plan.
Can it satisfy a regulator's exit-plan requirement?
That is how BFSI customers use it: the exit annexure becomes a dependency-mapped, rehearsed plan with drill evidence the supervisor can read.
What does the assessment need from us?
An Edge Agent per site with read access to the hypervisor. Interviews fill in what discovery cannot see — business criticality, licensing constraints, change windows.