Oracle Database to Azure Migration Center¶
The definitive resource for migrating from Oracle Database to Microsoft Azure -- whether displacing Oracle entirely with Azure SQL or PostgreSQL, or embracing Oracle Database@Azure for workloads that must remain on Oracle.
Who this is for¶
This migration center serves federal CIOs, CDOs, Chief Data Architects, database administrators, platform engineers, and application teams who are evaluating or executing a migration from Oracle Database to Azure-native managed databases. Whether you are responding to Oracle license renewal sticker shock, an open-source mandate, audit risk mitigation, or a strategic consolidation onto Azure, these resources provide the evidence, patterns, and step-by-step guidance to execute confidently.
Audience by role¶
| Role | Start here | Key concern |
|---|---|---|
| CIO / CDO / Executive sponsor | Why Azure over Oracle | Strategic rationale, vendor risk, innovation velocity |
| CFO / Procurement | TCO Analysis | Licensing savings, ⅗-year projections, audit risk elimination |
| Enterprise Architect | Feature Mapping | Capability parity, gap analysis, architectural decisions |
| DBA / Database Engineer | Schema Migration | PL/SQL conversion, data type mapping, performance tuning |
| Application Developer | Azure SQL Migration | Connection string changes, ORM updates, query refactoring |
| Security / Compliance | Security Migration | VPD migration, encryption, audit, FedRAMP inheritance |
| Federal Program Manager | Federal Migration Guide | IL compliance, MACC credits, Oracle in Gov regions |
Quick-start decision matrix¶
| Your situation | Start here |
|---|---|
| Executive evaluating Oracle displacement | Why Azure over Oracle |
| Need cost justification for migration | Total Cost of Ownership Analysis |
| Need a feature-by-feature comparison | Complete Feature Mapping (50+ features) |
| Standard OLTP, moderate PL/SQL complexity | Azure SQL MI Migration |
| Open-source mandate or PostgreSQL preference | PostgreSQL Migration |
| Cannot refactor, must keep Oracle engine | Oracle Database@Azure |
| Need PL/SQL to T-SQL conversion patterns | Schema Migration |
| Planning data movement strategy | Data Migration |
| Federal/government-specific requirements | Federal Migration Guide |
| Want a hands-on SSMA walkthrough | Tutorial: SSMA Migration |
| Want a hands-on ora2pg walkthrough | Tutorial: Oracle to PostgreSQL |
| Need performance comparison data | Benchmarks |
| Ready to plan full migration | Migration Playbook |
Target platform comparison¶
The first and most consequential decision is which Azure database platform to target. Oracle workloads typically land on one of four targets.
| Criterion | Azure SQL MI | Azure PostgreSQL | Oracle DB@Azure | SQL Server on VM |
|---|---|---|---|---|
| Best for | OLTP, moderate PL/SQL, Microsoft ecosystem | Open-source mandate, cost-sensitive, PostgreSQL-compatible | Complex RAC/Exadata, deep PL/SQL, cannot refactor | Legacy apps needing full SQL Server control |
| License cost | Included in service | None (open source) | Oracle licensing required (MACC eligible) | SQL Server license (AHB eligible) |
| PL/SQL conversion | SSMA (automated 80%+) | ora2pg (automated 60-70%) | Not required | SSMA (automated 80%+) |
| High availability | Built-in (99.99% SLA) | Built-in (zone-redundant) | RAC + Data Guard | Always On (customer-managed) |
| Max database size | 16 TB | 64 TB | Exadata scale | VM disk limits |
| Horizontal scale-out | Elastic pools | Citus extension | RAC | Not built-in |
| Managed service | Yes (PaaS) | Yes (PaaS) | Yes (Oracle-managed Exadata) | No (IaaS) |
| Fabric Mirroring | GA | Via ADF pipelines | Preview (Mirroring for Oracle) | Via ADF pipelines |
| Gov region availability | GA in Azure Gov | GA in Azure Gov | Roadmap for Azure Gov | GA in Azure Gov |
| Migration complexity | Medium | Medium-High | Low (lift and shift) | Medium |
How CSA-in-a-Box fits¶
Regardless of which target database you choose, CSA-in-a-Box serves as the unified analytics, governance, and AI platform that consumes data from migrated Oracle workloads.
flowchart TB
subgraph Oracle["Oracle Source Estate"]
direction LR
OLTP[OLTP Databases]
DW[Data Warehouses]
EBS[E-Business Suite]
end
subgraph Targets["Azure Database Tier"]
direction LR
SQL[Azure SQL MI]
PG[Azure PostgreSQL]
ORA[Oracle DB@Azure]
end
subgraph CSA["CSA-in-a-Box Platform"]
direction TB
subgraph Ingest["Ingestion Layer"]
MIRROR[Fabric Mirroring]
ADF_I[Azure Data Factory]
end
subgraph Lake["Lakehouse Layer"]
ONELAKE[OneLake + Delta Lake]
DBT[dbt Medallion Models]
end
subgraph Govern["Governance Layer"]
PURVIEW[Microsoft Purview]
CLASSIFY[Classifications + Lineage]
end
subgraph Serve["Serving Layer"]
PBI[Power BI + Direct Lake]
AIFD[Azure AI Foundry]
end
end
OLTP --> SQL
OLTP --> PG
OLTP --> ORA
DW --> SQL
EBS --> SQL
SQL --> MIRROR
PG --> ADF_I
ORA --> MIRROR
MIRROR --> ONELAKE
ADF_I --> ONELAKE
ONELAKE --> DBT
DBT --> PURVIEW
PURVIEW --> CLASSIFY
DBT --> PBI
DBT --> AIFD Key integration patterns:
- Fabric Mirroring replicates Azure SQL MI and Oracle DB@Azure tables to OneLake in near-real-time, enabling analytics without impacting transactional workloads
- Azure Data Factory pipelines in
domains/shared/pipelines/adf/orchestrate batch ingestion from PostgreSQL and other sources into the CSA-in-a-Box medallion architecture - Microsoft Purview in
csa_platform/csa_platform/governance/purview/catalogs migrated databases, applies data classifications (PII, CUI, PHI), and maintains end-to-end lineage - dbt models in
domains/shared/dbt/transform raw Oracle data through bronze/silver/gold layers with enforced contracts - Power BI with Direct Lake serves analytics directly from OneLake with no data copy
Strategic resources¶
Documents providing the business case, cost analysis, and strategic framing for decision-makers.
| Document | Audience | Description |
|---|---|---|
| Why Azure over Oracle | CIO / CDO / Board | Executive brief: licensing economics, open-source maturity, cloud-native advantages, AI integration, talent availability |
| Total Cost of Ownership | CFO / CIO / Procurement | Oracle licensing breakdown (EE + RAC + options + 22% support), Azure target cost modeling, ⅗-year projections, audit risk quantification |
| Feature Mapping | CTO / Enterprise Architecture | 50+ Oracle features mapped to Azure equivalents with conversion complexity and CSA-in-a-Box integration notes |
| Benchmarks | CTO / Platform Engineering | Query performance, transaction throughput, IOPS, concurrent session handling, cost-per-transaction comparison |
Migration guides¶
Target-specific deep dives covering every aspect of an Oracle-to-Azure migration.
| Guide | Migration path | Key tools |
|---|---|---|
| Azure SQL MI Migration | Oracle to Azure SQL Managed Instance | SSMA, Azure DMS, Fabric Mirroring |
| PostgreSQL Migration | Oracle to Azure Database for PostgreSQL | ora2pg, pgloader, Citus |
| Oracle Database@Azure | Oracle to Oracle DB@Azure (Exadata in Azure) | ZDM, Data Guard, GoldenGate |
| Schema Migration | PL/SQL to T-SQL and PL/pgSQL conversion patterns | SSMA, ora2pg, manual refactoring |
| Data Migration | Data movement strategies and tools | Azure DMS, ADF, Data Pump, Fabric Mirroring, GoldenGate |
| Security Migration | Oracle security model to Azure security model | VPD to RLS, TDE key migration, audit migration |
Tutorials¶
Hands-on, step-by-step walkthroughs for common migration scenarios.
| Tutorial | Duration | What you will build |
|---|---|---|
| SSMA Migration to Azure SQL MI | 3-4 hours | Install SSMA, assess an Oracle database, convert schema, remediate issues, migrate data, validate on Azure SQL MI |
| Oracle to PostgreSQL with ora2pg | 3-4 hours | Install ora2pg, analyze Oracle schema, convert to PostgreSQL, deploy to Azure Database for PostgreSQL Flexible Server, validate |
Federal and government¶
| Document | Description |
|---|---|
| Federal Migration Guide | Oracle displacement in federal agencies, Azure Gov region availability, FedRAMP/IL compliance, Oracle licensing audits in government, MACC for Oracle DB@Azure |
Assessment and planning¶
| Document | Description |
|---|---|
| Best Practices | Assessment methodology (SSMA assessment report), complexity tiers, workload decomposition, application testing strategy, parallel-run validation, CSA-in-a-Box integration |
Timeline expectations¶
Migration timelines depend heavily on Oracle estate complexity. These are representative ranges.
| Oracle estate size | Databases | PL/SQL complexity | Typical duration |
|---|---|---|---|
| Small | 1-5 databases, < 1 TB | Low (< 50 stored procedures) | 8-12 weeks |
| Medium | 5-20 databases, 1-10 TB | Medium (50-500 stored procedures, some packages) | 16-24 weeks |
| Large | 20-100 databases, 10-100 TB | High (500+ stored procedures, RAC, partitioning) | 24-40 weeks |
| Enterprise | 100+ databases, 100+ TB | Very high (complex PL/SQL, AQ, Spatial, VPD) | 40-60+ weeks |
Navigation¶
By migration phase¶
- Assess: Feature Mapping | TCO Analysis | Benchmarks
- Plan: Migration Playbook | Best Practices | Federal Guide
- Convert: Schema Migration | Azure SQL Migration | PostgreSQL Migration
- Move: Data Migration | Security Migration
- Validate: Benchmarks | Best Practices
- Optimize: CSA-in-a-Box integration | Cost Management
By Oracle feature¶
| Oracle feature | Conversion guide |
|---|---|
| PL/SQL packages, procedures, functions | Schema Migration |
| RAC (Real Application Clusters) | Feature Mapping |
| Data Guard | Feature Mapping |
| Partitioning | Feature Mapping |
| Virtual Private Database (VPD) | Security Migration |
| Transparent Data Encryption (TDE) | Security Migration |
| Advanced Queuing (AQ) | Feature Mapping |
| Oracle Spatial | Feature Mapping |
| Materialized Views | Feature Mapping |
| Oracle Text / Full-Text | Feature Mapping |
Maintainers: csa-inabox core team Last updated: 2026-04-30