Here’s the number before you get routed to an Oracle sales rep: moving an Oracle database to the cloud costs from about $40,000 for a rehost to $200,000 to $400,000-plus for a full refactor, and the migration tooling itself can be free. OCI Database Migration is free for the first 6 months. The number that actually decides your total cost isn’t the migration. It’s the licensing you run afterward. If you want that modeled for your workload, reach out.
Oracle migrations get quoted as a one-time project, and that framing hides the expensive part. The move is a few months. The Oracle license bill is forever, and one decision made during the move sets it. This post prices both.
We’re gmware, a software development firm headquartered in Austin, TX, with engineering centers in Bangalore and Mohali, India. Cloud migration and legacy modernization are core service lines. Below: the cost by migration approach, the OCI run-cost math, the BYOL lever, and the honest call on when to rehost instead of rewrite.
Oracle cloud migration cost by approach
What does Oracle to cloud migration cost by approach?
The approach you pick sets the number, and the approach should be set by the reason you’re moving, not by the biggest tier a vendor can sell you. These ranges come from 2026 cloud-migration market data.
| Approach | What it means | Cost | When it fits |
|---|---|---|---|
| Rehost (lift-and-shift) | Move the database as-is to cloud infrastructure | $40,000 to $100,000 | Data-center exit on a deadline, database works fine |
| Replatform | Move plus targeted changes (managed service, minor tuning) | $100,000 to $200,000 | Some optimization wanted, not a rewrite |
| Refactor / re-architect | Redesign the data layer for the cloud | $200,000 to $400,000+ | The old architecture is the actual problem |
Read this bottom-up and be suspicious of the bottom row. A lot of Oracle migrations get sold as refactors when the client needed a rehost. If the database does its job and the reason you’re moving is “the data center lease is up,” pay for the rehost, exit on time, and refactor later if you ever actually need to. Paying $300,000 to re-architect a database that works is a way to spend money, not save it.
Is OCI Database Migration really free?
Yes, and it’s a real lever, not a marketing asterisk. OCI Database Migration is free for up to 6 months (183 days), as long as the job doesn’t sit idle for more than 60 days. It’s a fully managed service that uses Zero Downtime Migration, the Cloud Premigration Advisor Tool, Data Pump, and GoldenGate to move Oracle databases from on-prem or other clouds into OCI.
So the tooling license during the move is zero. What you still pay for is the engineering: planning the cutover, remapping any schema that changed, validating that the target produces the same answers as the source, and designing the parallel run. That’s true of every migration, and we wrote up the general version in data migration cost. The free tool is nice. It doesn’t do the thinking.
The number that actually matters: OCI run cost and BYOL
Here’s where teams lose the plot. They negotiate the migration cost hard, then ignore the monthly OCI bill, which is the number they’ll pay every month for years. A serious Oracle deployment on OCI is expensive at list. An Exadata Cloud instance can run into six figures a month without licensing help.
Then bring-your-own-license changes everything. BYOL cuts the database line by up to 80% for Database VM Enterprise Edition and 67% for Autonomous Database Serverless. That’s not a rounding error. That’s the difference between a migration that pays for itself and one that doesn’t.
What BYOL cuts off the OCI database line
Egress is the other line people fear and shouldn’t, at least on OCI. Outbound data transfer is free for the first 10 TB per month per tenancy, then $0.0085 per GB. That’s genuinely low, and for a database workload it’s rarely the line that hurts. The line that hurts is the license, so model the monthly run cost with and without BYOL before you commit to anything. If you want that monthly number worked out for your workload, reach out.
When to rehost, and when a rewrite is worth it
The single most useful question in an Oracle migration is: what problem are you actually solving? Answer that honestly and the approach picks itself.
Rehost when you’re exiting a data center on a deadline and the database is doing its job. It’s the cheapest, fastest path, and it doesn’t foreclose anything. You can optimize later once you’re stable in the cloud.
Refactor when the Oracle architecture or licensing is the problem. If you’re moving specifically to get off expensive Oracle features, break up a monolithic schema, or re-architect for scale you don’t have today, then the rewrite is the point and the higher cost buys something real. If you’re moving because a lease is up, it doesn’t.
Here’s an opinion we’ll defend: most Oracle migrations should start as rehosts. Get out of the data center, get stable, then decide what’s actually worth re-architecting with real cloud production data in hand instead of a whiteboard guess. Trying to migrate and re-architect in one motion is how a six-month project becomes an eighteen-month one. For the broader legacy picture, our legacy application modernization cost guide covers the rehost-versus-rewrite trade-off across older systems, not just Oracle.
How gmware scopes an Oracle migration
We start by asking why you’re moving, because that answer sets the whole budget. If it’s a data-center exit, we scope the cheapest safe rehost and get you out on time. If the Oracle licensing is the pain, we model BYOL versus license-included so you see the monthly number before you commit, because that recurring cost dwarfs the one-time move. Sometimes the assessment ends with us telling you to rehost now and revisit the rewrite in a year. We’d rather give you the cheaper honest answer than sell the bigger project.
Delivery runs through our cloud migration practice: senior engineers in Bangalore and Mohali, architecture and accountability in Austin, hours that overlap yours. Zero-downtime cutovers get designed and validated, not hoped for.
Tell us what you’re running, why you’re moving, and what your Oracle licensing looks like. Reach out and we’ll give you a straight answer on approach, cost, and the monthly run number within 48 hours.