Oracle Support Rewards can offset your support bill in exchange for OCI consumption, and it can shape where workloads live around an exit. It is a real incentive worth modelling. It is not a reason to certify early or to renew, and treating it as one hands the vendor a lever.
Oracle Support Rewards lets a customer earn credits against its Oracle technology support invoice based on how much it spends on Oracle Cloud Infrastructure. In plain terms, OCI consumption buys down part of the support bill that keeps running after a ULA ends. That is genuinely useful, because support is the cost that continues at the ULA level regardless of what you certify, and anything that reduces it has lasting value. The fit in an exit is real but narrow. Support Rewards is an incentive that affects where workloads should live and how the ongoing support cost behaves. It is a separate question from whether your certified count is complete and defensible, and the two should be kept apart so the incentive informs the exit rather than steering it.
Certify on the strength of your evidence, not on a rebate. Support Rewards is a reason to think carefully about where workloads run after the exit. It is never a reason to certify early, to renew, or to inflate OCI spend you would not otherwise commit to.
The mechanic is straightforward in shape, even though the numbers are specific to each customer. You consume OCI, you accrue rewards, and those rewards offset part of your Oracle technology support invoice. The earn rate, the eligibility rules, and any uplift tied to particular agreements depend on the program terms in force and on what you have signed, so the value that matters is your value, calculated against your own support spend and your own realistic OCI consumption, not a headline rate. Because support continues after certification, a reward that reduces it compounds over the years you keep paying. That is what makes it worth modelling properly rather than dismissing or overstating.
An exit is a negotiation, and a vendor naturally brings incentives to the table that make staying in the Oracle estate attractive. Support Rewards is one of them. Offered alongside a renewal conversation or a migration proposal, it can make certifying and moving workloads to OCI look like the obviously cheaper path. Sometimes it is. The trap is letting the reward reframe the core decision. The question at exit is whether to certify or renew, and that turns on your deployment, your evidence, your growth, and your contract, not on a support discount. If the reward quietly becomes the reason you renew, or the reason you certify before your count is ready, the incentive has done the vendor's work. Keep the certify or renew decision clean, settle it on its own merits, then let Support Rewards influence the cheaper of the choices you have already validated.
There is one place the reward and the certification touch each other usefully, and it is workload placement. Many ULAs count OCI deployment more readily than third party public cloud, and some treat OCI as on premises for counting purposes. Where that is true, moving eligible workloads to OCI before exit can do two things at once: let those deployments count toward the certified baseline, and start accruing Support Rewards against future support. That is a real alignment of interests, but it only holds if the contract supports the counting and the migration is something you would do on its own merits. The counting treatment is governed by the cloud and counting language in your specific agreement, so confirm it before you move anything, because a migration done for a reward that does not count is cost without benefit.
A services group approaching certification was weighing whether to repatriate a set of public cloud workloads on premises so they would count, or move them to OCI instead. Its contract treated OCI deployment as countable on the same footing as on premises, and the group had a continuing support bill that Support Rewards could partly offset. Modelled side by side, OCI placement let the workloads count toward the certified baseline and reduced ongoing support, while repatriation only achieved the first. The group moved the eligible workloads to OCI, captured the count, and took the support offset as a secondary benefit. The figures are indicative, and the counting treatment depended entirely on that contract's cloud language.
The discipline is to keep the decisions in the right order and let the reward sit where it belongs.
Support Rewards is worth modelling, but only after the certify or renew decision is made on its own terms. Start with the ULA exit strategy pillar guide, then read decommissioning Oracle before certification and sequencing migrations around certification for the placement and timing mechanics in detail.
Oracle Support Rewards is a program that lets customers earn credits against their Oracle technology support bill based on how much they spend on Oracle Cloud Infrastructure. The more OCI you consume, the more of your support invoice the rewards can offset. The exact earn rate and eligibility depend on the program terms in force and on your agreements, so the value is specific to your situation rather than a fixed number.
It can inform the decision, but it should not drive it. Support Rewards offsets future support cost in exchange for OCI consumption, which is a separate question from whether your certified count is complete and defensible. Certify on the strength of your evidence and your deployment, then weigh Support Rewards as one input into where workloads live afterward. Treating the reward as a reason to certify early or to renew is how an incentive becomes a lever the vendor pulls.
Often yes, but it depends on the contract. Many ULAs count OCI deployment more readily than third party public cloud, and some treat OCI as on premises for counting purposes, so moving eligible workloads to OCI before exit can let them count toward the certified baseline. Whether that holds, and on what terms, is governed by the cloud and counting language in your specific agreement, so confirm it before you migrate.
Book a confidential assessment and we will settle your certify or renew decision on its merits, then model Support Rewards and OCI placement on your own numbers and your own contract.