Most candidates pass with 70 to 140 focused hours, depending on migration and networking background. The best use of time is to study by migration phase and cutover risk, not by memorizing disconnected tool names.
How to use this plan well
Each study block should do four things:
- classify the problem as assess, prepare, move, validate, cut over, or stabilize
- decide which connectivity or migration control belongs there
- do a short scenario set
- write down whether the miss was dependency order, validation weakness, or cutover risk
flowchart LR
Classify["Classify migration phase"] --> Choose["Choose path or control"]
Choose --> Drill["Do short scenario set"]
Drill --> Review["Review why misses happened"]
Review --> Classify
How long should you study?
| Your time |
Recommended timeline |
Good fit |
| 18 to 22 hrs/week |
30 days |
intensive path with some migration exposure |
| 10 to 14 hrs/week |
60 days |
balanced path for most candidates |
| 6 to 9 hrs/week |
90 days |
part-time path with slower reinforcement |
30-day intensive plan
| Week |
Focus |
Output |
| 1 |
discovery, dependency mapping, inventory, and landing-zone prep |
phase-order notes and short drills |
| 2 |
connectivity, networking patterns, VPN, FastConnect, DRG, and DNS |
path-choice tie-break sheet |
| 3 |
data movement, database migration, validation, and cutover planning |
weak-lane notes and mixed sets |
| 4 |
stabilization, observability, rollback, and final readiness |
mixed sets and compression |
60-day balanced plan
| Phase |
Weeks |
Focus |
| 1 |
1 to 2 |
terminology cleanup and migration-phase classification |
| 2 |
3 to 4 |
inventory, dependencies, landing-zone and network prep |
| 3 |
5 to 6 |
connectivity, transfer paths, and migration tools |
| 4 |
7 |
validation, cutover, rollback, and downtime logic |
| 5 |
8 |
stabilization, observability, and operational ownership |
| 6 |
9 to 10 |
weak-lane repair and final mixed review |
90-day part-time plan
| Month |
Focus |
Goal |
| 1 |
migration vocabulary and phase order |
stop losing points to sequence confusion |
| 2 |
connectivity, movement, and cutover planning |
build stronger migration judgment |
| 3 |
validation, rollback, and stabilization |
finish with mixed-set confidence |
If misses cluster here, do this next
| Miss pattern |
Weak lane |
Fix next |
| you keep choosing the wrong path into OCI |
connectivity |
review VPN, FastConnect, DRG, DNS, and hybrid path logic |
| you move too fast to cutover |
validation |
review readiness checks, rollback triggers, and outage tolerance |
| you solve transfer but not production switch |
cutover |
review sequencing, ownership, and change-control logic |
| you treat migration as one big move |
phase separation |
review assess vs move vs validate vs stabilize |
What strong prep usually does
- classifies the phase first, then picks the tool or path
- keeps a short confusion list for staging vs cutover and validation vs rollback
- writes down why the winning answer preserves safer rollback and clearer ownership instead of just memorizing it
- uses Oracle docs to settle disagreements, then comes back here for compression
Final 72 hours
| Keep doing |
Stop doing |
| rereading the cheat sheet and glossary |
opening unrelated new migration services |
| reviewing weak-lane misses |
treating every migration problem like a data-copy problem |
| checking official docs for disputed boundaries |
building a large new migration lab late |
| practicing migration-phase classification |
trusting unsupported blog summaries over Oracle docs |
Route yourself well
- cutover and connectivity traps: Cheat Sheet
- high-confusion migration terms: Glossary
- last-week questions: FAQ
- official Oracle and OCI source routing: Resources