Most large Oracle estates have grown by accretion. Licences and their support contracts were acquired in separate transactions over many years, each generating its own support agreement and its own renewal date, identified by its own Customer Support Identifier. The result is an estate fragmented into many small support contracts renewing throughout the year, none individually large enough to command attention, and a total support spend that never appears as a single negotiable figure. This fragmentation is not neutral; it systematically favours Oracle, and reversing it through co terming is one of the clearest structural moves available to a buyer, woven through the negotiation method in the support renewal pillar.
Co terming is the deliberate alignment of these scattered contracts to a common renewal date, consolidating many small negotiations into one large one. It changes nothing about the licences or the support service; it changes only the structure and timing of the renewals, and that structural change shifts leverage materially toward the buyer. This article explains how the fragmentation arises, why consolidation helps, and how to execute a co terming without falling into the repricing trap that can accompany any change to support arrangements.
What is Oracle support co terming?
Co terming is the practice of aligning the renewal dates of multiple Oracle support contracts so that they fall on a single common date and can be renewed together as one transaction. Where contracts currently renew in, say, March, June, September, and November, co terming brings them to a single date, typically through a short or extended initial period on some contracts to synchronise them. After co terming, the organisation faces one annual renewal covering the consolidated support base rather than a series of separate renewals throughout the year.
The mechanism is administrative but the effect is strategic. A single consolidated renewal presents Oracle with one large negotiation it cannot quietly process, exposes the total support spend as a single figure, and creates a natural point at which the support discussion can be combined with other transactions. The fragmentation that previously worked in Oracle favour is replaced by a concentration that works in the buyer favour, without any change to what is actually being supported.
CSI numbers and how the estate fragments
Each Oracle support contract is identified by a Customer Support Identifier, the CSI number, which ties a body of licences to a support agreement and a renewal date. An organisation that has purchased Oracle software in many transactions accumulates many CSI numbers, each with its own renewal cycle. Over time the estate becomes a patchwork of CSIs, often poorly documented, sometimes with overlapping or forgotten contracts, and almost always renewing on a scatter of dates that no one has consciously chosen.
This fragmentation has costs beyond the loss of negotiating leverage. It obscures the total support spend, makes it hard to identify duplicate or unused support, and complicates any attempt to reduce the bill, because the buyer cannot see the whole picture. The first step in co terming is therefore a CSI inventory: identifying every support contract, its licences, its renewal date, and its fee, so that the full support estate is visible. That inventory frequently surfaces immediate savings, duplicate support, licences supported but not used, that exist independently of the co terming itself, and it feeds directly into the cost reduction analysis.
A dozen small renewals are a dozen battles Oracle wins by default. One large renewal is a single negotiation the buyer can actually fight.
Why co terming increases leverage
Co terming increases leverage in three ways. First, it concentrates the spend: a single renewal covering the whole support base is large enough to command senior Oracle attention and to justify concessions that a small renewal never would, because Oracle allocates its negotiating flexibility to deals that matter. Second, it removes divide and rule: Oracle can no longer handle each contract in isolation, processing the small ones quietly while the buyer never sees the total, because there is now one total to see and to negotiate. Third, it creates a single, predictable point in the year at which the support discussion can be aligned with new purchases and with Oracle quarter end, enabling the bundling and timing levers described in the renewal negotiation guide.
The concentration also makes other levers more effective. An uplift cap negotiated on a consolidated base protects far more spend than one negotiated on a single small contract, and a credible alternative threatens a larger, more meaningful revenue loss. Co terming is therefore not merely a lever in itself but a multiplier on the other levers, which is why it is treated as a structural priority rather than a tactic. Its effect on the uplift alone, by bringing the whole base under a single negotiated cap, can justify the effort.
How do I co term Oracle support contracts?
Co terming proceeds in a defined sequence. Begin with a complete CSI inventory: list every support contract, its CSI number, its licences, its renewal date, and its annual fee, and identify any duplicate, overlapping, or unused support to be eliminated first. Choose a target common renewal date, ideally aligned to Oracle quarter or year end to enable timing leverage. Then work with Oracle to align the contracts to that date, typically by extending or shortening the initial period of some contracts so all subsequent renewals coincide.
The alignment itself is a negotiation, and it should be conducted as one rather than accepted as an administrative reformatting. Use the consolidation as the occasion to negotiate an uplift cap across the whole base, to protect against repricing, and to align the renewal with any planned new purchase. The objective is not merely a tidy single date but a single date that carries improved terms, achieved by treating the co terming as part of the broader renewal strategy set out in the renewal licensing white paper and supported by the firm advisory engagements.
The trade offs and the repricing caution
Co terming carries one principal caution: any change to support arrangements can interact with the matching service levels policy, and a poorly handled consolidation could trigger repricing if it is treated by Oracle as a reduction or restructuring of a supported set. The CSI inventory should therefore distinguish carefully between consolidating renewal dates, which is benign, and altering the licences under support, which can trigger repricing. Co terming should align dates without reducing the supported base, unless a deliberate, separately analysed termination of a cleanly separable set is also intended.
The other trade off is the short term cash effect of synchronising dates, since extending some contracts to align them means paying for the extension. This is a timing cost, not a real one, and it is repaid by the leverage the consolidation creates. Buyers should model the synchronisation cost and weigh it against the negotiating value, which for any sizeable estate is overwhelmingly positive. The repricing caution is the more important of the two, and it is why co terming should be planned with the same care as a cost reduction exercise rather than executed as routine administration.
Co terming alongside the other levers
Co terming is most powerful when combined with the other renewal levers, because it amplifies each of them. With a consolidated renewal aligned to quarter end, the buyer can bring a credible alternative, an uplift cap case, and a bundled new purchase to bear on the whole support base at once, rather than fighting the same battles repeatedly on small contracts throughout the year. The consolidation turns a year of minor, losing skirmishes into a single, winnable negotiation conducted from strength.
This is why co terming is best undertaken not in isolation but as the structural foundation of a renewal strategy. The buyer co terms in order to create the single large negotiation, then deploys the uplift cap, the credible alternative, and the timing levers within it. The sequence and the way the levers compound are set out in the renewal negotiation guide and the cost reduction guide, with co terming as the move that makes the others worth the effort.
The buyer side view
The buyer side view of Oracle support co terming is that estate fragmentation systematically favours Oracle, and consolidating renewals is a purely structural lever that costs little and shifts leverage materially to the buyer. A scatter of small renewals is a series of battles Oracle wins by default; a single consolidated renewal is one negotiation the buyer can actually fight, large enough to command attention and to carry the other levers. The fragmentation is rarely chosen; it accretes, and reversing it is among the highest leverage structural moves available.
The disciplined response is to inventory every CSI, eliminate duplicate and unused support first, choose a common renewal date aligned to Oracle quarter end, consolidate the contracts to that date without inadvertently triggering repricing, and use the resulting single negotiation to deploy the uplift cap, the credible alternative, and the bundling and timing levers together. Read the negotiation guide and the uplift guide for the levers co terming amplifies, weigh the engagement economics through the firm engagement model, and treat the fragmented estate as a structural weakness to be corrected before the next renewal rather than a fact to be lived with.
Aligning multiple support contracts and CSI numbers to one common renewal date, consolidating many small renewals into one large negotiation, as the renewal pillar describes. It concentrates spend into one visible renewal, removes divide and rule, and amplifies the uplift cap and alternative levers across the whole base. Inventory every CSI, eliminate duplicate support, choose a quarter end date, and align contracts to it as a negotiation, per the negotiation guide. It can if the supported base is altered; align dates without reducing the base, as the cost reduction guide cautions.Oracle support co terming: frequently asked questions
What is Oracle support co terming?
How does it increase leverage?
How do I co term contracts?
Does it risk repricing?