Flex-Down Licensing: Aligning SAP Sybase Costs With Migration Progress

Published 2 August 2026 · Updated 12 October 2026

Tables illustrate planning principles and example responsibilities. Actual scope and commercial terms depend on the agreed contract.

Every decommissioned database should feel like progress. On too many invoices, it doesn't.

Enterprise migrations reduce the active SAP Sybase estate in stages: a reporting instance this quarter, a batch platform the next, a core system once its replacement has proven itself. Whether support charges fall at the same pace depends on the agreement and the options available. Retirement alone does not establish a fee reduction.

The gap between usage and spend

This mismatch is easy to overlook early on, when the estate is still mostly intact. It becomes harder to defend as the programme progresses. By the later stages of a migration, an organisation may be paying to support capacity it decommissioned months or even years ago, while also funding the new platform at full cost. Finance teams notice, and the business case for modernisation starts to look weaker than it should.

What flex-down means, and what it doesn't

A flex-down arrangement allows defined licence or service charges to reduce as eligible capacity is verifiably retired. Done well, it turns the support contract into something that moves with the migration rather than against it.

It is important to be precise about what flex-down is not:

• A provider’s core-based flex-down mechanism must be defined in its agreement. Do not assume it is included in every SAP or provider contract, or that other reduction options are unavailable.
• It is not a discount on systems that remain active. Capacity still in use still requires appropriate support and licensing.
• It is not automatic. Reductions depend on evidence, notice and the conditions written into the agreement.

SAP’s July 2026 announcement describes more flexibility around commercial installations, unused-licence termination in specified circumstances and single-metric contracts. These options should be assessed alongside a provider’s proposed flex-down terms. They do not establish an automatic reduction for every retired ASE core. SAP’s July 2026 policy announcement

How it works in practice

The illustration below shows the principle. It is not a pricing commitment.

Establish a trustworthy baseline

Everything depends on the starting point. Begin with a verified view of cores, environments, entitlements and application ownership, agreed by both parties. The contract should state which measures determine fees, whether that is cores, instances, environments or service tiers, and how changes will be evidenced.

Set unambiguous reduction triggers

Ambiguity is where flex-down arrangements fail. A useful agreement specifies:

• What triggers a reduction: verified decommissioning, a reduction in core count or an agreed milestone.
• What evidence is required, and who provides it.
• Notice periods and the review points at which reductions take effect.
• Minimum commitments or floors, if any.
• How temporary capacity, such as parallel running or disaster recovery tests, is treated.
• Exceptions, such as systems that are retired and then reinstated.

Guardrails: protect compliance and continuity

Cost reduction must never get ahead of operational reality. A system that is still active, even at reduced use, still needs proper support, security governance and correct licensing. Finance, infrastructure and application teams should reconcile changes before commercial reductions take effect, and SySAM licence records should be updated in step.

Read: Maintaining Audit-Ready SAP Sybase Environments During Enterprise Migration

Test it against delay

A flex-down agreement should be tested against migration delays. Establish what happens when systems stay active longer than planned, whether minimums or other charges apply, and whether the customer can keep appropriate support until retirement is safe. Model the agreement against the expected, accelerated and delayed scenarios in the migration plan.

Read: Why Enterprise SAP Sybase Migrations Take Longer Than Planned

Frequently asked questions

Is flex-down available on standard SAP contracts?

Do not assume a particular core-based reduction mechanism is included. SAP has announced wider maintenance and licensing flexibility, while provider flex-down mechanisms depend on the agreed terms. Compare eligibility, retained usage rights, notice, minimums and when a reduction takes effect. SAP maintenance and commercial options

What evidence is usually needed to trigger a reduction?

The contract should specify the evidence. It may include decommissioning records, updated core or instance counts, relevant licence records and system-owner approval. The required evidence and the resulting fee change depend on the agreement.

What if a retired system has to come back?

A good agreement covers this in advance, including how reinstated or temporary capacity is charged, so a recovery event doesn't become a commercial dispute.

Assessing Insight commercial terms

Insight is the primary product from tdglobal’s Data business, offered as a subscription-based managed solution. A flex-down proposal should be assessed against its written measurement and reduction terms. Explore Insight for SAP Sybase

Pay for the estate you run

The value of flex-down is not just a lower starting price. It is a contract that tells the truth about the estate, so every database retired shows up as progress on the invoice as well as in the architecture diagram.

Discuss Insight Commercial Options →