Use Case
VMware to OCI Migration
For teams moving VMware workloads to OCI without refactoring the application stack, while keeping dry-run evidence, target mapping, cutover sequencing, and rollback assumptions visible.
Operating Context
Where this use case fits
This use case fits when the source estate, target model, operating system coverage, RTO/RPO expectations, validation evidence, database scope, and recovery or migration governance must be planned together.
Source environment considerations
VMware vSphere / ESXi environments often combine mixed operating systems, disk layouts, network dependencies, and business-critical applications that must be planned as one workload portfolio.
OCI target operating model
OCI delivery brings tenancy access, network mapping, storage placement, validation evidence, and recovery or cutover readiness into a single planning model.
Agentless
Yorigu coordinates access, target preparation, validation evidence, and lifecycle state through the orchestration layer while keeping the source-side operating model lightweight.
Lifecycle
Controlled migration, with validation and rollback planning
The operating method is framed around migration control: assessment, preparation, dry-run, cutover, validation, and rollback planning.
AssessPrepareDry RunCutoverValidateRollback Planning
Related Yorigu Product
Yorigu Migrate for OCI provides the Yorigu product scope for this use case. Detailed coverage, packaging, and DB System options are outlined on the product page.
Review Product ScopeNext Step
Confirm fit for your environment
A Yorigu scope discussion confirms operating system coverage, access model, network reachability, target placement, DB System requirements, validation expectations, and handoff criteria before implementation.