Cloud Migration turns a datacenter exit or a regulator's exit-plan requirement into a costed, sequenced programme. Workloads discovered by the Edge Agent are classified, scored with a 6R assessment for cost, effort and blockers, and cut into dependency-aware waves with rollback plans. Assessment and wave planning are live; execution hooks that hand the move to tooling and track it back are in progress.
- 6R
- Rehost · replatform · refactor · repurchase · retire · retain — scored per workload
- Live
- Assessment and wave planning; execution hooks in progress
- Any target
- Six public clouds, private platforms via Edge Agent, or repatriation
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.
How it works
- 1
Step 1
On-prem workloads are discovered via the Edge Agent and auto-classified with their dependencies.
- 2
Step 2
A 6R assessment scores each workload for cost, effort and blockers.
- 3
Step 3
Workloads are cut into dependency-aware waves; Whale AI drafts the sequence and flags risks.
- 4
Step 4
Waves are rehearsed and approved against the unified inventory, with rollback plans attached.
- 5
Step 5
Execution hooks (in progress) hand each wave to tooling and track it back on the board.
What is included
- Auto-classification of on-prem workloads
- 6R assessment with cost, effort & blockers
- Dependency-aware wave planning with rollback
- Whale AI migration guidance
Modules involved
Migration Engine
6R assessment, rehearsed waves & rollback for cloud migration.
Inventory & Discovery
A live, unified map of every asset — across every cloud and on-prem.
Cloud Connectors
One control plane over six public clouds, plus private, hybrid & edge.
Editions and audience
Recommended editions: Enterprise and Telco & Datacenter.
Who it is for: CIOs and Heads of Infrastructure running data-center-exit and cloud-migration programs.
Delivered engagement — Two leading banks, Singapore & Qatar
Two banks running public cloud, private infrastructure and on-premises systems under MAS and Qatar central-bank supervision moved from weeks of manual evidence assembly per inspection to reports generated from one policy layer — and rehearsed the exit plans they had only ever documented.
“The last supervisory request took three days. Before, it took three weeks of five people pulling screenshots. And the exit plan has now been run as a drill, with the evidence filed.”
Questions teams ask in the evaluation
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.