Short answer: OCI migration credits are one-time, time-boxed OCI consumption credits Oracle grants to offset cloud usage during a migration window — not a discount on your committed rate. Paired with free Cloud Lift engineering, they subsidize the move but commit you to a multi-year Universal Credit spend whose full cost arrives once the credits expire.
Definition: OCI migration credits are one-time promotional OCI consumption credits Oracle grants to offset cloud usage during a defined migration window. They reduce your net OCI bill while you move workloads, but they expire if unconsumed and almost always require you to sign or expand an OCI Universal Credit commitment to receive them.
It helps to separate three things Oracle deliberately blends in a migration proposal. The Universal Credit commitment is your multi-year promise to spend a minimum amount on OCI. The discount rate is the percentage off list you pay against that commitment. And migration credits are a separate, finite pool of credits layered on top to subsidize the transition period. The first two define your long-term cost. The third is a short-term sweetener that disappears.
Oracle's account team presents the migration credit as the headline number — "we're giving you $400,000 in credits to move." That framing is designed to anchor the conversation on the gift rather than the commitment. The credit is real, but it is the cheapest part of the deal for Oracle to give, because Oracle only delivers value if you consume OCI services, and consuming OCI services is exactly the multi-year behavior the commitment locks in. The credit is bait for the contract.
For the wider mechanics of how committed OCI spend is drawn down, see our companion guide on OCI Universal Credits and net pricing, and the cluster hub, the Oracle Cloud Licensing Guide.
Short answer: Yes, the engineering labor is free — and no, the program is not without cost. Oracle Cloud Lift Services supplies Oracle architects and migration engineers at no charge, but the program exists to accelerate a Universal Credit commitment, and it architects your workloads around OCI-specific services that raise the cost of leaving later.
Oracle Cloud Lift Services is Oracle's white-glove migration program: Oracle assigns cloud engineers to plan, architect, and execute the move of your workloads onto OCI, at no line-item charge. For a complex Oracle Database or middleware estate, that engineering is worth real money, and the offer is attractive on its face. The labor genuinely is free.
The cost is structural, not invoiced. First, Lift is granted in exchange for a commitment — Oracle funds the engineering because it expects years of OCI consumption in return, so the "free" help is the front end of a long contract. Second, Oracle engineers naturally architect for OCI-native services — Autonomous Database, OCI-specific networking, managed services — which deepens technical lock-in and raises the switching cost if you later want to leave. Third, the Lift scope covers Oracle's side of the migration, not your internal labor: testing, validation, change management, application remediation, and parallel-run operations all remain your cost.
The lock-in mechanism: Free Lift engineering is the most effective lock-in tool Oracle has, precisely because it feels like a favor. The more OCI-native the resulting architecture, the harder and more expensive any future exit becomes — which is exactly why Oracle is willing to staff the migration for free.
None of this means you should refuse Lift. It means you should value it correctly: as a negotiated concession with a price tag attached to the commitment, not as charity. Our Oracle Cloud & OCI Advisory team models the Lift concession against the commitment it funds so you can see the true exchange.
Short answer: OCI migration credits carry a 6–12 month expiry window. Credits unconsumed when the window closes are forfeited — and because migrations routinely slip, enterprises lose part of the credit value and begin paying full committed rates earlier than the business case assumed.
Migration credits are use-it-or-lose-it. Oracle grants the pool with a fixed expiry — frequently 6 to 12 months from the contract or grant date — and any balance remaining at expiry is gone. The structure assumes a migration that completes on Oracle's optimistic schedule, which real enterprise migrations rarely do. Application dependencies surface, testing takes longer than planned, change windows are limited, and the migration that was scoped for six months runs nine or twelve.
When that happens, two costs land at once. You forfeit the unconsumed credit balance, and you start drawing down your committed Universal Credit pool at full rate while still mid-migration — paying for OCI before the workloads that justify it are fully live. The credit that was supposed to de-risk the transition instead penalizes the realistic timeline.
The defense is to negotiate the expiry window against your actual migration plan, not Oracle's, and to secure extension or rollover rights for credits if the migration slips for reasons within normal project variance. For the broader pattern of Oracle's time-boxed cloud incentives, see our analysis of Oracle Cloud Lift Services as a lock-in trap and the migration credit benchmarks that show what Oracle will actually concede.
Short answer: The post-credit cliff is the jump in net OCI cost when promotional migration credits are exhausted and you begin paying full committed rates. TCO models built on the subsidized period understate steady-state cost — often by 30–50% in the first full year after credits expire (Oracle Licensing Experts, 2026).
Picture the cost curve. During migration, credits offset a large share of your OCI bill, so the net monthly spend looks modest. That is the number that tends to reach the board. Then the credits run out, and the curve steps up to your full committed rate with no subsidy underneath it. That step is the cliff, and most migration business cases never plot it.
The size of the cliff depends on how large the credit pool was relative to annual spend and how much of the commitment ramps into the post-credit years. When credits cover a big slice of the first 9–12 months and the commitment ramps upward afterward, the first full unsubsidized year can run 30–50% above the migration-period run rate. An organization that committed to OCI on the strength of the subsidized number is then defending a much larger steady-state bill it never modeled.
The fix is mechanical: build the TCO on the full committed rate with zero migration credit applied, treat the credits as a one-time transition offset booked separately, and only then decide whether OCI's steady-state economics justify the move. If the deal only works with the credits applied, it does not work.
Our Oracle Cloud & OCI Advisory team rebuilds the TCO at full committed rates, separates the credit from the commitment, and benchmarks the ramp — see our energy-sector case study: $3.5M saved on an OCI migration.
The table below separates what the migration credit covers from the costs that remain yours. Use it to stress-test any "free migration" proposal before signing.
| Cost element | Covered by migration credit / Lift? | Who pays in practice |
|---|---|---|
| OCI consumption during migration window | Partly — until credits expire | You, after expiry |
| Oracle migration engineering (architecture, cutover) | Yes — Cloud Lift Services | Oracle, during program |
| Steady-state OCI consumption (post-credit) | No | You, at full committed rate |
| Universal Credit commitment ramp (years 2–3) | No | You |
| Dual-running of source + OCI during overlap | No | You |
| Data egress from incumbent cloud / on-prem | No | You |
| Internal testing, remediation, validation labor | No | You |
| Forfeited credits if migration slips past expiry | N/A — lost value | You |
The pattern is consistent: the credit and Lift cover the visible, front-loaded migration costs, while the recurring, back-loaded costs that define long-term TCO remain entirely yours. That is by design — Oracle subsidizes the decision, not the consequence.
Short answer: Disaggregate the four terms — migration credit, commitment level, discount rate, and ramp schedule — and negotiate each on its own merits. Size the commitment to realistic consumption, model cost at full rate after credits expire, and secure rollover and ramp-relief rights so a slipped migration does not become a penalty.
The five moves that consistently improve an OCI migration deal:
Done well, an OCI migration with credits and Lift can be a sound commercial decision. The failure mode is accepting Oracle's framing — credit as gift, commitment as formality, steady-state cost as an afterthought. Reverse that order and the offer becomes negotiable rather than predetermined.
OCI migration credits are one-time promotional OCI consumption credits Oracle grants to offset cloud usage during a defined migration window. They are not a discount on your committed rate — they are time-boxed credits that expire if unconsumed, and they typically require you to sign or expand an OCI Universal Credit commitment to receive them.
The engineering labor is genuinely free. Oracle provides architects and migration engineers at no line-item charge. The hidden cost is commercial: Lift is funded to accelerate a 3–5 year OCI consumption commitment, and Oracle engineers architect for OCI-native services that raise the cost of leaving later. Value it as a negotiated concession, not charity.
Yes. OCI migration credits carry an expiry window — commonly 6 to 12 months from grant. Credits unconsumed at the end of the window are forfeited. Enterprises whose migrations slip behind schedule routinely lose part of the credit value, then begin paying full committed rates earlier than the business case assumed.
The post-credit cliff is the jump in net OCI cost when promotional migration credits are exhausted and you begin drawing down your committed Universal Credit pool at full rate. TCO models built on the credit-subsidized period understate steady-state cost, often by 30 to 50 percent in the first full year after credits expire.
Yes. Migration credits, the Universal Credit commitment level, the discount rate, and the ramp schedule are four separate negotiable terms. Oracle prefers to bundle them so the credit value masks an aggressive commitment. Disaggregate each term, model steady-state cost after credits expire, and never let the credit headline drive the commitment size.
The main hidden costs are credit-expiry forfeiture, an inflated Universal Credit commitment, a back-loaded ramp schedule, dual-running costs while both environments operate, data egress from your incumbent cloud, internal labor outside the Lift scope, and post-credit cliff pricing once the subsidy ends.
Generally no. Migration credits are tied to a specific commitment level. Reducing the commitment typically reduces or voids the credit grant. This is why the commitment size — not the credit headline — should anchor your negotiation; the credit follows the commitment, not the other way around.
OCI pricing changes, migration-credit benchmarks, and Universal Credit negotiation tactics delivered to enterprise Oracle stakeholders.
Former Oracle cloud executives rebuild your migration TCO at full committed rates, separate the credit from the commitment, and structure the negotiation — giving you the analysis Oracle's account team doesn't volunteer. Not affiliated with Oracle Corporation.