OCI Migration Architect study plan

Map every assessment input you would request from a stakeholder (inventory, dependency, performance baseline, compliance constraints) into a checklist you can reuse

Explain the difference between rehost, replatform, refactor, and retire decisions and justify one choice per workload archetype

Draft a discovery questionnaire that captures application-to-database coupling and network egress dependencies

Identify the top five OCI migration blockers (licensing, latency, data residency, identity, unsupported features) and note how each is detected early

Build a workload sizing worksheet that converts on-premises CPU, memory, and IOPS into OCI shape candidates

Derive a total cost of ownership comparison that includes compute, storage, egress, and support tiers

Sequence a migration wave plan by dependency depth and business criticality

Define rollback criteria and decision gates for each wave

Design a VCN layout with public and private subnets, route tables, and a NAT plus service gateway pattern for migration traffic

Select a connectivity option (Site-to-Site VPN, FastConnect, or hybrid combination) for a given bandwidth and latency requirement and justify it

Configure security lists versus network security groups and articulate when each applies

Plan DNS strategy including private zones and cutover of resolver settings

Size a FastConnect or VPN path against measured data transfer volume and available cutover window

Design load balancing and traffic management for a phased application cutover

Identify inspection and firewall insertion points without breaking replication flows

Document failure domains and availability domain placement for migrated tiers

Compare database migration methods (logical export/import, physical backup and restore, and change-data-capture replication) and pick one per scenario

Plan schema conversion steps including character set, data type, and PL/SQL compatibility checks

Design an application migration approach for containerized and non-containerized tiers with configuration externalization

Define data validation queries and reconciliation checks to run before and after cutover

Estimate downtime for each migration method and match it to business tolerance

Plan identity and secrets migration including federation and credential rotation

Design a test and performance validation plan that compares baseline against OCI results

Identify application dependencies on legacy platform services and map each to an OCI equivalent or a workaround

Write a cutover runbook with timestamped steps, owners, communication points, and abort conditions

Define pre-cutover and post-cutover validation checklists including smoke tests and data integrity checks

Plan a pilot migration and a rehearsal with measured results

Design monitoring, logging, and alerting for the post-migration steady state

Run a full mock cutover against your runbook and record every deviation

Define hypercare exit criteria and the handover package to operations

Revisit the assessment checklist and wave plan to incorporate lessons learned

Complete timed practice across all four domains and review every missed item