Third party support. The 2026 decision framework.

Third party support is the discipline of replacing publisher support fees on selected products with an independent provider. The decision applies across Oracle, IBM, SAP, and a growing list of enterprise publishers. Five questions answer the decision. Cost, scope, risk, leverage, and exit. The scoring framework returns a stay, switch, or split recommendation.

Read this alongside the Oracle 3PS evaluation, the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the license optimization playbook.

Cross vendor scope

The 3PS market started with Oracle, but mature providers now cover IBM, SAP, and adjacent publishers. The decision framework needs to handle that range.

Where 3PS applies

• Oracle. Database, EBS, Middleware, applications. Mature market with multiple providers.
• IBM. Mainframe, AIX, WebSphere, Db2. Selective coverage, fewer providers.
• SAP. ECC and selected modules. Limited but growing.
• Adjacent publishers. Selected enterprise products at the publisher level.

The five decision questions

Answer five questions per product line. The combined answer drives the recommendation.

Question one. Cost

• Current publisher fee. Annual fee plus the locked in uplift schedule.
• 3PS quote. Two or three provider quotes on equivalent scope.
• Switching cost. Knowledge transfer, run book replication, overlap fees.

Question two. Scope

• Release strategy. Is the product on a terminal release.
• Regulatory updates. Tax, customs, payroll, statutory content needs.
• Patch source. Security patch flow and where those patches come from.

Question three. Risk

• Audit posture. The publisher audit clause sits in the master agreement.
• Cloud entanglement. Cloud discount conditions tied to on premises support.
• M and A noise. Future acquisitions that may extend the estate beyond 3PS scope.

Question four. Leverage

• Discount unlock. The publisher moves to deeper discount when a credible 3PS option exists.
• Term flex. A 3PS option shortens the publisher term lock.
• Module drop. Buyers use 3PS leverage to drop low value modules.

Question five. Exit

• Reinstatement path. Cost and timeline of returning to publisher support.
• Future release access. Path to renewed publisher support for new releases.
• Audit closeout. Documented compliance baseline before switching.

Scoring matrix

Apply the five questions to a four axis scoring matrix. The matrix returns the stay, switch, or split recommendation.

Scoring framework

Axis	Stay	Switch	Split
Cost	Publisher baseline plus uplift	40 to 55 percent saving	20 to 35 percent saving
Scope	Full content access	Terminal release only	Mixed by product line
Risk	Lowest contractual risk	Reinstatement and audit exposure	Manageable per line
Leverage	None	Loss of publisher discount	Active leverage at renewal

By publisher

The framework returns different answers for different publishers. The mechanics differ.

Three publisher patterns

1. Oracle. Mature 3PS market. Multiple providers. Split estate is common. See the Oracle 3PS evaluation for the deep dive.
2. IBM. Selective 3PS coverage. Mainframe and AIX dominate. Watch for ELA entanglement.
3. SAP. Limited 3PS coverage on ECC. Watch for indirect access and RISE entanglement.

Risks and trade offs

Every 3PS evaluation carries trade offs. Name them before signing.

Six trade offs

1. Reinstatement penalty. Return paths carry back support and reinstatement fees.
2. Audit posture. The audit clause is independent of the support contract.
3. Patch source. Publisher patches are not freely redistributable.
4. Cloud discount. Cloud agreements may tie discount to on premises support.
5. Future releases. 3PS buyers cannot adopt new publisher releases without renewed support.
6. M and A noise. Future acquisitions may bring an estate outside the 3PS scope.

What to do next

The checklist takes a CIO from current state to a defensible 3PS decision in 90 days.

1. Inventory the publisher estate. Product, metric, quantity, deployment, terminal release status.
2. Pull every publisher contract. Master agreement, ordering documents, support contracts.
3. Brief three 3PS providers. Equivalent scope, equivalent SLA, equivalent geographies.
4. Score the five questions. Per product line, not per estate.
5. Pick the path. Stay, switch, or split per product line.
6. Open the publisher conversation. Renewal terms, discount uplift, term flex.
7. Lock the decision. Sign with leverage preserved.

Read the Oracle 3PS evaluation, the Vendor Shield subscription, the Vendor Shield pillar, the Renewal Program, and the Renewal Program pillar.

Continue with the Benchmark Program, the Benchmark Program pillar, the license optimization playbook, the licensing advisor comparison, the software spend health check, the case studies, the management team, and the contact page.

Frequently asked questions