Domain 1: Fundamentals of Cloud Migrations (10%)
Domain 1 of the 1Z0-1123-25 OCI Migration Architect Professional exam covers the foundational principles of cloud migration: why organizations migrate, what strategies they use, how they assess readiness, and how Oracle's frameworks guide the process. This domain represents approximately 5 questions on the exam. Despite the low weight, it establishes vocabulary and concepts that every other domain builds on.
1. Key Drivers for Cloud Adoption
Understanding why organizations migrate to OCI is foundational. The exam tests whether you can identify the correct business or technical driver for a given scenario.
Business Drivers
| Driver |
Description |
| Cost reduction |
Shift from capital expenditure (CapEx) to operational expenditure (OpEx). Eliminate data center hardware procurement, facilities, and maintenance costs. OCI claims >3x better compute price-performance than AWS and 74% lower private network connectivity costs. (OCI Value Proposition) |
| Agility and speed |
Provision infrastructure in minutes instead of weeks. Respond to market changes faster with elastic scaling. |
| Innovation enablement |
Access to AI, ML, data science, and modern platform services without building from scratch. |
| Risk reduction |
Distribute workloads across regions and availability domains. OCI provides comprehensive SLAs covering availability, manageability, and performance. |
| Regulatory compliance |
Meet data residency requirements using OCI's global regions, Dedicated Regions (Cloud@Customer), or multicloud deployments. |
Technical Drivers
| Driver |
Description |
| Data center consolidation |
Reduce physical footprint by moving workloads to OCI. |
| End-of-life hardware |
Avoid costly hardware refresh cycles by migrating to cloud infrastructure. |
| Disaster recovery |
Replace expensive idle DR sites with OCI cross-region replication. |
| Performance optimization |
Leverage OCI bare metal, RDMA cluster networking, and HPC capabilities. |
| Security posture |
OCI's security is built into the core architecture (off-box virtualization, custom security chips) and included at no additional charge. (OCI Value Proposition) |
Exam trap: Cost savings alone are rarely the correct sole answer. Oracle's framework emphasizes that a strong business case must address both tangible financial benefits (TCO reduction) and intangible benefits (agility, time to market, competitive advantage). (OCI Business Case)
2. Challenges During Migration
The exam expects you to identify which challenges apply to a given migration scenario and recommend appropriate mitigations.
| Challenge Category |
Specific Challenges |
| Technical |
Application compatibility, legacy dependencies, data transfer bandwidth limitations, downtime constraints, network latency requirements, licensing complexity (BYOL vs. new licenses) |
| Organizational |
Resistance to change, skills gaps, lack of executive sponsorship, unclear ownership between teams, insufficient Cloud Center of Excellence (CCoE) |
| Compliance |
Data residency regulations (GDPR, HIPAA, PCI DSS, SOX, CCPA), cross-border data transfer restrictions, audit requirements, industry-specific mandates |
| Operational |
Managing hybrid environments during transition, maintaining SLAs during cutover, coordinating multi-team migration schedules, post-migration optimization |
Exam trap: Organizational challenges (people, process) are tested as heavily as technical ones. The Oracle Cloud Adoption Framework explicitly lists People Strategy and Process Design as two of its six pillars. A technically sound migration plan that ignores organizational readiness will fail. (OCI CAF)
3. The 7 Rs of Migration Strategy
This is the most directly testable topic in Domain 1. You must match each strategy to the correct scenario and understand the tradeoffs.
| Strategy |
Also Called |
What It Does |
When to Use |
OCI Relevance |
| Rehost |
Lift and shift |
Move workloads as-is with no code changes |
Quick migration, tight timelines, minimal risk tolerance |
Oracle Cloud Migrations service automates VM rehosting from VMware and AWS EC2 (Cloud Migrations Overview) |
| Replatform |
Lift, tinker, and shift |
Minor optimizations during migration (e.g., switch to managed database) |
Moderate modernization with limited refactoring budget |
Migrate Oracle DB to Autonomous Database or Exadata Cloud Service during migration |
| Refactor |
Re-architect |
Redesign application to be cloud-native |
Maximize cloud benefits, long-term investment, applications that need elasticity |
Containerize to OKE, adopt microservices, use OCI serverless |
| Repurchase |
Drop and shop |
Replace existing application with a SaaS or cloud-native equivalent |
Legacy applications with modern SaaS replacements available |
Replace on-premises ERP with Oracle Fusion Cloud Applications |
| Retire |
Decommission |
Identify and shut down applications no longer needed |
Redundant, low-value, or duplicate applications discovered during assessment |
Reduces migration scope and cost |
| Retain |
Revisit later |
Keep application in its current environment |
Regulatory constraints, deep dependencies, recently upgraded, no business case to migrate now |
Maintain on-premises with hybrid connectivity via FastConnect |
| Relocate |
Hypervisor-level move |
Move entire virtualized environment without changing the virtualization layer |
VMware environments that need cloud economics without any application changes |
Migrate to Oracle Cloud VMware Solution (OCVS) |
Decision Criteria for Selecting a Strategy
| Factor |
Favors Rehost |
Favors Replatform |
Favors Refactor |
| Timeline |
Weeks to months |
Months |
Months to years |
| Cost (migration) |
Low |
Medium |
High |
| Cost (ongoing) |
Higher (no optimization) |
Medium |
Lowest (cloud-native efficiency) |
| Risk |
Lowest |
Low-Medium |
Highest |
| Cloud benefit realization |
Minimal |
Moderate |
Maximum |
| Skills required |
Infrastructure team |
Infrastructure + DBA |
Application developers + architects |
Exam trap: Relocate and Rehost are not the same thing. Relocate moves the entire virtualization layer (e.g., VMware to OCVS) with zero application changes. Rehost moves individual VMs to OCI Compute instances, which requires boot volume conversion and may need configuration adjustments. The Oracle Cloud Migrations service supports Rehost, not Relocate.
4. Migration Workflow Phases
Oracle defines a four-phase migration methodology: Plan, Prepare, Execute, and Validate. (Oracle Cloud Migration Hub) The Oracle Cloud Migrations service operationalizes this into three workflow phases.
Oracle Cloud Migrations Service Workflow
Phase 1: Manage Assets (Discovery)
- Establish connectivity to source environment (VMware or AWS)
- VMware uses an agent-based approach: deploy a Remote Agent Appliance
- AWS uses an agentless approach: direct OCI-initiated connection
- Automatically discover compute, storage, and networking resources
- Store discovered assets in an Inventory database within the OCI tenancy
- Collect performance data stored in OCI Monitoring service
- Refresh inventory on-demand or via automated Discovery Schedule
(Cloud Migrations Overview)
Phase 2: Plan and Migrate Assets
- Create a Migration Project (logical container grouping migration assets and plans)
- Recommendation Engine generates initial target configuration based on discovered attributes and performance statistics
- Create multiple migration plans for different scenarios (smoke testing, integration testing, load testing, cost analysis)
- Each migration plan includes a monthly cost estimate
- Data replication is independent of planning and uses HTTPS
- Incremental replication is supported
- Data is replicated once to a specific availability domain; each plan clones the replicated data
Phase 3: Verify Migration
- Integrates with OCI Resource Manager (Terraform) for target deployment
- Running a migration plan: clones data, generates a Resource Manager Stack, applies target configuration, performs automated remediation
- Validation is performed outside the Cloud Migrations service
- If verification fails: terminate resources, update replication, re-run plan
- Mark migration project complete to lock configuration (prevents accidental changes to verified production resources)
Exam trap: Replication and planning are independent processes. You can replicate data before finalizing your target configuration. You do not need to complete planning before starting replication.
Key Terminology
| Term |
Definition |
| Asset Source |
Connectivity information for the source environment |
| Inventory Asset |
Metadata representation of a discovered resource with collected metrics |
| Migration Asset |
Inventory asset assigned to a migration project with a replication location |
| Target Asset |
Asset in a migration plan representing the target deployment configuration |
| Hydration Agent |
Temporary OCI compute instance that reads source snapshots and writes to OCI Block Volumes |
| Remote Agent Appliance |
VM deployed in VMware with plugins for Discovery, Replication, and AgentHealthMonitoring |
| Replication Schedule |
User-defined schedule for replicating source data per migration asset |
5. Assessment Methodology
Migration assessment is the systematic evaluation of the source environment to determine what to migrate, how to migrate it, and what it will cost. The exam tests all five assessment dimensions.
Compute Assessment
| Assessment Area |
What to Evaluate |
| CPU and memory utilization |
Right-size OCI shapes based on actual usage, not provisioned capacity |
| Operating system compatibility |
Verify OS version support on OCI Compute |
| Architecture |
x86 vs. ARM (Ampere A1 on OCI) workload compatibility |
| Licensing |
BYOL eligibility, processor metric mapping (on-premises cores to OCI OCPUs) |
| Performance baselines |
The Cloud Migrations Recommendation Engine uses collected performance statistics to suggest OCI compute shapes |
Storage and Data Assessment
| Assessment Area |
What to Evaluate |
| Volume and type |
Total data volume, block vs. object vs. file storage needs |
| IOPS and throughput |
Match performance requirements to OCI Block Volume performance tiers |
| Transfer method |
Online (HTTPS replication) vs. offline (OCI Data Transfer Appliance for large datasets) |
| Database size and type |
Determines whether OCI Database Migration, Data Pump, or GoldenGate is appropriate |
| Retention requirements |
Archive storage tiers for infrequently accessed data |
Network and Security Assessment
| Assessment Area |
What to Evaluate |
| Bandwidth requirements |
Determines FastConnect circuit size or VPN throughput needs |
| Latency sensitivity |
Affects region selection and connectivity type (FastConnect vs. VPN vs. internet) |
| IP address dependencies |
Applications with hardcoded IPs may need OCI Bring Your Own IP (BYOIP) |
| Firewall and security rules |
Map on-premises firewall rules to OCI Security Lists and Network Security Groups |
| DNS requirements |
Plan DNS cutover and consider OCI DNS for resolution |
| Load balancing |
Map current load balancer configurations to OCI Load Balancer or Network Load Balancer |
Compliance Assessment
The OCI CAF Risk and Compliance documentation defines a 12-step regulatory analysis process:
- Identify applicable regulations by geography and industry
- Assemble a cross-functional compliance team
- Research and document specific regulatory requirements
- Identify data types and sensitivity levels (PII, financial, health records)
- Map data flows between on-premises and cloud
- Interpret regulations for cloud-specific applicability
- Perform gap analysis against current practices
- Conduct Data Privacy Impact Assessment (DPIA)
- Develop compliance strategy with specific controls
- Collaborate with legal and compliance experts
- Review and obtain stakeholder approval
- Document and maintain audit-ready records
| Regulation |
Scope |
Key OCI Consideration |
| GDPR |
EU data protection |
Data residency in EU OCI regions, encryption, breach response |
| HIPAA |
US healthcare data |
ePHI protection, audit logs, risk assessments |
| PCI DSS |
Payment card data |
Cardholder data encryption, vulnerability scans |
| SOX |
US financial reporting |
Access controls, segregation of duties, transaction monitoring |
| CCPA |
California consumer privacy |
Personal data collection and use controls |
Exam trap: Compliance is not just about where data is stored. It includes data flows (how data moves between environments), access controls (who can see the data), audit logging (proving compliance), and breach response (notification timelines). The exam may present scenarios where data residency is satisfied but another compliance dimension is not.
Application Assessment
| Assessment Area |
What to Evaluate |
| Dependencies |
Map application-to-application and application-to-infrastructure dependencies |
| Migration group sequencing |
Applications with tight dependencies must migrate together |
| Modernization candidacy |
Determine which applications benefit from refactoring vs. rehosting |
| Business criticality |
Drives migration priority and acceptable downtime windows |
| Technical debt |
Legacy frameworks, unsupported libraries, or deprecated APIs that complicate migration |
6. Oracle Cloud Adoption Framework (CAF)
The OCI CAF provides prescriptive guidance across six pillars. Each pillar is independently addressable, and the framework is iterative.
| Pillar |
Focus |
Exam-Relevant Details |
| Business Strategy |
Business case, TCO, KPIs |
Build the financial justification; align cloud adoption to business goals |
| People Strategy |
Cloud Center of Excellence, training, change management |
CCoE is a multidisciplinary team (business + technical) leading organizational change |
| Security |
Architecture, controls, drift prevention |
Define foundational security controls before migration begins |
| Process Design |
Enterprise architecture, governance, risk, compliance |
Establish governance model and risk guidelines; evaluate hybrid/multi-vendor approaches |
| Technology Implementation |
Landing Zone, migration execution, cloud-native development |
Landing Zone is the Terraform-based foundation meeting CIS OCI Foundations Benchmark |
| Management and Operations |
Post-deployment optimization, cost management, growth readiness |
Ongoing performance optimization and cost management after migration |
Exam trap: The CAF is not a linear, one-time process. It is iterative. Organizations revisit pillars as priorities evolve. A question may present a scenario where an organization skips directly to Technology Implementation without completing Business Strategy or People Strategy -- this is incorrect according to the framework.
7. Total Cost of Ownership (TCO) Analysis
The OCI Business Case documentation defines TCO as the sum of all costs involved in purchasing, operating, and maintaining IT assets over their lifetime.
On-Premises Cost Categories (What You Compare Against)
| Cost Area |
Examples |
| Compute |
Servers, rack chassis, PDUs, top-of-rack switches, hardware maintenance contracts |
| Storage |
Disk arrays, FC SAN switches, maintenance |
| Networking |
LAN switches, load balancers, bandwidth, maintenance |
| Facilities |
Data center space, power, cooling, physical security |
| Security |
Firewalls, NDS/IDS appliances, maintenance |
| Software |
Licenses, annual renewals, version upgrades |
| People |
Hiring, training, salaries for infrastructure management |
| Disaster Recovery |
Alternate site costs, idling DR infrastructure |
OCI Cost Advantages
| Metric |
OCI Position |
| Compute price-performance |
>3x better than AWS (OCI Value Proposition) |
| Network egress |
74% less than AWS |
| HPC workloads |
Comparable performance at 44% lower cost |
| Global pricing |
Consistent pricing across all regions (no regional price variation) |
| SLAs |
Most comprehensive in industry (availability + manageability + performance) |
Tangible vs. Intangible Benefits
| Tangible (Quantifiable) |
Intangible (Strategic) |
| Data center operating cost reduction |
Increased agility |
| Capital equipment elimination |
Faster time to market |
| Labor cost reduction via managed services |
Elastic demand response |
| Security and compliance cost reduction |
Technology modernization |
| Training cost reduction |
Simplified operating environment |
| OpEx consumption model (pay-as-you-use) |
Improved competitive position |
Exam trap: TCO analysis must include opportunity costs -- the cost of NOT migrating. A like-to-like cost comparison (on-premises server cost vs. OCI compute cost) is insufficient. The business case must also account for what the organization loses by staying on-premises: slower innovation, hardware refresh cycles, inability to scale elastically.
8. OCI Migration Tools Summary
| Tool |
Purpose |
Migration Strategy |
| Oracle Cloud Migrations |
End-to-end VM migration from VMware and AWS EC2 |
Rehost |
| OCI Database Migration |
Database migration with minimal downtime |
Rehost/Replatform |
| OCI Data Transfer |
Offline data transfer via physical appliance |
Data migration |
| Oracle Cloud VMware Solution (OCVS) |
Run VMware natively on OCI bare metal |
Relocate |
| OCI Container Engine for Kubernetes (OKE) |
Run containerized workloads |
Refactor |
| OCI Resource Manager |
Terraform-based infrastructure deployment |
All strategies |
| RackWare, ZConverter, Commvault |
Third-party migration tools for physical/virtual workloads |
Rehost |
Key Concepts for Exam Preparation
Quick-Reference Decision Matrix
| Scenario |
Recommended Strategy |
| "Move to cloud as fast as possible with minimal changes" |
Rehost |
| "Migrate database to a managed service but keep app code the same" |
Replatform |
| "Redesign for microservices and containers" |
Refactor |
| "Replace legacy CRM with SaaS" |
Repurchase |
| "Application is redundant, nobody uses it" |
Retire |
| "Cannot migrate due to regulation, revisit next year" |
Retain |
| "Move entire VMware environment to cloud without changes" |
Relocate |
Likely Exam Traps Summary
- Rehost is not Relocate -- Rehost moves individual VMs to OCI Compute; Relocate moves the entire VMware layer to OCVS.
- Replication is independent of planning -- You can replicate data before your migration plan is finalized.
- VMware discovery is agent-based; AWS discovery is agentless -- Do not confuse the two connectivity models.
- TCO must include intangible benefits and opportunity costs -- A pure hardware cost comparison is incomplete.
- CAF is iterative, not linear -- Pillars can be revisited; skipping pillars is an anti-pattern.
- Compliance goes beyond data residency -- Access controls, audit logging, breach notification, and data flow mapping are all compliance dimensions.
- The Recommendation Engine suggests shapes, not mandates -- Its output is a customizable starting point, not a final configuration.
- Temporary migration resources are billed -- Hydration agents, temporary VCNs, and Object Storage buckets created during migration incur normal OCI charges.
References
- Oracle Cloud Migrations Overview -- Service architecture, workflow phases, terminology
- Oracle Cloud Adoption Framework -- Six pillars, iterative methodology
- OCI CAF Business Case -- TCO analysis, ROI methodology, cost categories
- OCI CAF Risk and Compliance -- 12-step regulatory analysis, risk register, compliance frameworks
- OCI Value Proposition -- Price-performance data, security architecture, deployment flexibility
- Oracle Cloud Migration Hub -- Migration tools, supported workloads, four-phase methodology
- 1Z0-1123-25 Exam Page -- Official exam objectives and format