Cloud and third party support. The dual track.

A growing number of Oracle customers operate a hybrid strategy that combines Oracle cloud migration for new workloads with third party support on legacy on premises products. The dual track creates specific commercial leverage and specific operational considerations that buyer side teams should understand.

The dual track strategy emerged in response to two structural changes in the Oracle commercial landscape. The expansion of Oracle Cloud Infrastructure and Fusion Cloud Apps created new opportunities for cloud first deployment patterns. The maturation of the third party support market, with providers such as Rimini Street and Spinnaker Support offering credible alternatives to Oracle premier support, created cost reduction opportunities on the legacy footprint. Customers that integrate the two strategies achieve material cost reduction while maintaining strategic flexibility.

This article walks through the dual track framework. The structural rationale for the hybrid approach. The workload allocation decision between Oracle cloud and third party support. The contractual considerations and the Oracle commercial response patterns. The operational implementation framework. The risk considerations and the mitigation approach. The article applies to customers with material Oracle on premises footprints considering cloud migration alongside support cost optimisation.

The structural rationale.

The dual track structural rationale reflects the different commercial characteristics of the Oracle cloud portfolio and the on premises legacy footprint. The Oracle cloud portfolio offers product innovation, new functional capability, and strategic alignment with Oracle's investment direction. The on premises legacy footprint typically operates in steady state, with limited functional change required and the support cost dominated by patches and minor enhancements rather than new capability.

The commercial logic is that the customer pays Oracle premier support on the legacy footprint primarily for stability and patches, while paying separately for the cloud subscription that delivers the new capability. The third party support market provides equivalent stability and patches at materially lower cost, releasing the customer's commercial spend for the cloud investment. The integrated economics typically demonstrate material savings against the alternative of paying Oracle premier support on both the legacy footprint and the cloud subscription.

The structural response is to evaluate each Oracle product separately for the dual track classification. Products in steady state with limited change requirements are candidates for third party support. Products with active investment requirements or that drive the cloud migration are candidates for continued Oracle premier support during the transition. See the renewal contract term article.

The workload allocation.

The workload allocation decision is the operational core of the dual track strategy. Each Oracle workload should be classified into one of three categories. The cloud migration target category includes workloads that will move to Oracle cloud or alternative cloud platforms over a defined horizon. The third party support category includes workloads that will remain on premises with support transferred from Oracle to a third party provider. The Oracle premier support category includes workloads that will remain with Oracle support, typically because of specific functional or strategic requirements.

The classification framework considers several factors for each workload. The functional stability and the change requirement over the planning horizon. The strategic importance of the workload and the alignment with Oracle's investment direction. The technical complexity of the alternative support arrangement. The operational risk tolerance for the support transition. Each factor should be evaluated explicitly, with the classification documented for each workload in the Oracle portfolio.

The structural response is the integrated workload allocation plan that addresses the full Oracle portfolio. The plan typically distributes the workloads across the three categories, with the distribution reflecting the customer's strategic position, the operational risk tolerance, and the commercial economics. The plan should be reviewed annually as the Oracle product strategy and the customer's operational requirements evolve. See the Oracle Database product page.

The Oracle commercial response.

Oracle commercial teams respond to the dual track strategy through several patterns that buyer side teams should anticipate. The principal patterns include the support reinstatement positioning, the cloud incentive offers, the audit risk positioning, and the strategic relationship arguments. Each pattern has a specific counter response that buyer side teams should prepare in advance.

The support reinstatement positioning argues that the customer's transition to third party support creates risk of future support reinstatement fees if the customer needs to return to Oracle premier support. The reinstatement fees are typically positioned as a significant cost, with the customer's flexibility constrained by the threat of the fee. The counter response is the structured analysis of the reinstatement fee scenario, with the probability and the cost assessed explicitly against the support cost saving over the planning horizon.

The cloud incentive offers position Oracle cloud commitments as alternatives to the third party support transition, with discount provisions on the cloud subscription tied to maintaining Oracle premier support on the legacy footprint. The counter response is to evaluate the integrated commercial position, separating the cloud commercial terms from the legacy support arrangement and negotiating each on independent merit. See our renewal negotiation service.

The contractual considerations.

The dual track strategy requires specific contractual provisions to protect the customer's flexibility and to address the operational reality. The principal provisions include the support termination rights, the cloud subscription independence, the data portability provisions, and the future reinstatement provisions. Each provision should be addressed explicitly in the contractual framework.

The support termination rights should permit the customer to terminate Oracle premier support on specific products without affecting the broader contractual relationship. Oracle's standard contract template typically permits this termination, but the operational implementation can be complicated by interdependencies between products and contract terms. The structural response is to document the support termination rights explicitly for each product, with the termination process and the implementation framework defined in advance.

The cloud subscription independence provisions ensure that the cloud commercial terms are not affected by the legacy support arrangement. The provisions typically include the cloud price stability, the cloud term independence, and the cloud renewal terms unaffected by the legacy support decisions. The provisions are typically negotiated as part of the broader cloud commercial conversation, with the dual track strategy informing the negotiation position. See our contract review service.

The operational implementation.

The operational implementation of the dual track strategy requires structured planning across the support transition and the cloud migration. The transition typically occurs in phases, with the third party support transition happening before or in parallel with the cloud migration on specific workloads. The phased approach permits the customer to validate the third party support quality before committing the full legacy footprint.

The third party support transition has specific operational requirements. The selection of the third party provider with the appropriate Oracle product coverage. The transition planning including the knowledge transfer from Oracle to the third party. The operational integration of the third party support process into the customer's IT service management framework. The contractual coverage including the SLA, the escalation, and the issue resolution framework.

The cloud migration has separate operational requirements that interact with the third party support strategy. The migration sequencing across workloads. The cloud platform decision between Oracle cloud and alternative providers. The data migration tooling and the application compatibility validation. The integration with the legacy footprint during the migration. Each requirement has cost implications that should be reflected in the integrated dual track economics. See our cloud migration advisory service and the OCI Universal Credits deal type page.

Risk considerations.

The dual track strategy has specific risk considerations that should be addressed in the implementation framework. The principal risks include the third party support quality risk, the future reinstatement risk, the audit exposure during the transition, and the strategic relationship risk with Oracle. Each risk has a specific mitigation approach that should be incorporated into the strategy.

The third party support quality risk reflects the dependency on a non Oracle provider for support on critical workloads. The mitigation typically includes the provider selection due diligence, the contractual SLA framework, the operational testing during the transition, and the contingency plan for support escalation. The mitigation framework should be documented and tested before the full transition is implemented.

The future reinstatement risk reflects the possibility that the customer may need to return to Oracle premier support on specific products in the future. The mitigation includes the structured analysis of the reinstatement scenario, the contractual provisions that limit the reinstatement fee exposure, and the operational planning that supports the reinstatement if required. The mitigation framework should reflect the customer's strategic position and the realistic probability of the reinstatement scenario. See the support reinstatement article and the Oracle Negotiation Playbook white paper.

Putting it together.

The dual track strategy combines Oracle cloud migration with third party support on legacy products to achieve material cost reduction while maintaining strategic flexibility. The structural rationale, the workload allocation, the Oracle commercial response, the contractual considerations, the operational implementation, and the risk considerations each require structured analysis. The integrated strategy typically achieves 30 to 50 percent total Oracle spend reduction against the alternative of full Oracle premier support and full Oracle cloud commitment.

For the broader framework see the cloud negotiation pillar and the renewal negotiation pillar.