{"id":872,"date":"2026-04-16T12:16:42","date_gmt":"2026-04-16T12:16:42","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-migrations-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-compute\/"},"modified":"2026-04-16T12:16:42","modified_gmt":"2026-04-16T12:16:42","slug":"oracle-cloud-migrations-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-compute","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-migrations-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-compute\/","title":{"rendered":"Oracle Cloud Migrations Tutorial: Architecture, Pricing, Use Cases, and Hands-On Guide for Compute"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Category<\/h2>\n\n\n\n<p>Compute<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introduction<\/h2>\n\n\n\n<p>Oracle Cloud Migrations is an Oracle Cloud (OCI) <strong>Compute-focused migration service<\/strong> designed to help you move server workloads (typically virtual machines) into <strong>OCI Compute<\/strong> with a guided, repeatable process.<\/p>\n\n\n\n<p>In simple terms: it helps you <strong>lift-and-shift<\/strong> existing servers into Oracle Cloud so you can run them as OCI instances with minimal redesign\u2014while still giving you checkpoints to validate, test, and cut over safely.<\/p>\n\n\n\n<p>Technically, Oracle Cloud Migrations provides a migration control plane in OCI for <strong>discovering source workloads<\/strong>, <strong>replicating VM disks and configuration<\/strong>, and <strong>launching equivalent OCI Compute instances<\/strong> in a target compartment, VCN, and subnet. It integrates with core OCI services such as <strong>Identity and Access Management (IAM)<\/strong>, <strong>Networking (VCN)<\/strong>, <strong>Block Volumes<\/strong>, <strong>Object Storage (in some workflows)<\/strong>, <strong>Audit<\/strong>, and <strong>Work Requests<\/strong> for governance and operations.<\/p>\n\n\n\n<p>The problem it solves: migrations fail when they are treated as ad-hoc copy operations. Oracle Cloud Migrations addresses the hard parts\u2014inventory, repeatability, replication, cutover orchestration, and operational visibility\u2014so teams can migrate server workloads into OCI with less risk and better control.<\/p>\n\n\n\n<blockquote>\n<p>Naming note (important): In the OCI Console and documentation, this capability is commonly presented as <strong>Cloud Migrations<\/strong>. This tutorial uses <strong>Oracle Cloud Migrations<\/strong> as the primary name (as requested) and treats <strong>\u201cCloud Migrations\u201d<\/strong> as the console\/documentation label. Verify the latest naming in the official docs: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/cloud-migrations\/home.htm<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Oracle Cloud Migrations?<\/h2>\n\n\n\n<p><strong>Official purpose (what it\u2019s for)<\/strong><br\/>\nOracle Cloud Migrations is intended to help you migrate server workloads\u2014most commonly <strong>VMware-based virtual machines<\/strong> and similar VM workloads\u2014into <strong>OCI Compute<\/strong> by using a managed migration workflow: discover, assess (where available), replicate, test, and cut over.<\/p>\n\n\n\n<p><strong>Core capabilities (what it can do)<\/strong><br\/>\nCapabilities vary by supported source types and current OCI release, but the service is generally centered around:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Creating a <strong>migration project<\/strong> to organize migrations<\/li>\n<li>Connecting to a <strong>source environment<\/strong> (for example, a virtualization environment such as VMware) for discovery\/inventory (where supported)<\/li>\n<li>Replicating workloads to OCI (disk data and some configuration)<\/li>\n<li>Launching OCI Compute instances from the replicated state<\/li>\n<li>Tracking progress via <strong>status<\/strong>, <strong>work requests<\/strong>, and console activity<\/li>\n<\/ul>\n\n\n\n<p>If you need database-specific migrations, application refactoring, or data pipeline moves, OCI provides separate services (for example, OCI Database Migration, GoldenGate, Data Transfer). Oracle Cloud Migrations is primarily about <strong>Compute \/ server workload migration<\/strong>.<\/p>\n\n\n\n<p><strong>Major components (how it\u2019s structured)<\/strong><br\/>\nCommon conceptual components you\u2019ll see in Oracle Cloud Migrations workflows include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Migration projects<\/strong>: A logical container for migrations and related configuration, scoped to a compartment.<\/li>\n<li><strong>Migration resources<\/strong>: The individual migrations you create per VM\/workload.<\/li>\n<li><strong>Replication and staging<\/strong>: The mechanism and OCI-side resources that receive replicated disk data and make it launchable.<\/li>\n<li><strong>Work requests \/ jobs<\/strong>: Asynchronous operations that track progress and failures in OCI.<\/li>\n<\/ul>\n\n\n\n<p>Exact component names in your tenancy may differ slightly by region or service version\u2014verify against the current console and docs.<\/p>\n\n\n\n<p><strong>Service type (control plane vs. data plane)<\/strong><br\/>\nOracle Cloud Migrations is primarily a <strong>managed control plane<\/strong> in OCI that orchestrates migration operations. The actual data movement uses <strong>replication\/staging infrastructure<\/strong> that interacts with source environments and OCI storage\/compute resources.<\/p>\n\n\n\n<p><strong>Regional vs. global; scope<\/strong> <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Regional<\/strong>: OCI services like this are typically <strong>regional<\/strong>\u2014you choose a target region where the migration project and target instances will live.<\/li>\n<li><strong>Compartment-scoped<\/strong>: Resources are created and governed within an OCI <strong>compartment<\/strong>, controlled by IAM policies.<\/li>\n<li><strong>Tenancy-wide governance<\/strong>: You can enforce tagging, audit, and guardrails at the tenancy level.<\/li>\n<\/ul>\n\n\n\n<p><strong>How it fits into the Oracle Cloud ecosystem<\/strong><br\/>\nOracle Cloud Migrations sits in the <strong>Compute migration toolkit<\/strong> of OCI and commonly integrates with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OCI Compute<\/strong>: target runtime for migrated instances<\/li>\n<li><strong>VCN (Networking)<\/strong>: subnets, security lists\/NSGs, routing, NAT\/IGW<\/li>\n<li><strong>Block Volumes<\/strong>: boot and data volumes for instances<\/li>\n<li><strong>IAM<\/strong>: least-privilege access, compartments, dynamic groups (in some patterns)<\/li>\n<li><strong>Vault<\/strong>: storing secrets\/credentials (recommended)<\/li>\n<li><strong>Logging, Audit, Events<\/strong>: operational monitoring and compliance trails<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Oracle Cloud Migrations?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Business reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Reduce migration risk<\/strong>: Use a structured workflow instead of \u201ccopy a disk and hope it boots.\u201d<\/li>\n<li><strong>Shorten project timelines<\/strong>: Repeatable steps and clearer visibility reduce rework and downtime.<\/li>\n<li><strong>Enable phased migration<\/strong>: Migrate in waves aligned to business priorities (dev\/test first, then production).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Lift-and-shift for Compute<\/strong>: Suitable when you want to move VMs with minimal code change.<\/li>\n<li><strong>Support for iterative replication<\/strong>: Lets you keep syncing changes until cutover.<\/li>\n<li><strong>Target OCI-native constructs<\/strong>: Launch to OCI instances in a VCN\/subnet with OCI security controls.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Central visibility<\/strong> in OCI Console: track migration status, tasks, failures.<\/li>\n<li><strong>Work-request-based operations<\/strong>: asynchronous operations are auditable and observable.<\/li>\n<li><strong>Standard OCI governance<\/strong>: compartments, tagging, audit logs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security \/ compliance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>IAM policy control<\/strong>: restrict who can create migrations, who can launch instances, who can access logs.<\/li>\n<li><strong>Auditability<\/strong>: OCI Audit logs record control plane actions.<\/li>\n<li><strong>Network isolation<\/strong>: place replication and target instances in private subnets, use VPN\/FastConnect.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scalability \/ performance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Parallel migration waves<\/strong>: organize projects and migrate many VMs with consistent patterns.<\/li>\n<li><strong>Right-size in OCI<\/strong>: modernize shapes, adjust CPU\/memory, and adopt OCI features post-migration.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose Oracle Cloud Migrations<\/h3>\n\n\n\n<p>Choose it when:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You are migrating <strong>server\/VM workloads<\/strong> into <strong>OCI Compute<\/strong><\/li>\n<li>You need <strong>repeatable migration orchestration<\/strong> instead of one-off manual conversions<\/li>\n<li>You want <strong>OCI-native governance<\/strong> (compartments, policies, tags, audit trails)<\/li>\n<li>You have network connectivity and access to source environments to support replication<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose it<\/h3>\n\n\n\n<p>Consider alternatives when:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You need <strong>application refactoring<\/strong>, not lift-and-shift (consider containers, OKE, or app modernization)<\/li>\n<li>You\u2019re primarily migrating <strong>databases<\/strong> (consider OCI Database Migration, Data Pump, GoldenGate)<\/li>\n<li>You cannot meet <strong>connectivity\/security requirements<\/strong> between source and OCI<\/li>\n<li>Your source platform isn\u2019t supported by the service\u2019s current capabilities (verify in docs)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Oracle Cloud Migrations used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Financial services (regulated workloads needing audit trails)<\/li>\n<li>Healthcare (controlled cutovers, traceability)<\/li>\n<li>Retail\/e-commerce (seasonal scaling, cloud adoption)<\/li>\n<li>Manufacturing (legacy on-prem VMs moving to cloud)<\/li>\n<li>SaaS providers (infrastructure consolidation into OCI)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Team types<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud platform teams migrating shared infrastructure<\/li>\n<li>Infrastructure\/virtualization teams moving VMware estates<\/li>\n<li>SRE\/operations teams standardizing backup\/monitoring post-move<\/li>\n<li>Security teams enforcing segmentation and IAM guardrails<\/li>\n<li>DevOps teams migrating CI\/CD runners, build servers, jump boxes<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Linux\/Windows application servers<\/li>\n<li>Web\/API tiers<\/li>\n<li>Batch processing workers<\/li>\n<li>Enterprise middleware running on VMs<\/li>\n<li>Third-party vendor appliances (verify supportability\/licensing)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Architectures and contexts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hub-and-spoke VCN networks with centralized security services<\/li>\n<li>Private subnets with NAT for egress and load balancers for ingress<\/li>\n<li>Hybrid connectivity via IPSec VPN or FastConnect to on-prem data centers<\/li>\n<li>Migration factory: waves, runbooks, and repeatable landing zones<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Production vs. dev\/test usage<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dev\/test<\/strong>: validate patterns (subnets, DNS, IAM, boot behavior), build runbooks, baseline performance.<\/li>\n<li><strong>Production<\/strong>: staged replication, change windows, pre-cutover checks, controlled cutover with rollback plan.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are realistic scenarios where Oracle Cloud Migrations (Compute category) is commonly used.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) VMware estate lift-and-shift into OCI Compute<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Hundreds of VMware VMs must move off aging hardware.<\/li>\n<li><strong>Why this fits<\/strong>: Structured migration projects and orchestration reduce manual conversions.<\/li>\n<li><strong>Example<\/strong>: Migrate 200 mixed Linux\/Windows VMs over 6 waves into OCI with minimal app changes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Data center exit with phased cutover<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Lease ends in 6 months; must evacuate workloads safely.<\/li>\n<li><strong>Why this fits<\/strong>: Replicate ahead of time and cut over in a controlled maintenance window.<\/li>\n<li><strong>Example<\/strong>: Replicate web tier continuously; final cutover happens overnight with DNS updates.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Migrate legacy apps to OCI before modernization<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Apps are too risky to refactor now, but must move to cloud.<\/li>\n<li><strong>Why this fits<\/strong>: Lift-and-shift to OCI first; modernize later.<\/li>\n<li><strong>Example<\/strong>: Move a monolithic Java app VM to OCI, then containerize after stabilization.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Hybrid burst and DR seeding<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Need a standby environment in OCI for disaster recovery.<\/li>\n<li><strong>Why this fits<\/strong>: Replication workflows can help seed OCI-side copies for DR planning (verify exact DR features in docs).<\/li>\n<li><strong>Example<\/strong>: Keep a warm copy in OCI and periodically test failover.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Standardize governance during migration (compartments\/tags)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: On-prem lacks consistent ownership and cost allocation.<\/li>\n<li><strong>Why this fits<\/strong>: OCI compartments and mandatory tags enforce structure.<\/li>\n<li><strong>Example<\/strong>: Every migrated VM is tagged with cost center, app ID, environment, owner.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Re-platform network\/security while keeping servers intact<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Need new segmentation and security posture without changing apps.<\/li>\n<li><strong>Why this fits<\/strong>: Launch migrated instances into hardened VCNs and NSGs.<\/li>\n<li><strong>Example<\/strong>: Place app servers in private subnets and front them with OCI Load Balancer + WAF.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Migrate build agents and CI runners<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Build farm is capacity constrained and costly to maintain.<\/li>\n<li><strong>Why this fits<\/strong>: Lift-and-shift build VMs quickly; later convert to autoscaled pools.<\/li>\n<li><strong>Example<\/strong>: Move Jenkins agents, then rebuild them as immutable images post-migration.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Vendor appliance migration (when supported)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A vendor VM appliance must run in OCI.<\/li>\n<li><strong>Why this fits<\/strong>: VM migration reduces changes (but licensing\/support must be verified).<\/li>\n<li><strong>Example<\/strong>: Migrate a monitoring appliance VM; validate vendor support in OCI.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Consolidate multi-region workloads into a single OCI region<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Too many small sites; want centralized operations.<\/li>\n<li><strong>Why this fits<\/strong>: Migration projects support organized consolidation waves.<\/li>\n<li><strong>Example<\/strong>: Migrate branch office app servers into OCI, connect via VPN.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Migrate with pre-cutover testing to reduce downtime<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Apps have strict availability requirements.<\/li>\n<li><strong>Why this fits<\/strong>: Test launches before final cutover reduce surprises.<\/li>\n<li><strong>Example<\/strong>: Launch test instances in isolated subnet; run functional checks; then cut over.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Migrate to OCI to use OCI-native backup and monitoring<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: On-prem backup tools are inconsistent across teams.<\/li>\n<li><strong>Why this fits<\/strong>: After migration, standardize on OCI Block Volume backups and OCI Monitoring.<\/li>\n<li><strong>Example<\/strong>: Apply backup policies to all migrated boot\/data volumes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Migrate \u201csnowflake\u201d servers with unknown dependencies (first step)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Poor documentation; need to move but dependencies are unclear.<\/li>\n<li><strong>Why this fits<\/strong>: Migration projects provide a trackable path; you can instrument and discover dependencies post-move.<\/li>\n<li><strong>Example<\/strong>: Migrate a legacy reporting server first, then map downstream connections in OCI.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<blockquote>\n<p>Feature availability can vary by region and source platform support. Always verify the latest feature set in the official Oracle Cloud Migrations documentation: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/cloud-migrations\/home.htm<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">1) Migration projects (organization and governance)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Groups migrations under a project boundary in a compartment.<\/li>\n<li><strong>Why it matters<\/strong>: Enables wave planning, ownership, and consistent configuration.<\/li>\n<li><strong>Practical benefit<\/strong>: Separate dev\/test vs prod projects; separate per business unit.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Projects don\u2019t replace proper compartment design; use compartments for isolation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Source environment connectivity and discovery (where supported)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Connects Oracle Cloud Migrations to a source virtualization environment to list VMs\/assets.<\/li>\n<li><strong>Why it matters<\/strong>: Inventory is the starting point for reliable migrations.<\/li>\n<li><strong>Practical benefit<\/strong>: Reduces spreadsheet-based tracking and missed dependencies.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Requires access and credentials to source platforms; ensure security review.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Replication\/staging orchestration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Coordinates disk replication from source to OCI staging so instances can be launched.<\/li>\n<li><strong>Why it matters<\/strong>: Migrations fail most often due to inconsistent disk transfers.<\/li>\n<li><strong>Practical benefit<\/strong>: More predictable cutovers with iterative syncing.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Requires sufficient bandwidth and time; large disks can take days.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Test launch before cutover (typical migration pattern)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Allows launching a migrated instance for testing before final production cutover.<\/li>\n<li><strong>Why it matters<\/strong>: Validates boot, networking, application behavior, and performance.<\/li>\n<li><strong>Practical benefit<\/strong>: Catch driver, NIC naming, DNS, or firewall issues early.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Ensure test isolation to avoid IP conflicts or accidental production traffic.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Target configuration mapping (OCI shapes, network placement)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Launches into selected VCN\/subnet and OCI Compute shape.<\/li>\n<li><strong>Why it matters<\/strong>: Landing zone compliance (subnets, NSGs, routing, IAM).<\/li>\n<li><strong>Practical benefit<\/strong>: Align with security segmentation and operational model.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Some source settings won\u2019t map 1:1; plan for post-launch changes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Work Requests and operational status tracking<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: OCI-style asynchronous operation tracking for migrations and related actions.<\/li>\n<li><strong>Why it matters<\/strong>: Provides auditability and a place to troubleshoot failures.<\/li>\n<li><strong>Practical benefit<\/strong>: Standard operator workflow: check Work Requests for errors.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Work request error messages can be terse; correlate with logs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Integration with OCI IAM, compartments, and tagging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Applies OCI-native access control and organization.<\/li>\n<li><strong>Why it matters<\/strong>: Migrations involve powerful permissions (compute, volumes, networking).<\/li>\n<li><strong>Practical benefit<\/strong>: Least privilege, separation of duties, cost allocation.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Misconfigured IAM is a common blocker; validate policies early.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Compatibility handling and post-migration adjustments (typical requirement)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Helps you move the VM; you still validate OS drivers, network config, cloud-init, etc.<\/li>\n<li><strong>Why it matters<\/strong>: Boot success \u2260 application readiness.<\/li>\n<li><strong>Practical benefit<\/strong>: Establish post-migration runbooks: update NIC config, install OCI agents, etc.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Some OS\/app issues must be fixed manually; plan time for remediation.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">7. Architecture and How It Works<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">High-level architecture<\/h3>\n\n\n\n<p>Oracle Cloud Migrations generally works as an orchestrator that:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Lets you define a migration project and connect to a source environment (where supported).<\/li>\n<li>Select a VM\/workload to migrate.<\/li>\n<li>Replicates VM disk data to OCI staging using a replication mechanism.<\/li>\n<li>Creates a launchable state (for example, a boot volume or custom image-like artifact).<\/li>\n<li>Launches an OCI Compute instance into your selected network and compartment.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Request\/data\/control flow (conceptual)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Control plane<\/strong>: User actions in OCI Console\/API create migration resources, initiate replication, and trigger launches.<\/li>\n<li><strong>Data plane<\/strong>: Disk data flows from the source environment to OCI staging over the network (VPN\/FastConnect\/public internet depending on design).<\/li>\n<li><strong>Outcome<\/strong>: OCI creates an instance with attached boot\/data volumes representing the migrated workload.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Compute<\/strong>: target instances; shapes and instance configuration<\/li>\n<li><strong>Block Volume<\/strong>: staging\/boot\/data volumes created during migration<\/li>\n<li><strong>VCN<\/strong>: subnets, route tables, security lists\/NSGs for replication and target workloads<\/li>\n<li><strong>IAM<\/strong>: policies to manage migrations and dependent resources<\/li>\n<li><strong>Vault (recommended)<\/strong>: store secrets used by connectors or appliances<\/li>\n<li><strong>Audit<\/strong>: records migration actions for compliance<\/li>\n<li><strong>Monitoring\/Logging<\/strong>: track instance health and operational metrics after launch<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services<\/h3>\n\n\n\n<p>At minimum, most migrations depend on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A target <strong>VCN<\/strong> and <strong>subnet<\/strong><\/li>\n<li>Quota\/limits for <strong>Compute instances<\/strong> and <strong>Block Volumes<\/strong><\/li>\n<li>IAM privileges to create and manage the above<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/authentication model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Human operators authenticate using OCI IAM (SSO\/federation possible).<\/li>\n<li>Access is authorized by IAM policies on compartments.<\/li>\n<li>Source-side connectivity typically requires credentials and secure network paths; treat these as sensitive and handle with Vault where possible.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Networking model<\/h3>\n\n\n\n<p>You have two main networking concerns:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Migration\/replication connectivity<\/strong> between source and OCI<br\/>\n   &#8211; Often via <strong>IPSec VPN<\/strong> or <strong>FastConnect<\/strong> for predictable throughput and security.\n   &#8211; Public internet can work for some scenarios, but security and performance must be assessed.<\/p>\n<\/li>\n<li>\n<p><strong>Target runtime networking<\/strong> in OCI<br\/>\n   &#8211; Place migrated instances in appropriate subnets (private vs public).\n   &#8211; Use NSGs\/security lists to enforce least-privilege traffic.\n   &#8211; Integrate with Load Balancers, Bastion, WAF, DNS as needed.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Monitoring\/logging\/governance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>OCI Audit<\/strong> to track who initiated migrations and instance launches.<\/li>\n<li>Use <strong>Work Requests<\/strong> for the migration service operations.<\/li>\n<li>Use <strong>OCI Monitoring<\/strong> and <strong>Logging<\/strong> on target instances after cutover (OS Management\/Compute agent as appropriate).<\/li>\n<li>Apply <strong>tags<\/strong> for cost tracking from day one (migration project and launched instances).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Simple architecture diagram (conceptual)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  U[Engineer \/ Migration Operator] --&gt;|Console\/API| OCM[Oracle Cloud Migrations&lt;br\/&gt;(Control Plane)]\n  OCM --&gt; WR[Work Requests \/ Status]\n\n  subgraph Source[Source Environment]\n    VC[vCenter \/ Hypervisor&lt;br\/&gt;+ Source VMs]\n  end\n\n  subgraph OCI[Oracle Cloud (Target Region)]\n    VCN[VCN + Subnets]\n    STG[Staging: Block Volumes \/ Artifacts]\n    CMP[OCI Compute Instances]\n  end\n\n  VC --&gt;|Replication data flow| STG\n  OCM --&gt;|Orchestrates| STG\n  STG --&gt;|Launch| CMP\n  CMP --&gt; VCN\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Production-style architecture diagram (migration factory)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph Org[Enterprise Governance]\n    IAM[IAM: Groups\/Policies&lt;br\/&gt;Dynamic Groups]\n    TAG[Tagging &amp; Cost Mgmt]\n    AUD[Audit]\n  end\n\n  subgraph Net[Hybrid Network]\n    DC[On-Prem DC&lt;br\/&gt;VMware \/ VMs]\n    VPN[IPSec VPN \/ FastConnect]\n    HUB[OCI Hub VCN&lt;br\/&gt;Firewall\/NVA (optional)]\n    SPOKE[Spoke VCNs&lt;br\/&gt;Prod \/ Nonprod]\n  end\n\n  subgraph Mig[Oracle Cloud Migrations]\n    PROJ[Migration Projects&lt;br\/&gt;Waves &amp; Runbooks]\n    REPL[Replication \/ Staging]\n    WRQ[Work Requests]\n  end\n\n  subgraph Runtime[OCI Runtime]\n    CMP[Compute Instances]\n    BLK[Block Volumes&lt;br\/&gt;Boot\/Data]\n    LB[Load Balancer]\n    OBS[Observability&lt;br\/&gt;Monitoring\/Logging]\n    BCP[Backups \/ DR pattern]\n  end\n\n  IAM --&gt; Mig\n  TAG --&gt; Mig\n  AUD --&gt; Mig\n\n  DC --&gt; VPN --&gt; HUB --&gt; SPOKE\n  PROJ --&gt; REPL --&gt; BLK --&gt; CMP\n  CMP --&gt; LB\n  CMP --&gt; OBS\n  BLK --&gt; BCP\n  Mig --&gt; WRQ\n  SPOKE --&gt; Runtime\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Tenancy \/ account requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An active <strong>Oracle Cloud (OCI) tenancy<\/strong> with permissions to create and manage Compute, Networking, and Storage resources.<\/li>\n<li>Access to the target <strong>compartment<\/strong> where you will create migration projects and launch instances.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM roles<\/h3>\n\n\n\n<p>You need IAM permissions to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Manage Oracle Cloud Migrations resources in the target compartment<\/li>\n<li>Create\/manage dependent resources (commonly: instances, volumes, VCN\/subnets, VNICs)<\/li>\n<\/ul>\n\n\n\n<p>OCI uses policy language like \u201cAllow group \u2026 to manage \u2026 in compartment \u2026\u201d. The exact policy verbs\/resources for Oracle Cloud Migrations can evolve. Start here and verify in current docs:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Migrations docs: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/cloud-migrations\/home.htm  <\/li>\n<li>IAM policy reference: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Identity\/Concepts\/policygetstarted.htm<\/li>\n<\/ul>\n\n\n\n<p>A practical approach is to use a dedicated group (for example, <code>MigrationAdmins<\/code>) and grant only what is required in the specific compartment(s). If you have a platform team, split duties:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Migration operators: manage migration projects and launches<\/li>\n<li>Network team: manage VCN\/subnets\/NSGs<\/li>\n<li>Security team: manage Vault, KMS keys, and audit settings<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Billing requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Oracle Cloud Migrations itself may not be separately metered, but migrations typically create chargeable resources (Compute, Block Volumes, network egress). Treat this as a billable project.<\/li>\n<li>Ensure you can use the <strong>Cost Estimator<\/strong> and review the <strong>price list<\/strong>:<\/li>\n<li>OCI pricing: https:\/\/www.oracle.com\/cloud\/price-list\/<\/li>\n<li>OCI cost estimator: https:\/\/www.oracle.com\/cloud\/costestimator.html<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tools<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI Console access<\/li>\n<li>SSH client for Linux instance validation<\/li>\n<li>(Optional) OCI CLI for related tasks (networking, instances)<br\/>\n  OCI CLI: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/API\/Concepts\/cliconcepts.htm<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Oracle Cloud Migrations availability can vary by region. Verify in the service documentation or the OCI console service list for your region.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas \/ limits<\/h3>\n\n\n\n<p>Check quotas\/limits for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Compute instances (including any staging\/replication instances if applicable)<\/li>\n<li>Block Volumes (total GB and volume count)<\/li>\n<li>VNICs, subnets, and public IPs (if used)<\/li>\n<li>Object Storage (if the workflow uses buckets)<\/li>\n<\/ul>\n\n\n\n<p>Limits are tenancy and region specific. Verify in the OCI console: <strong>Governance &amp; Administration \u2192 Limits, Quotas and Usage<\/strong> (exact menu naming may vary).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services and setup<\/h3>\n\n\n\n<p>At minimum:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A target <strong>VCN and subnet<\/strong> (private subnet recommended for production)<\/li>\n<li>Security rules for:<\/li>\n<li>Replication traffic (source \u2192 OCI)<\/li>\n<li>Operator access (SSH via Bastion or private access)<\/li>\n<li>Connectivity plan:<\/li>\n<li>Prefer <strong>VPN or FastConnect<\/strong> for enterprise migrations<\/li>\n<li>For labs\/POCs, public internet may be possible but must be security-reviewed<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<p>Oracle Cloud Migrations cost modeling is mainly about the <strong>resources it uses<\/strong>, not just the migration UI.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing dimensions (what you pay for)<\/h3>\n\n\n\n<p>You typically pay for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OCI Compute<\/strong> instances used during migration and after cutover (target instances; and any staging\/replication compute components, if your workflow provisions them)<\/li>\n<li><strong>Block Volumes<\/strong>:<\/li>\n<li>Boot volumes and data volumes created for migrated instances<\/li>\n<li>Any staging volumes used during replication<\/li>\n<li>Backups\/snapshots you keep<\/li>\n<li><strong>Object Storage<\/strong> (if used by the workflow or for logs\/artifacts)<\/li>\n<li><strong>Network<\/strong>:<\/li>\n<li>Ingress is often free, but <strong>egress<\/strong> (OCI \u2192 internet) is typically charged<\/li>\n<li>Data transfer across regions (if applicable) can be charged<\/li>\n<li>FastConnect\/VPN costs (ports\/provider, etc.) are separate considerations<\/li>\n<li><strong>Load Balancer \/ WAF \/ Bastion<\/strong> (if used in your landing zone)<\/li>\n<\/ul>\n\n\n\n<p>Oracle Cloud Migrations service control plane charges: in many OCI services, the control plane is not separately billed and you pay for underlying resources. <strong>Verify the current pricing stance for \u201cCloud Migrations\u201d in official pricing<\/strong> because service packaging can change.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Price list: https:\/\/www.oracle.com\/cloud\/price-list\/<\/li>\n<li>Cost estimator: https:\/\/www.oracle.com\/cloud\/costestimator.html<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier<\/h3>\n\n\n\n<p>OCI has a Free Tier, but migration projects usually require:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enough Block Volume GB to stage\/launch instances<\/li>\n<li>Network connectivity<\/li>\n<li>Potentially paid shapes for realistic testing<\/li>\n<\/ul>\n\n\n\n<p>Treat Free Tier as suitable only for <strong>very small<\/strong> experiments; verify eligibility and regional availability.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Cost drivers (what makes bills grow)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Total disk size replicated (GB) and number of VMs<\/li>\n<li>Duration of replication\/staging resources being kept running<\/li>\n<li>High-performance block volume tiers (if selected)<\/li>\n<li>Retaining snapshots\/backups long-term<\/li>\n<li>Egress-heavy testing (downloading packages, logs, or transferring data back out)<\/li>\n<li>Overprovisioning target shapes (CPU\/memory)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Hidden or indirect costs<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Parallel test instances<\/strong> (test launches can double runtime compute temporarily)<\/li>\n<li><strong>Duplicate storage<\/strong> during staging (source still running + staging volumes + target boot volume)<\/li>\n<li><strong>Operational tooling<\/strong> post-migration (logging, monitoring, third-party agents)<\/li>\n<li><strong>Connectivity<\/strong> (FastConnect ports, partner charges, or VPN operational overhead)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network\/data transfer implications<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Migration replication is data-intensive. Even if OCI ingress is not charged, your source environment may have ISP or interconnect costs.<\/li>\n<li>If you run tests that move data back to on-prem or to the internet, OCI egress charges can appear.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to optimize cost (practical tactics)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Right-size staging resources and keep them only as long as needed.<\/li>\n<li>Migrate in waves; avoid keeping large staging volumes for weeks.<\/li>\n<li>Use private subnets + NAT and minimize unnecessary internet egress.<\/li>\n<li>Right-size instances post-migration and adopt autoscaling patterns where applicable.<\/li>\n<li>Delete failed migrations\u2019 residual volumes (common surprise cost).<\/li>\n<li>Use tags from day one to attribute migration spend.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (no fabricated numbers)<\/h3>\n\n\n\n<p>A low-cost POC typically includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>1 small target Compute instance running for a few hours\/days<\/li>\n<li>A modest boot volume (and maybe one small data volume)<\/li>\n<li>Minimal egress<\/li>\n<li>Optional Bastion session usage<\/li>\n<\/ul>\n\n\n\n<p>Because OCI pricing varies by region, shape, and storage performance tier, <strong>use the OCI Cost Estimator<\/strong> to model:\n&#8211; \u201c1 instance \u00d7 N hours\u201d\n&#8211; \u201cboot volume GB \u00d7 storage tier\u201d\n&#8211; \u201cdata volume GB \u00d7 storage tier\u201d\n&#8211; \u201csnapshot\/backups \u00d7 retention\u201d<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations<\/h3>\n\n\n\n<p>For production migration waves, plan for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Temporary duplication of storage during replication and testing<\/li>\n<li>Multiple parallel migrations requiring extra quotas and staging capacity<\/li>\n<li>DR\/backups after cutover (ongoing monthly cost)<\/li>\n<li>Load balancers, WAF, and centralized logging<\/li>\n<\/ul>\n\n\n\n<p>A common enterprise pattern is to allocate a dedicated \u201cMigration\u201d compartment and track spend with tags:\n&#8211; <code>costCenter<\/code>, <code>app<\/code>, <code>env<\/code>, <code>owner<\/code>, <code>migrationWave<\/code><\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<p>This lab walks through a realistic, common scenario: migrating a VMware VM into OCI Compute using Oracle Cloud Migrations (Cloud Migrations).<\/p>\n\n\n\n<p>Because Oracle Cloud Migrations commonly targets VMware-based environments, this tutorial assumes you have <strong>VMware vCenter<\/strong> access. If you don\u2019t have VMware available, you can still use this as a runbook template and follow the same OCI-side steps in a corporate lab.<\/p>\n\n\n\n<blockquote>\n<p>The exact screen names and required connectors\/appliances can change. Follow the latest steps in the official docs while using this lab as the end-to-end blueprint: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/cloud-migrations\/home.htm<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<p>Migrate a single Linux VM from a VMware environment to <strong>OCI Compute<\/strong> using <strong>Oracle Cloud Migrations<\/strong>, then validate the migrated instance boots and is reachable via SSH.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Prepare an OCI landing zone (compartment, VCN\/subnet, IAM access).<\/li>\n<li>Create an Oracle Cloud Migrations project in OCI.<\/li>\n<li>Connect Oracle Cloud Migrations to your VMware source (via the supported connector\/appliance method in the docs).<\/li>\n<li>Discover the source VM and create a migration.<\/li>\n<li>Start replication and wait for it to become launch-ready.<\/li>\n<li>Launch a test instance in OCI and validate.<\/li>\n<li>Clean up staging and test resources to control cost.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Prepare the OCI target environment (network + access)<\/h3>\n\n\n\n<p><strong>Goal<\/strong>: Have a VCN\/subnet where the migrated instance will launch, with safe access.<\/p>\n\n\n\n<p>1) Create (or choose) a compartment, for example:\n&#8211; <code>cmp-migrations-lab<\/code><\/p>\n\n\n\n<p>2) Create a VCN (if you don\u2019t already have one):\n&#8211; Name: <code>vcn-migrations-lab<\/code>\n&#8211; CIDR: <code>10.10.0.0\/16<\/code><\/p>\n\n\n\n<p>3) Create subnets:\n&#8211; Private subnet for migrated instances: <code>subnet-private-app<\/code> (example: <code>10.10.10.0\/24<\/code>)\n&#8211; Optional public subnet for a bastion host or temporary test host: <code>subnet-public-bastion<\/code> (example: <code>10.10.1.0\/24<\/code>)<\/p>\n\n\n\n<p>4) Provide admin access pattern (choose one):\n&#8211; <strong>Recommended<\/strong>: Use <strong>OCI Bastion<\/strong> for SSH access to private instances (verify Bastion setup in docs).\n&#8211; <strong>Simpler lab option<\/strong>: Launch the test instance with a public IP temporarily, then remove later.<\/p>\n\n\n\n<p>5) Security rules:\n&#8211; If using a public IP temporarily, allow inbound TCP\/22 from <strong>your IP only<\/strong>.\n&#8211; Otherwise, allow SSH only from your bastion subnet or bastion service.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You have a compartment, VCN, and subnet ready for a new OCI instance.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In OCI Console, confirm the VCN and subnet exist and are in the correct region\/compartment.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Confirm IAM access for migration operators<\/h3>\n\n\n\n<p><strong>Goal<\/strong>: Ensure you can create migration resources and dependent compute\/storage resources.<\/p>\n\n\n\n<p>1) Create or identify an IAM group for operators, e.g.:\n&#8211; <code>grp-migration-operators<\/code><\/p>\n\n\n\n<p>2) Add your user to the group.<\/p>\n\n\n\n<p>3) Create compartment-scoped policies that allow the group to manage required resources.<\/p>\n\n\n\n<p>Because exact resource families for Oracle Cloud Migrations can change, use the docs to confirm. Start by reviewing:\n&#8211; Cloud Migrations IAM requirements: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/cloud-migrations\/home.htm\n&#8211; IAM policy language basics: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Identity\/Concepts\/policygetstarted.htm<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Your user can create a migration project and launch instances into the target compartment.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In the OCI Console, navigate to Oracle Cloud Migrations (Cloud Migrations). You should be able to create a project without authorization errors.<\/p>\n\n\n\n<p><strong>Common error<\/strong>\n&#8211; <code>NotAuthorizedOrNotFound<\/code> when creating projects or launching instances<br\/>\n<strong>Fix<\/strong>: Expand IAM policies to include required dependent resources (Compute, Volumes, Networking) in the correct compartment.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Create an Oracle Cloud Migrations project<\/h3>\n\n\n\n<p><strong>Goal<\/strong>: Create a project container for your migration.<\/p>\n\n\n\n<p>1) In OCI Console, open:\n&#8211; <strong>Oracle Cloud Migrations<\/strong> (often labeled <strong>Cloud Migrations<\/strong>)<\/p>\n\n\n\n<p>2) Click <strong>Create project<\/strong>:\n&#8211; Name: <code>proj-vmware-to-oci-lab<\/code>\n&#8211; Compartment: <code>cmp-migrations-lab<\/code><\/p>\n\n\n\n<p>3) Add tags (optional but recommended):\n&#8211; <code>env=lab<\/code>\n&#8211; <code>owner=&lt;yourname&gt;<\/code>\n&#8211; <code>app=migration-lab<\/code><\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; A migration project exists and is visible in the project list.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Open the project details page and confirm status is active\/available.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Connect Oracle Cloud Migrations to VMware (source setup)<\/h3>\n\n\n\n<p><strong>Goal<\/strong>: Allow the service to discover your VMware inventory and replicate a VM.<\/p>\n\n\n\n<p>The VMware connection step is the most environment-specific part. Oracle typically provides a <strong>supported connector\/appliance<\/strong> approach (often an OVA deployed into VMware) or another supported mechanism. Follow the current doc instructions for \u201cConnect to VMware\/vCenter\u201d in Oracle Cloud Migrations.<\/p>\n\n\n\n<p>High-level steps you should expect (verify exact steps in docs):<\/p>\n\n\n\n<p>1) Download the Oracle-provided migration connector\/appliance package (if required) from OCI documentation or console workflow.<\/p>\n\n\n\n<p>2) Deploy the appliance into your VMware environment:\n&#8211; Deploy OVA\/OVF into a VMware cluster with network access to:\n  &#8211; vCenter\n  &#8211; Source VM datastores\n  &#8211; The route to OCI target region endpoints (via VPN\/FastConnect\/internet)<\/p>\n\n\n\n<p>3) Configure the appliance:\n&#8211; Provide vCenter endpoint and credentials (least privilege recommended)\n&#8211; Provide OCI credentials or registration token (prefer OCI-native secure method as documented)\n&#8211; Select the OCI region and compartment\/project for registration<\/p>\n\n\n\n<p>4) Confirm discovery connectivity.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Oracle Cloud Migrations can communicate with your vCenter and list source VMs.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In your migration project, go to the discovery\/inventory area and confirm VMs appear.<\/p>\n\n\n\n<p><strong>Common errors and fixes<\/strong>\n&#8211; <strong>DNS resolution failures<\/strong>: Ensure the appliance can resolve OCI endpoints and vCenter FQDN.\n&#8211; <strong>TLS\/certificate issues<\/strong>: Use trusted certificates where possible; follow the connector doc guidance.\n&#8211; <strong>Network path blocked<\/strong>: Confirm firewall rules allow required outbound ports to OCI.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Select a source VM and create a migration<\/h3>\n\n\n\n<p><strong>Goal<\/strong>: Define which VM to migrate and where it should land in OCI.<\/p>\n\n\n\n<p>1) In the migration project, choose <strong>Create migration<\/strong> (or similar).\n2) Select the source VM from the discovered inventory.\n3) Provide target settings:\n&#8211; Target compartment: <code>cmp-migrations-lab<\/code>\n&#8211; Target VCN\/subnet: <code>vcn-migrations-lab<\/code> \/ <code>subnet-private-app<\/code> (or public for lab)\n&#8211; Target shape: choose a shape that matches the source VM CPU\/RAM as closely as possible\n&#8211; Boot volume size: at least as large as the source disk (add headroom)<\/p>\n\n\n\n<p>4) Save\/create the migration.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; A migration object is created with a status like \u201cCreated\u201d or \u201cReady to replicate\u201d (exact wording varies).<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Open migration details and confirm:\n  &#8211; Source VM name\/ID\n  &#8211; Target subnet\n  &#8211; Target shape mapping<\/p>\n\n\n\n<p><strong>Common error<\/strong>\n&#8211; Boot volume too small<br\/>\n<strong>Fix<\/strong>: Increase boot volume size in migration settings (if supported) or choose correct mapping.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Start replication and monitor progress<\/h3>\n\n\n\n<p><strong>Goal<\/strong>: Copy disk data from source to OCI staging.<\/p>\n\n\n\n<p>1) From the migration details page, click <strong>Start replication<\/strong> (or equivalent).\n2) Monitor:\n&#8211; Migration status in the console\n&#8211; Work Requests for errors and progress<\/p>\n\n\n\n<p>Replication time depends on:\n&#8211; Total disk GB\n&#8211; Source disk change rate\n&#8211; Network throughput\/latency\n&#8211; Staging\/storage performance<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Replication begins; progress updates in status\/work requests.\n&#8211; Eventually, the migration becomes <strong>launch-ready<\/strong> (wording varies).<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Migration status indicates the VM can be launched or tested.\n&#8211; No failed work requests.<\/p>\n\n\n\n<p><strong>Common errors<\/strong>\n&#8211; Timeouts \/ connectivity loss<br\/>\n<strong>Fix<\/strong>: Confirm stable VPN\/FastConnect, avoid packet inspection breaking replication streams, verify MTU.\n&#8211; Insufficient OCI quotas (volumes\/instances)<br\/>\n<strong>Fix<\/strong>: Request quota increase or free capacity.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 7: Launch a test instance in OCI<\/h3>\n\n\n\n<p><strong>Goal<\/strong>: Boot the migrated VM as an OCI Compute instance and validate access.<\/p>\n\n\n\n<p>1) Click <strong>Launch test instance<\/strong> (or \u201cLaunch instance\u201d) from the migration page.\n2) Choose:\n&#8211; Subnet: for lab, you may temporarily select a public subnet + public IP\n&#8211; SSH keys: provide your SSH public key for Linux\n&#8211; NSGs\/security list: allow SSH from your IP (temporary)<\/p>\n\n\n\n<p>3) Launch and wait for provisioning.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; An OCI instance exists and transitions to <strong>Running<\/strong>.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In <strong>Compute \u2192 Instances<\/strong>, confirm the instance is running and has:\n  &#8211; VNIC attached\n  &#8211; Correct subnet\n  &#8211; Public IP (if you chose it)<\/p>\n\n\n\n<p>If Linux and you attached your SSH key, connect:<\/p>\n\n\n\n<pre><code class=\"language-bash\">ssh -i ~\/.ssh\/id_rsa opc@&lt;public_ip&gt;\n<\/code><\/pre>\n\n\n\n<blockquote>\n<p>The username can differ by OS image and migrated configuration. For migrated VMs, the default user may not be <code>opc<\/code>. Use the OS\u2019s standard user (e.g., <code>ubuntu<\/code>, <code>ec2-user<\/code>, etc.) or your existing VM user. Verify the correct login approach in your source VM configuration.<\/p>\n<\/blockquote>\n\n\n\n<p>Run basic checks:<\/p>\n\n\n\n<pre><code class=\"language-bash\">uname -a\ndf -h\nip a\nsystemctl --failed || true\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; The instance is reachable and the OS boots cleanly.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 8: Decide cutover approach (test vs. production)<\/h3>\n\n\n\n<p><strong>Goal<\/strong>: Plan the last-mile steps safely.<\/p>\n\n\n\n<p>For a real migration cutover, a typical safe approach is:<\/p>\n\n\n\n<p>1) Confirm application behavior on the test instance.\n2) Schedule a cutover window.\n3) Freeze changes (or stop source VM, depending on app).\n4) Perform final sync\/replication.\n5) Launch the production instance in the correct subnet (private).\n6) Update DNS, load balancer backends, firewall rules.\n7) Monitor and keep rollback plan.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You have a clear path to production cutover with minimal downtime.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Validation<\/h3>\n\n\n\n<p>Use this checklist:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Migration status indicates replication succeeded and instance launched.<\/li>\n<li>OCI instance boots and is reachable (SSH\/RDP as applicable).<\/li>\n<li>Network connectivity works:<\/li>\n<li>Instance can reach required endpoints (DBs, APIs)<\/li>\n<li>Security rules match intended architecture<\/li>\n<li>Storage is consistent:<\/li>\n<li>Expected filesystems present<\/li>\n<li>Data volumes attached (if any)<\/li>\n<li>Services are healthy:<\/li>\n<li>No failed systemd services (Linux)<\/li>\n<li>Application logs show normal startup<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<p>Common issues and practical fixes:<\/p>\n\n\n\n<p>1) <strong>Instance boots but has no network<\/strong>\n&#8211; Cause: NIC naming changes, missing drivers, or wrong subnet\/NSG rules.\n&#8211; Fix: Use OCI console serial console (if enabled) for diagnostics; verify DHCP, IP config, and security rules.<\/p>\n\n\n\n<p>2) <strong>SSH not working<\/strong>\n&#8211; Cause: Wrong username, key not injected, firewall blocks, or SSH daemon down.\n&#8211; Fix: Confirm inbound rules allow TCP\/22 from your IP; confirm correct OS user; use serial console to check <code>\/var\/log\/auth.log<\/code> or <code>journalctl -u ssh<\/code>.<\/p>\n\n\n\n<p>3) <strong>Replication never becomes launch-ready<\/strong>\n&#8211; Cause: Network instability or insufficient quotas.\n&#8211; Fix: Check Work Requests error messages; verify connectivity; validate limits for volumes and instances.<\/p>\n\n\n\n<p>4) <strong>Unexpected costs<\/strong>\n&#8211; Cause: Staging volumes and test instances left running.\n&#8211; Fix: Tag all resources and clean up immediately after test.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>To avoid ongoing charges:<\/p>\n\n\n\n<p>1) Terminate the test OCI instance:\n&#8211; <strong>Compute \u2192 Instances \u2192 Terminate<\/strong>\n&#8211; Choose whether to delete attached boot volume (for lab, delete it)<\/p>\n\n\n\n<p>2) Delete migration resources:\n&#8211; In Oracle Cloud Migrations project, delete the migration and any staging artifacts (as allowed)<\/p>\n\n\n\n<p>3) Remove or stop replication\/staging components (if provisioned):\n&#8211; Any dedicated compute instances and volumes created for replication\/staging should be terminated\/deleted if not needed<\/p>\n\n\n\n<p>4) On VMware side:\n&#8211; Power off and delete the migration connector\/appliance if it was deployed just for the lab<\/p>\n\n\n\n<p>5) Verify no leftover Block Volumes:\n&#8211; <strong>Block Storage \u2192 Block Volumes \/ Boot Volumes<\/strong>\n&#8211; Delete unused volumes and old backups\/snapshots<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">11. Best Practices<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Architecture best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Build a <strong>landing zone first<\/strong>: compartments, VCNs, subnets, route tables, DNS strategy, and ingress\/egress model.<\/li>\n<li>Use <strong>private subnets<\/strong> for production workloads; front with Load Balancers\/WAF.<\/li>\n<li>Standardize shapes and OS baselines post-migration (golden images, configuration management).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">IAM \/ security best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Implement <strong>least privilege<\/strong>: migration operators should not automatically get broad network admin rights.<\/li>\n<li>Use <strong>separate compartments<\/strong> for:<\/li>\n<li>migration factory (staging\/testing)<\/li>\n<li>production runtime<\/li>\n<li>Use <strong>Vault<\/strong> for sensitive secrets used by connectors (where supported).<\/li>\n<li>Enable and monitor <strong>Audit<\/strong> logs for migration-related actions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treat staging resources as <strong>temporary<\/strong>\u2014delete quickly after cutover.<\/li>\n<li>Migrate in <strong>waves<\/strong>; don\u2019t keep parallel replication running for everything.<\/li>\n<li>Use tags like:<\/li>\n<li><code>migrationProject<\/code>, <code>wave<\/code>, <code>app<\/code>, <code>env<\/code>, <code>owner<\/code>, <code>costCenter<\/code><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Performance best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Size target instances with <strong>headroom<\/strong>, then right-size after performance tests.<\/li>\n<li>Place instances in subnets with adequate bandwidth and minimal bottlenecks (avoid over-restrictive middleboxes during testing).<\/li>\n<li>Verify block volume performance tier matches workload requirements.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Reliability best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use test launches and validation before cutover.<\/li>\n<li>Keep rollback plan:<\/li>\n<li>preserve source VM until production is stable<\/li>\n<li>document DNS rollback steps<\/li>\n<li>After cutover, implement backups and (if needed) DR patterns using OCI-native services.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operations best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use centralized logging\/monitoring from day one on target instances.<\/li>\n<li>Define runbooks:<\/li>\n<li>boot failures<\/li>\n<li>network connectivity checks<\/li>\n<li>application smoke tests<\/li>\n<li>Track migrations using tickets and change management; treat cutovers as controlled changes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Governance \/ tagging \/ naming<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use consistent naming:<\/li>\n<li><code>proj-&lt;source&gt;-to-oci-&lt;wave&gt;<\/code><\/li>\n<li><code>mig-&lt;app&gt;-&lt;env&gt;-&lt;vmname&gt;<\/code><\/li>\n<li><code>inst-&lt;app&gt;-&lt;env&gt;-&lt;role&gt;<\/code><\/li>\n<li>Enforce tags via governance policies where applicable.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">12. Security Considerations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Identity and access model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Oracle Cloud Migrations actions are governed by <strong>OCI IAM<\/strong>.<\/li>\n<li>Restrict who can:<\/li>\n<li>create migration projects<\/li>\n<li>connect to source environments<\/li>\n<li>launch instances<\/li>\n<li>delete migration artifacts (to prevent accidental data loss)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI encrypts data at rest by default for many storage services; confirm for Block Volumes and backups in your region and tenancy settings.<\/li>\n<li>For sensitive workloads, use <strong>customer-managed keys<\/strong> where supported (OCI Vault\/KMS) and validate the integration.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network exposure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Avoid exposing replication endpoints publicly if possible.<\/li>\n<li>Prefer VPN\/FastConnect for migration traffic.<\/li>\n<li>Place migrated instances in private subnets; use Bastion for admin access.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secrets handling<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Do not store vCenter credentials or OCI credentials in plain text on admin laptops.<\/li>\n<li>Use OCI Vault for secrets where feasible.<\/li>\n<li>Rotate credentials used by connectors\/appliances after migration waves.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Audit\/logging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enable <strong>OCI Audit<\/strong> and export logs to a central logging\/SIEM pipeline if required.<\/li>\n<li>Review Work Requests and related logs after each migration wave to capture lessons learned.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data residency: keep migrations in the approved OCI region(s).<\/li>\n<li>PII\/PHI: ensure encrypted transit paths and controlled operator access.<\/li>\n<li>Change management: migrations should follow your org\u2019s change control process.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common security mistakes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Launching migrated instances with public IPs permanently.<\/li>\n<li>Overly broad IAM policies (\u201cmanage all-resources in tenancy\u201d).<\/li>\n<li>Leaving staging volumes and snapshots accessible to too many users.<\/li>\n<li>Reusing shared admin credentials for connectors.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secure deployment recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use a dedicated <strong>migration compartment<\/strong> with strict IAM and tag enforcement.<\/li>\n<li>Use private networking and least-privilege security rules.<\/li>\n<li>Maintain an access log of who can initiate cutovers and launches.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<blockquote>\n<p>These are common real-world challenges. Confirm exact service limits and supported sources in official Oracle Cloud Migrations docs: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/cloud-migrations\/home.htm<\/p>\n<\/blockquote>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Source platform support<\/strong>: Not every hypervisor or VM format is supported. Validate compatibility early.<\/li>\n<li><strong>Driver and boot issues<\/strong>: A VM that ran on VMware may require adjustments to boot cleanly on OCI (kernel\/initramfs\/network config).<\/li>\n<li><strong>Network identity changes<\/strong>: IP addresses, MAC addresses, and interface names may change\u2014plan DNS and firewall updates.<\/li>\n<li><strong>Licensing constraints<\/strong>: Some commercial software licenses are host-locked or restrict cloud deployment.<\/li>\n<li><strong>Cutover complexity<\/strong>: Data consistency and downtime planning are still your responsibility.<\/li>\n<li><strong>Bandwidth and time<\/strong>: Large disks take time; plan replication windows and avoid peak business hours.<\/li>\n<li><strong>Quota surprises<\/strong>: Volume count\/size quotas can block migrations late in the process.<\/li>\n<li><strong>Staging cost creep<\/strong>: Staging artifacts left behind can generate ongoing Block Volume charges.<\/li>\n<li><strong>Security constraints<\/strong>: Deep packet inspection or restrictive firewalls can break replication streams.<\/li>\n<li><strong>Operational readiness<\/strong>: Migrated workloads need OCI monitoring, backups, patching, and security baseline after move.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<p>Oracle Cloud Migrations is one option in a broader migration toolkit.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Alternatives within Oracle Cloud<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Custom image import \/ manual disk conversion<\/strong>: More manual; useful for one-off migrations.<\/li>\n<li><strong>OCI Compute + rsync \/ backup-restore<\/strong>: Works for file-level migration but not a VM lift-and-shift.<\/li>\n<li><strong>OCI Database Migration<\/strong>: Best for databases, not VM compute lift-and-shift.<\/li>\n<li><strong>OCI GoldenGate<\/strong>: Best for replication-based data migration, not VM migration.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Alternatives in other clouds<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>AWS Application Migration Service (MGN)<\/strong>: Lift-and-shift server migration into AWS.<\/li>\n<li><strong>Azure Migrate<\/strong>: Discovery, assessment, and migration into Azure.<\/li>\n<li><strong>Google Cloud Migrate to VMs<\/strong>: VM migration into Google Cloud.<\/li>\n<li><strong>VMware HCX<\/strong>: Strong for VMware-to-VMware hybrid\/cloud mobility, depending on target.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Open-source \/ self-managed<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Backup\/restore + rebuild<\/strong> (Veeam, etc.) depending on environment and licensing<\/li>\n<li><strong>Disk conversion tools<\/strong> (qemu-img, etc.) for DIY, but high operational risk at scale<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Comparison table<\/h4>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Best For<\/th>\n<th>Strengths<\/th>\n<th>Weaknesses<\/th>\n<th>When to Choose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Oracle Cloud Migrations<\/td>\n<td>Migrating VMs into OCI Compute with a guided workflow<\/td>\n<td>OCI-native governance, migration orchestration, repeatable process<\/td>\n<td>Requires supported sources\/connectivity; still need OS\/app validation<\/td>\n<td>You\u2019re moving VM\/server workloads to OCI and want structured migrations<\/td>\n<\/tr>\n<tr>\n<td>Manual VM conversion + custom images<\/td>\n<td>One-off or niche VM formats<\/td>\n<td>Full control; can work when managed tools don\u2019t<\/td>\n<td>Error-prone, hard to scale, weaker auditing<\/td>\n<td>Small migrations where you can accept manual effort<\/td>\n<\/tr>\n<tr>\n<td>OCI Database Migration<\/td>\n<td>Database migrations to OCI<\/td>\n<td>Purpose-built for DBs; minimizes downtime with proper strategies<\/td>\n<td>Not for VM lift-and-shift<\/td>\n<td>Your primary scope is databases, not server VMs<\/td>\n<\/tr>\n<tr>\n<td>AWS MGN<\/td>\n<td>Server migration into AWS<\/td>\n<td>Mature server replication and cutover tooling<\/td>\n<td>Locks into AWS target<\/td>\n<td>Your target is AWS, not OCI<\/td>\n<\/tr>\n<tr>\n<td>Azure Migrate<\/td>\n<td>Server migration into Azure<\/td>\n<td>Strong assessment and planning tools<\/td>\n<td>Azure-only target<\/td>\n<td>Your target is Azure<\/td>\n<\/tr>\n<tr>\n<td>Google Migrate to VMs<\/td>\n<td>Server migration into Google Cloud<\/td>\n<td>VM migration tooling for GCP<\/td>\n<td>GCP-only target<\/td>\n<td>Your target is GCP<\/td>\n<\/tr>\n<tr>\n<td>VMware HCX<\/td>\n<td>VMware mobility\/hybrid strategy<\/td>\n<td>Excellent for VMware-centric environments<\/td>\n<td>Depends on VMware stack and target support<\/td>\n<td>You\u2019re staying VMware-first and moving between VMware environments<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">15. Real-World Example<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Enterprise example: regulated company migrating VMware workloads to OCI<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A financial services organization must exit a data center. Workloads are mostly VMware VMs with strict audit requirements and segmented networks.<\/li>\n<li><strong>Proposed architecture<\/strong>:<\/li>\n<li>Build OCI landing zone with hub-and-spoke VCNs<\/li>\n<li>Use VPN\/FastConnect for replication traffic<\/li>\n<li>Use Oracle Cloud Migrations projects per wave and business unit<\/li>\n<li>Launch migrated workloads into private subnets behind load balancers<\/li>\n<li>Centralize logging and enable audit exports<\/li>\n<li><strong>Why Oracle Cloud Migrations was chosen<\/strong>:<\/li>\n<li>Provides structured migration control within OCI<\/li>\n<li>Works with OCI IAM\/compartments\/tags for governance<\/li>\n<li>Supports phased replication and test launches (verify feature behavior in your region)<\/li>\n<li><strong>Expected outcomes<\/strong>:<\/li>\n<li>Predictable migration waves with traceable work requests<\/li>\n<li>Reduced downtime through pre-cutover validation<\/li>\n<li>Improved governance and cost allocation via OCI tagging<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: lift-and-shift a small set of VMs to OCI<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A startup runs 10 VMs on a small VMware cluster; hardware failures are increasing. They need a fast move without refactoring.<\/li>\n<li><strong>Proposed architecture<\/strong>:<\/li>\n<li>Single VCN with separate subnets for app and admin<\/li>\n<li>Oracle Cloud Migrations project for all VM migrations<\/li>\n<li>Temporary public IPs only during testing; move to private subnets after<\/li>\n<li>Adopt OCI backups and monitoring after cutover<\/li>\n<li><strong>Why Oracle Cloud Migrations was chosen<\/strong>:<\/li>\n<li>Faster and more repeatable than manual disk conversions<\/li>\n<li>Aligns with OCI Compute target environment<\/li>\n<li><strong>Expected outcomes<\/strong>:<\/li>\n<li>Migration completed in days, not weeks<\/li>\n<li>Standardized backups and monitoring<\/li>\n<li>Reduced operational overhead of on-prem hardware<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<p>1) <strong>Is Oracle Cloud Migrations the same as \u201cCloud Migrations\u201d in the OCI Console?<\/strong><br\/>\nYes\u2014Oracle commonly labels it \u201cCloud Migrations\u201d in the console\/docs. This tutorial uses \u201cOracle Cloud Migrations\u201d as the primary name. Verify in docs: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/cloud-migrations\/home.htm<\/p>\n\n\n\n<p>2) <strong>What workloads does Oracle Cloud Migrations target?<\/strong><br\/>\nPrimarily <strong>server\/VM migrations<\/strong> into <strong>OCI Compute<\/strong>. For exact supported sources (VMware versions, OS types), verify the support matrix in the official docs.<\/p>\n\n\n\n<p>3) <strong>Does it migrate databases too?<\/strong><br\/>\nIt can migrate a VM that <em>contains<\/em> a database, but that\u2019s not the same as a database migration strategy. For database-native migration, use OCI Database Migration or related tooling.<\/p>\n\n\n\n<p>4) <strong>Is downtime required?<\/strong><br\/>\nMost migrations require a cutover window to ensure consistency. Replication can reduce downtime, but final cutover planning is still required.<\/p>\n\n\n\n<p>5) <strong>Do I need VPN or FastConnect?<\/strong><br\/>\nNot always, but it\u2019s strongly recommended for production migrations for security and predictable throughput. Public internet migrations require careful review.<\/p>\n\n\n\n<p>6) <strong>Can I test the migrated VM before production cutover?<\/strong><br\/>\nA test launch is a common migration best practice and is typically part of migration workflows. Confirm the exact \u201ctest instance\u201d capabilities in your service version\/region.<\/p>\n\n\n\n<p>7) <strong>What happens to IP addresses and DNS?<\/strong><br\/>\nIP addresses typically change in OCI. Plan DNS updates, load balancer configuration, and firewall rules as part of the cutover.<\/p>\n\n\n\n<p>8) <strong>Can I right-size the VM during migration?<\/strong><br\/>\nYou can usually choose an OCI shape for the target instance. Right-size after performance testing to reduce cost.<\/p>\n\n\n\n<p>9) <strong>How do I track failures?<\/strong><br\/>\nUse migration status plus OCI <strong>Work Requests<\/strong> and <strong>Audit<\/strong> logs. Work requests often contain the most actionable failure details.<\/p>\n\n\n\n<p>10) <strong>What are the biggest causes of migration delays?<\/strong><br\/>\nBandwidth constraints, large disks, change rate on source disks, quota limits, and insufficient pre-cutover validation.<\/p>\n\n\n\n<p>11) <strong>How do I control cost during migration?<\/strong><br\/>\nDelete staging artifacts quickly, avoid leaving test instances running, and tag everything for chargeback\/showback.<\/p>\n\n\n\n<p>12) <strong>Is Oracle Cloud Migrations agent-based or agentless?<\/strong><br\/>\nIt depends on the source type and current implementation. VMware migrations are often connector\/appliance based. Verify the specific method for your source platform in docs.<\/p>\n\n\n\n<p>13) <strong>Can I use it for cross-region migration?<\/strong><br\/>\nOracle Cloud Migrations is typically used to migrate into a selected target region. Cross-region moves may require separate strategies. Verify capabilities and supported patterns.<\/p>\n\n\n\n<p>14) <strong>What security controls should I implement?<\/strong><br\/>\nLeast-privilege IAM, private networking, Vault for secrets, audit log export, and strict security rules for replication and admin access.<\/p>\n\n\n\n<p>15) <strong>How do I validate application correctness after migration?<\/strong><br\/>\nUse a runbook: boot validation, network checks, service health checks, application smoke tests, and performance baselines compared to the source.<\/p>\n\n\n\n<p>16) <strong>Can I migrate Windows VMs?<\/strong><br\/>\nPossibly, depending on supported sources and OS requirements. Pay attention to drivers, licensing, and activation. Verify Windows support in official documentation.<\/p>\n\n\n\n<p>17) <strong>What\u2019s the recommended order: migrate first or build landing zone first?<\/strong><br\/>\nBuild the landing zone first. Migrations into an unstructured network and IAM environment often create security debt and rework.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn Oracle Cloud Migrations<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Resource Type<\/th>\n<th>Name<\/th>\n<th>Why It Is Useful<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Official documentation<\/td>\n<td>Oracle Cloud Migrations (Cloud Migrations) Docs \u2014 https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/cloud-migrations\/home.htm<\/td>\n<td>Primary source for supported platforms, workflows, and IAM requirements<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>OCI Price List \u2014 https:\/\/www.oracle.com\/cloud\/price-list\/<\/td>\n<td>Authoritative pricing reference (region\/SKU dependent)<\/td>\n<\/tr>\n<tr>\n<td>Official calculator<\/td>\n<td>OCI Cost Estimator \u2014 https:\/\/www.oracle.com\/cloud\/costestimator.html<\/td>\n<td>Model migration staging + target runtime costs without guessing<\/td>\n<\/tr>\n<tr>\n<td>Official IAM docs<\/td>\n<td>OCI IAM Overview \u2014 https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Identity\/Concepts\/overview.htm<\/td>\n<td>Required for least privilege and compartment strategy<\/td>\n<\/tr>\n<tr>\n<td>Official networking docs<\/td>\n<td>OCI Networking (VCN) Overview \u2014 https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Network\/Concepts\/overview.htm<\/td>\n<td>Essential for designing secure replication and target networks<\/td>\n<\/tr>\n<tr>\n<td>Architecture center<\/td>\n<td>Oracle Architecture Center \u2014 https:\/\/docs.oracle.com\/solutions\/<\/td>\n<td>Reference architectures and patterns relevant to landing zones and migrations<\/td>\n<\/tr>\n<tr>\n<td>Official tutorials\/labs<\/td>\n<td>Oracle LiveLabs \u2014 https:\/\/apexapps.oracle.com\/pls\/apex\/r\/dbpm\/livelabs\/home<\/td>\n<td>Hands-on labs for OCI services (search for migration\/compute labs)<\/td>\n<\/tr>\n<tr>\n<td>Official videos<\/td>\n<td>Oracle Cloud Infrastructure YouTube \u2014 https:\/\/www.youtube.com\/@OracleCloudInfrastructure<\/td>\n<td>Vendor-maintained demos and walkthroughs (verify recency)<\/td>\n<\/tr>\n<tr>\n<td>CLI docs<\/td>\n<td>OCI CLI Documentation \u2014 https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/API\/Concepts\/cliconcepts.htm<\/td>\n<td>Useful for automating validation and related OCI tasks<\/td>\n<\/tr>\n<tr>\n<td>Community learning<\/td>\n<td>Oracle Cloud Customer Connect \u2014 https:\/\/cloudcustomerconnect.oracle.com\/<\/td>\n<td>Discussions and practical troubleshooting from OCI users (validate against docs)<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">18. Training and Certification Providers<\/h2>\n\n\n\n<p>The following training providers may offer Oracle Cloud and migration-related learning. Verify current course availability directly on their sites.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Institute<\/th>\n<th>Suitable Audience<\/th>\n<th>Likely Learning Focus<\/th>\n<th>Mode<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps engineers, SREs, platform teams<\/td>\n<td>Cloud\/DevOps foundations, CI\/CD, operations practices applicable to OCI migrations<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>ScmGalaxy.com<\/td>\n<td>Beginners to intermediate engineers<\/td>\n<td>DevOps tooling, SCM, automation concepts useful during migration projects<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.scmgalaxy.com\/<\/td>\n<\/tr>\n<tr>\n<td>CLoudOpsNow.in<\/td>\n<td>Cloud ops teams, administrators<\/td>\n<td>Cloud operations and governance practices relevant to post-migration operations<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.cloudopsnow.in\/<\/td>\n<\/tr>\n<tr>\n<td>SreSchool.com<\/td>\n<td>SREs, reliability engineers<\/td>\n<td>Reliability engineering practices, monitoring, incident response for migrated workloads<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.sreschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>AiOpsSchool.com<\/td>\n<td>Ops teams exploring AIOps<\/td>\n<td>Automation\/observability concepts that can complement migration operations<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.aiopsschool.com\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<p>These sites are presented as training resources\/platforms. Validate current Oracle Cloud offerings and trainer credentials directly.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Platform\/Site<\/th>\n<th>Likely Specialization<\/th>\n<th>Suitable Audience<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>RajeshKumar.xyz<\/td>\n<td>DevOps\/cloud training content (verify OCI topics)<\/td>\n<td>Engineers seeking guided training<\/td>\n<td>https:\/\/rajeshkumar.xyz\/<\/td>\n<\/tr>\n<tr>\n<td>devopstrainer.in<\/td>\n<td>DevOps training and mentoring (verify OCI topics)<\/td>\n<td>Beginners to intermediate DevOps engineers<\/td>\n<td>https:\/\/www.devopstrainer.in\/<\/td>\n<\/tr>\n<tr>\n<td>devopsfreelancer.com<\/td>\n<td>Freelance DevOps guidance (verify OCI topics)<\/td>\n<td>Teams needing short-term coaching<\/td>\n<td>https:\/\/www.devopsfreelancer.com\/<\/td>\n<\/tr>\n<tr>\n<td>devopssupport.in<\/td>\n<td>Ops\/DevOps support and training resources (verify OCI topics)<\/td>\n<td>Operations teams and engineers<\/td>\n<td>https:\/\/www.devopssupport.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<p>These consulting companies may help with cloud migration planning, landing zones, DevOps, and operations. Validate specific Oracle Cloud Migrations experience directly.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Company<\/th>\n<th>Likely Service Area<\/th>\n<th>Where They May Help<\/th>\n<th>Consulting Use Case Examples<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cotocus.com<\/td>\n<td>Cloud\/DevOps consulting (verify OCI offerings)<\/td>\n<td>Migration planning, automation, ops enablement<\/td>\n<td>Build migration runbooks; implement tagging\/IAM guardrails; post-migration monitoring setup<\/td>\n<td>https:\/\/cotocus.com\/<\/td>\n<\/tr>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>Training + consulting (verify OCI offerings)<\/td>\n<td>Enablement, DevOps pipelines, operational readiness<\/td>\n<td>Migration factory process; CI\/CD for post-migration deployments; SRE practices<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>DEVOPSCONSULTING.IN<\/td>\n<td>DevOps consulting (verify OCI offerings)<\/td>\n<td>DevOps transformations, automation, platform engineering<\/td>\n<td>Infrastructure as Code; standard logging\/monitoring; governance automation<\/td>\n<td>https:\/\/www.devopsconsulting.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">21. Career and Learning Roadmap<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn before Oracle Cloud Migrations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI fundamentals:<\/li>\n<li>Regions, compartments, IAM<\/li>\n<li>VCN basics: subnets, routing, security lists\/NSGs, NAT\/IGW<\/li>\n<li>Compute fundamentals:<\/li>\n<li>Shapes, boot volumes, block volumes, VNICs<\/li>\n<li>Linux\/Windows administration (boot troubleshooting, networking)<\/li>\n<li>Migration fundamentals:<\/li>\n<li>RPO\/RTO concepts<\/li>\n<li>Cutover planning and rollback strategies<\/li>\n<li>DNS and load balancer basics<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after Oracle Cloud Migrations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI observability:<\/li>\n<li>Monitoring, Logging, Alarms, Notifications<\/li>\n<li>OCI security services:<\/li>\n<li>Vault\/KMS, Cloud Guard (if used in your org), security zones (where applicable)<\/li>\n<li>High availability and DR:<\/li>\n<li>Multi-AD and multi-region designs (depending on region)<\/li>\n<li>Backup policies, restore testing<\/li>\n<li>Modernization:<\/li>\n<li>Containers (OKE), Terraform\/IaC, CI\/CD pipelines<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Job roles that use it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Engineer \/ Cloud Operations Engineer<\/li>\n<li>Solutions Architect \/ Cloud Architect<\/li>\n<li>DevOps Engineer \/ Platform Engineer<\/li>\n<li>SRE \/ Reliability Engineer<\/li>\n<li>Security Engineer (migration governance and controls)<\/li>\n<li>Infrastructure\/Virtualization Engineer (VMware \u2192 OCI transitions)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Oracle\u2019s certification landscape changes. Start with OCI foundational learning and then specialize. Verify current Oracle certification paths here:\n&#8211; https:\/\/education.oracle.com\/<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Build a migration landing zone with compartments + tag strategy.<\/li>\n<li>Create a \u201cmigration wave\u201d runbook and apply it to 3 test VMs.<\/li>\n<li>Implement a post-migration baseline:<\/li>\n<li>monitoring + alarms<\/li>\n<li>backup policy<\/li>\n<li>CIS-style OS hardening steps (as appropriate)<\/li>\n<li>Simulate cutover:<\/li>\n<li>test instance in isolated subnet<\/li>\n<li>production launch in private subnet behind load balancer<\/li>\n<li>DNS switch + rollback exercise<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OCI (Oracle Cloud Infrastructure)<\/strong>: Oracle Cloud platform providing compute, networking, storage, and managed services.<\/li>\n<li><strong>Compartment<\/strong>: OCI logical isolation boundary for resources and IAM policy scope.<\/li>\n<li><strong>VCN (Virtual Cloud Network)<\/strong>: OCI virtual network containing subnets and routing.<\/li>\n<li><strong>Subnet<\/strong>: Network segment within a VCN (public or private).<\/li>\n<li><strong>NSG (Network Security Group)<\/strong>: Security rules applied to VNICs for micro-segmentation.<\/li>\n<li><strong>Security List<\/strong>: Subnet-level virtual firewall rules (older model; still used).<\/li>\n<li><strong>Boot Volume<\/strong>: The disk that contains the OS for an OCI instance.<\/li>\n<li><strong>Block Volume<\/strong>: Persistent storage volume attached to an OCI instance.<\/li>\n<li><strong>Work Request<\/strong>: OCI mechanism for tracking asynchronous operations and their status.<\/li>\n<li><strong>Lift-and-shift<\/strong>: Migrating a workload with minimal changes to architecture\/application code.<\/li>\n<li><strong>Cutover<\/strong>: The final switch from source workload to target workload in production.<\/li>\n<li><strong>Rollback<\/strong>: Reverting to the source environment if the cutover fails.<\/li>\n<li><strong>FastConnect<\/strong>: Dedicated private connectivity to OCI (carrier\/partner dependent).<\/li>\n<li><strong>IPSec VPN<\/strong>: Encrypted site-to-site tunnel over the internet.<\/li>\n<li><strong>Landing zone<\/strong>: Pre-built cloud environment with standard networking, IAM, security, and governance.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>Oracle Cloud Migrations (Cloud Migrations in the OCI console) is an Oracle Cloud <strong>Compute migration service<\/strong> used to move VM\/server workloads into <strong>OCI Compute<\/strong> through a structured workflow: organize migrations into projects, connect to sources, replicate data, launch instances, validate, and cut over.<\/p>\n\n\n\n<p>It matters because migration success depends on repeatability, visibility, and governance\u2014not just copying disks. Oracle Cloud Migrations helps teams reduce risk with tracked operations (work requests), OCI-native IAM controls, and a process that supports testing before final cutover.<\/p>\n\n\n\n<p>Cost-wise, focus on the real drivers: <strong>Compute runtime<\/strong>, <strong>Block Volume storage<\/strong> (including staging and leftovers), and <strong>networking<\/strong>. Security-wise, prioritize <strong>least-privilege IAM<\/strong>, private networking, Vault-backed secrets, and strong audit practices.<\/p>\n\n\n\n<p>Use Oracle Cloud Migrations when you need a practical lift-and-shift path into OCI Compute and you can meet the connectivity and source platform requirements. Next step: read the official documentation end-to-end and run a small POC migration in a dedicated compartment with strict tagging and cleanup discipline: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/cloud-migrations\/home.htm<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Compute<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26,62],"tags":[],"class_list":["post-872","post","type-post","status-publish","format-standard","hentry","category-compute","category-oracle-cloud"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/872","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=872"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/872\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=872"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=872"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=872"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}