What does Analytics Cloud migration involve?
Migrating to Oracle Analytics Cloud means moving an analytics workload from a customer managed OBIEE or Oracle Analytics Server platform to Oracle's managed cloud service. Technically it is a re platforming exercise; commercially it is a decision about how the new consumption is licensed and what happens to the perpetual entitlements left behind. The commercial question is the one that determines whether the migration saves money or quietly forfeits it.
The foundations are shared with the rest of the Oracle BI and analytics portfolio, but the migration adds a layer: the interaction between the perpetual estate and the cloud subscription. A buyer who understands that interaction can preserve the value of years of maintained licences; one who does not can pay twice, once for the perpetual estate and again for the cloud.
The two licensing paths: subscription and BYOL
There are two ways to license Oracle Analytics Cloud after a migration. The first is a fresh subscription, where the customer buys cloud capacity outright, priced by the cloud unit and funded through universal credits or an annual commitment. The second is Bring Your Own Licence, where existing OBIEE or Oracle Analytics Server entitlements are converted into cloud capacity at a defined ratio, reducing the subscription rate.
The migration decision is not whether to move to the cloud. It is whether the move preserves or discards the perpetual value you have already paid to maintain.
The choice between the two paths is the central commercial question of the migration. BYOL preserves the value of a maintained perpetual estate; a fresh subscription discards it unless the perpetual licences are repurposed or terminated for credit. The right answer depends on the value of the estate, the support status, and the workload profile, and it must be modelled rather than defaulted.
How Bring Your Own Licence works for OAC
Bring Your Own Licence for Oracle Analytics Cloud converts active perpetual entitlements into cloud capacity at a published conversion ratio between the perpetual metric, Processor or Named User Plus, and the cloud subscription unit. The customer continues to pay support on the perpetual licences and pays a reduced cloud rate, the BYOL rate, rather than the full subscription rate. The mechanics mirror the broader Bring Your Own Licence model used across Oracle's cloud portfolio.
The conversion ratio is the variable that determines the economics, and it deserves scrutiny because it sets how much cloud capacity each perpetual licence buys. A favourable ratio makes BYOL clearly cheaper than a fresh subscription; an unfavourable one narrows the gap. Modelling the ratio against the actual cloud capacity required is the only way to know whether BYOL is the better path for a given estate.
Should you migrate OBIEE to Oracle Analytics Cloud?
Whether to migrate from OBIEE to Oracle Analytics Cloud is a question with no universal answer, because the economics depend on the workload. A stable, predictable analytics workload running on a fully paid up perpetual OBIEE or OAS estate can be cheaper to keep on premise, where the marginal cost is only support. A growing, seasonal or unpredictable workload can favour the consumption based cloud model, where capacity flexes with demand.
| Workload profile | Likely better option | Reason |
|---|---|---|
| Stable, fully paid up perpetual | Stay on OAS | Marginal cost is support only |
| Growing or seasonal | Migrate with BYOL | Capacity flexes; perpetual value preserved |
| New deployment, no perpetual estate | Fresh OAC subscription | No entitlements to convert |
The decision should be modelled against a multi year horizon, because a migration that looks cheaper in year one can be more expensive across the contract term. The same scrutiny that governs any BYOL decision applies here, and the worst outcome, a hasty migration that strands perpetual value, is entirely avoidable.
OCPU and user pricing on Analytics Cloud
Oracle Analytics Cloud is priced by the cloud subscription unit, which is OCPU based or user based depending on the edition. The OCPU model meters compute capacity and suits workloads where consumption varies; the user model counts named users and suits stable communities. The edition tier determines which capabilities are available and at what rate, and the subscription can be funded through universal credits.
The pricing basis interacts with the migration path. Under BYOL, the conversion ratio translates perpetual entitlements into the relevant cloud unit, so the choice of edition and unit affects how far the existing estate stretches. Modelling the cloud unit, the edition and the conversion ratio together is the only way to size the subscription accurately.
Avoiding stranded perpetual value
The most expensive migration error is stranding perpetual value. An organisation that migrates to a fresh Oracle Analytics Cloud subscription while continuing to pay support on an unused perpetual OBIEE or OAS estate is paying twice for the same capability. The perpetual value is not recovered unless the licences are converted through BYOL, repurposed elsewhere, or terminated as part of a structured renewal.
Preserving the value requires planning the migration as a commercial event, not just a technical one. Either the perpetual estate funds the cloud through BYOL, or it is wound down deliberately so that support payments stop on capability that is no longer used. Leaving a maintained perpetual estate idle while paying for the cloud is the silent cost that migrations incur when the licensing is an afterthought.
Why active support governs the migration
Active support is the precondition for almost every favourable migration path. It is what entitles the customer to Oracle Analytics Server as the OBIEE successor, and it is what makes the perpetual estate eligible for BYOL conversion to the cloud. A lapsed support stream forecloses both, leaving a fresh subscription as the only path and the perpetual value as a sunk cost.
This is why the support decision is strategic rather than a discretionary line item. Dropping support to save money in the year before a migration can cost far more than it saves by removing the BYOL option and stranding the perpetual estate. The support stream is the asset that keeps the cheapest migration paths open.
Negotiating the migration on buyer terms
A migration is a negotiation, and the buyer who models the alternatives, stay on OAS, migrate with BYOL, or buy a fresh subscription, before engaging Oracle controls the conversation. Performing this independent modelling first establishes the buyer's walkaway position and prevents a sales motion from defaulting the customer into a fresh subscription that discards perpetual value. The same discipline our practice brings to every cloud transition applies to analytics.
An Analytics Cloud migration checklist
A buyer can approach an Analytics Cloud migration with a structured checklist. First, value the perpetual estate: the maintained OBIEE and OAS entitlements and their support cost. Second, confirm support status, because it governs the BYOL option. Third, model all three paths, stay, BYOL, and fresh subscription, against a multi year horizon. Fourth, scrutinise the conversion ratio and the cloud unit pricing. Fifth, plan the wind down of any perpetual estate not carried forward, so support payments stop on unused capability. Completed together, these steps prevent the silent costs that undermine analytics migrations.
Oracle Analytics Cloud migration: a summary
The practical core of Oracle Analytics Cloud migration licensing is the choice between Bring Your Own Licence and a fresh subscription. BYOL preserves the value of a maintained perpetual estate by converting it into cloud capacity at a defined ratio; a fresh subscription discards that value unless the perpetual licences are repurposed or terminated. The choice must be modelled against a multi year horizon, because year one economics can mislead.
The decisions with the largest cost consequence are the migration path, the conversion ratio, and the support status that governs both. A buyer who values the perpetual estate, confirms support, models all three paths, and plans the wind down of unused capability will migrate without stranding value, rather than paying twice for the same analytics.
The buyer side view
Analytics Cloud migration rewards buyers who treat it as a commercial event first. The cloud is not the decision; preserving the perpetual value you have maintained is. The priority is protecting the support stream, valuing the estate, and modelling BYOL against a fresh subscription before Oracle frames the move. Begin with the Oracle Analytics Cloud licensing guide for the subscription mechanics, then model your own migration paths against a multi year horizon.
Yes. Active OBIEE or Oracle Analytics Server licences can be brought to Oracle Analytics Cloud under Bring Your Own Licence, subject to a conversion ratio between the perpetual metric and the cloud unit. Support must be active for the option to apply. It depends on the value of the perpetual estate and the workload. BYOL preserves the value of maintained perpetual licences and is usually cheaper for a stable workload, while a fresh subscription can suit a new or rapidly growing deployment. Model both before committing. Oracle Analytics Cloud is priced by the cloud subscription unit, per OCPU or per user depending on the edition, and can be funded through universal credits. BYOL reduces the rate by applying existing entitlements. If you migrate without using BYOL, the perpetual OBIEE or OAS value is effectively stranded. Preserving it requires an active support stream and a BYOL conversion, which is why the support decision is strategic.Oracle Analytics Cloud migration: frequently asked questions
Can I bring my OBIEE licences to Oracle Analytics Cloud?
Is BYOL or a fresh subscription cheaper for OAC?
How is Oracle Analytics Cloud priced?
What happens to perpetual value when migrating to OAC?
Related analysis in this cluster: Oracle Analytics Cloud licensing, Oracle OBIEE licensing.