Trade up and competitive trade up programs.
Trade up programs let you convert an older IBM license into a newer or larger one, and competitive trade up programs credit a rival product toward an IBM purchase. Both move you onto fresh entitlements, and both leave a trail an audit will follow. The savings are real, but only if the conversion is documented as cleanly as it was sold.
What each program actually does
A trade up converts an entitlement you already hold into a different one, typically a newer edition, a larger capacity, or a successor product, at a price that credits what you owned. A competitive trade up credits a non IBM product you are replacing toward the IBM equivalent. In both cases the commercial logic is the same: you give up something, and the new entitlement is priced to reflect that. The catch is that the thing you gave up has to be genuinely retired, and the new entitlement has to be recorded for what it actually grants.
The retirement obligation
A trade up is not an addition. It is a replacement. The traded entitlement is meant to be retired, and continuing to run the old product alongside the new one turns a discount into an unlicensed deployment. Competitive trade ups carry the same logic for the rival product. The most common finding here is simple: the organization kept running what it was supposed to retire, because the migration slipped or the old instances were never decommissioned. An audit finds both products live and counts the one that should be gone.
Where the new entitlement gets misread
Trade up conversions change the metric, the edition, or the capacity, and the new entitlement is not always recorded faithfully:
- The new edition carries a different metric than the old one, and the deployment is still counted on the retired metric.
- The traded up capacity is larger or smaller than assumed, and the entitlement record was never updated to match.
- The competitive product credit was conditional, and the conditions were not met, so the credited quantity does not hold.
- The conversion paperwork sits with the reseller or a regional team and never reached the records the audit will read.
Each of these leaves the new entitlement looking smaller, or differently metered, than what was actually purchased.
Document the conversion before the audit does
The defense is to treat every trade up as a two sided record: proof that the old entitlement was retired, and proof of exactly what the new one grants, by metric, edition, and quantity. Where a competitive trade up applies, the same discipline covers the rival product retired and the conditions met. Assembled in advance, this turns a migration that an audit could read as unlicensed sprawl into a clean, credited entitlement. Left undocumented, it becomes one of the easier findings for an audit to raise and one of the harder to reverse after the fact.
Trade up and competitive trade up programs are defensible only when both halves are recorded: the retired entitlement gone, and the new one captured for what it truly grants. The recurring findings are old products still running and new entitlements misread on the wrong metric or quantity. Document the conversion fully before an audit reconstructs it, and the program delivers the savings it promised instead of a finding.
Did a trade up leave the old product running?
Our Settlement Negotiation engagement reconstructs each trade up as a clean record, proves the retired entitlement, captures what the new one grants, and credits the conversion an audit would otherwise read as unlicensed use.
See Settlement Negotiation →The IBM Audit Brief
Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.
Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.