A focused course, tailored for you
The Oracle Cloud Workload Migration Reference
An OCI-anchored workload migration reference for the customer enterprise architect: Exadata Cloud Service positioning, OCI-Azure Interconnect pattern, sovereign cloud topology, OCI Database 23ai feature landing.
Oracle Cloud Solution Architects face customer enterprise architects who arrived with three lift-and-shift options on the slide. The course delivers the OCI-anchored migration reference that wins the architecture decision.
$199 one-time
Tailored to your situation. Access within 24 hours. 30-day money-back.
Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.
Why this course
Oracle Cloud Solution Architects in 2026 face a customer enterprise architect who arrived with three lift-and-shift options on the slide: AWS RDS Custom for Oracle, Azure SQL Managed Instance, or OCI. The default OCI pitch is the database-on-Exadata-Cloud-Service story. The enterprise architect already heard it. The conversation needs to move past the headline into the integrated OCI-anchored answer: the OCI-Azure Interconnect pattern for the customer's hybrid posture, the sovereign-cloud topology for the customer's data-residency obligations, the OCI Database 23ai feature landing (JSON Duality, AI Vector Search, True Cache), and the FinOps story that the customer's CFO signs.
The course works through the integrated reference. The Exadata Cloud Service positioning that does not pretend to be a generic cloud database. The OCI-Azure Interconnect pattern that respects the customer's Microsoft-heavy enterprise stack. The sovereign-cloud topology (OCI Dedicated Region, OCI for EU Sovereign Cloud, OCI for Government). The OCI Database 23ai feature landing. The customer-side identity federation. The FinOps story. The shared-responsibility framing. Twelve modules with deliverables. Plus a hand-built playbook for your account mix.
What you walk away with
- A documented Exadata Cloud Service positioning.
- An OCI-Azure Interconnect pattern.
- A sovereign-cloud topology.
- An OCI Database 23ai feature landing pattern.
- A customer-side identity federation pattern.
- A FinOps story the CFO signs.
- A shared-responsibility framing.
- A 10-week build plan.
The 12 modules
Module 1. The 2026 OCI enterprise landscape
Walkthrough of the 2026 OCI enterprise landscape. The customer cohort that has lift-and-shift options on the slide. The Microsoft-heavy enterprise stack profile. The Oracle E-Business Suite and PeopleSoft and JD Edwards customer cohort. The sovereign-cloud customer cohort. The competitive landscape against AWS RDS Custom for Oracle, Azure SQL Managed Instance, and the hyperscaler-native alternatives. The strategic decisions an OCI Solution Architect faces.
Module 2. Exadata Cloud Service positioning
Build the Exadata Cloud Service positioning. The Exadata-specific feature set the customer DBA has been using for years. The Smart Scan pattern. The Hybrid Columnar Compression pattern. The Real Application Clusters pattern in cloud. The contrast with AWS RDS Custom for Oracle and Azure SQL Managed Instance feature-by-feature. The integration with the customer's existing Exadata operating model.
Module 3. OCI-Azure Interconnect pattern
Build the OCI-Azure Interconnect pattern. The customer's Microsoft-heavy enterprise stack. The application-on-Azure-database-on-OCI pattern. The low-latency cross-cloud network topology. The identity federation across Azure AD and OCI IAM. The customer's existing Microsoft enterprise agreement integration. Plus the worked example for a customer with .NET applications on Azure and Oracle EBS on OCI.
Module 4. Sovereign cloud topology
Build the sovereign-cloud topology. OCI Dedicated Region for on-premise sovereignty. OCI for EU Sovereign Cloud for EU data residency. OCI for Government for federal customer programmes. The integration with the customer's existing data-classification framework. The integration with the customer's existing regulatory engagement cadence. Plus the worked example for the customer's first sovereign-cloud workload landing pattern.
Module 5. OCI Database 23ai feature landing
Build the OCI Database 23ai feature landing. JSON Relational Duality as a database primitive. AI Vector Search for retrieval-augmented workloads. True Cache for distributed caching. The customer-side application change pattern for each feature. The integration with the customer's existing development cadence. Plus the worked example for the customer's first three 23ai feature adoptions.
Module 6. Identity federation pattern
Build the customer-side identity federation pattern. The integration with the customer's existing identity provider (Microsoft Entra ID, Okta, Ping Identity). The SCIM provisioning pattern. The role-based access pattern. The customer-side audit-trail integration. The break-glass pattern. The integration with the customer's existing privileged-access-management cadence. Plus the worked example for the customer's typical user population.
Module 7. FinOps story
Build the FinOps story the CFO signs. The OCI consumption model. The OCI Universal Credits pattern. The customer's existing AWS Savings Plans equivalent translation. The customer's existing Azure Reserved Instances equivalent translation. The customer-side cost-allocation framework. The integration with the customer's existing FinOps cadence. Plus the worked example for the customer's first-year cost model comparison.
Module 8. Shared-responsibility framing
Build the shared-responsibility framing. The customer-managed responsibility list. The Oracle-managed responsibility list. The customer-side risk-management committee integration. The integration with the customer's existing third-party-risk cadence. The audit-trail framework. Plus the worked example for the shared-responsibility document the customer's enterprise architect and customer's CISO sign.
Module 9. Migration workflow
Build the migration workflow. The Zero Downtime Migration pattern. The GoldenGate Veridata pattern. The customer-side test-bed framework. The customer-side cutover-rehearsal pattern. The customer-side stakeholder-communication cadence during cutover. The post-cutover validation framework. Plus the worked example for a customer with three databases under simultaneous migration.
Module 10. Operations and observability
Build the operations and observability pattern. The OCI Monitoring integration. The OCI Logging integration. The customer-side observability stack integration (Datadog, Splunk, OpenSearch). The customer-side SRE-team integration. The customer-side database administration team integration. The on-call rotation pattern. Plus the worked example for the customer's first 90 days post-migration.
Module 11. Customer engagement structure
Build the customer engagement structure. The discovery phase. The reference-architecture phase. The migration-pilot phase. The full-rollout phase. The sustainment phase. The renewal conversation. The integration with the customer's existing Oracle account-team cadence. Plus the worked example for a 12-month customer engagement and the pricing framework for fixed-scope and time-and-materials engagements.
Module 12. Your 10-week build plan
Week by week. Weeks 1-2: landscape and Exadata Cloud Service positioning. Weeks 3-4: OCI-Azure Interconnect and sovereign cloud topology. Weeks 5-6: Database 23ai feature landing and identity federation. Weeks 7-8: FinOps story, shared-responsibility, migration workflow. Weeks 9-10: operations and observability, customer engagement structure. Deliverable: an OCI-anchored workload migration reference ready for the next enterprise customer.
How this addresses your situation
Specific modules that map to what you said you are dealing with.
Customer wants Exadata-on-cloud → Module 2.
Customer is Microsoft-heavy → Module 3.
Customer has sovereignty obligations → Module 4.
Customer wants 23ai features → Module 5.
Customer wants identity federation → Module 6.
Customer CFO needs cost story → Module 7.
Customer needs migration playbook → Module 9.
Customer needs operations → Module 10.
What you get with this course
- The 12-module course delivered as text plus downloadable templates.
- Templates and worked examples for every module.
- A hand-built playbook generated for your account mix.
- Three reference architectures from peer OCI engagements.
- Scripted talking points for the customer enterprise architect and customer CFO engagement.
What you will have in hand by Day 1, Week 1, Month 1
Day 1: Exadata Cloud Service positioning scaffold drafted.
Week 4: OCI-Azure Interconnect and sovereign cloud topology designed.
Week 8: Database 23ai feature landing, identity federation, FinOps, shared-responsibility, migration workflow operational.
Week 10: Reference ready for next enterprise customer.
Before and after
Before
Default OCI pitch is the database-on-Exadata-Cloud-Service story. Enterprise architect already heard it. Conversation stalls. Customer chooses AWS RDS Custom or Azure SQL Managed Instance.
After
Integrated OCI-anchored answer. Sovereign cloud, OCI-Azure Interconnect, 23ai feature landing, FinOps story land in the same conversation. Customer chooses OCI.
What happens if you do not address this
AWS and Azure database-services teams are sharpening their Oracle-workload-migration field motion in 2026. OCI Solution Architects who do not arrive with the integrated answer lose accounts to lift-and-shift alternatives.
Who it is for
For Oracle Cloud Solution Architects, senior cloud architects serving Oracle customers, principal pre-sales solution architects, and senior consultants delivering OCI migration programmes.
Who this is NOT for. Pure non-Oracle practitioners. Practitioners with no enterprise database migration experience. Pure non-architecture roles.
How it arrives
Text-based course via LMS, plus downloadable templates and worked examples and the hand-built playbook.
Time investment. Roughly 18 hours of reading and 60 to 120 hours of build effort across the 10-week plan.
Why $199 is the right number
External OCI architect enablement programmes charge from 100,000 to 500,000 USD. 199 USD buys the focused playbook and the implementation document for your account mix.
FAQ
Does this cover OCI Generative AI Service?
Module 5 covers OCI Generative AI Service in the 23ai-adjacency context.
What about OCI Autonomous Database?
Module 2 covers Autonomous Database as part of the database-cloud-service portfolio positioning.
Does this cover MySQL HeatWave on OCI?
Module 5 covers MySQL HeatWave as part of the broader OCI database portfolio.
What is in the implementation playbook for me specifically?
Reference tuned to your account mix, FinOps story matched to the customer's existing cloud financial pattern, customer engagement structure pre-loaded with your sales cycle.
30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.
