Certification gives you perpetual licenses for a fixed quantity, and that quantity can be deployed wherever you choose within the licensed entity and territory. You can retire one server and stand the same entitlement up on another, as long as total deployment stays inside the certified number.
One of the quieter benefits of a clean certification is flexibility. The perpetual licenses you certify are not pinned to the servers they happened to run on at exit; they are a quantity of entitlement you can deploy across the estate as the business changes, within the bounds the licenses carry. That flexibility is valuable, because estates are never static. Hardware is refreshed, workloads consolidate, projects move between data centres, and a certified quantity that can follow those changes is worth far more than one trapped on its original footprint. This article explains how reallocation works after a ULA, what the entitlement actually permits, the constraints that apply, and how to treat the gap between your certified quantity and your live deployment as managed headroom rather than waste. As ever, the limits turn on the licensing terms and the entity and territory definitions in your own agreement, so confirm the specifics before relying on them.
Yes. Certification produces perpetual licenses for a fixed quantity of each product, and that quantity can be deployed wherever you choose within the licensed entity and territory, on the product's ordinary licensing terms. You can decommission a server and bring the same entitlement up elsewhere, refresh hardware under the existing licenses, or shift a workload between sites, provided your total deployment of the product stays within the certified quantity. The entitlement is a number you manage, not a fixed assignment to particular machines, and that is what makes reallocation possible. The wider cost picture this sits within is in support costs after ULA certification.
The governing limit is the certified number. As long as concurrent deployment of a product stays at or below the quantity you certified, you are free to arrange that deployment as you see fit. Reallocation is simply the act of changing where the entitlement is consumed without changing how much is consumed in total, and the ceiling is the certified figure that the certification fixed.
Reallocation operates inside the scope the agreement defined. The licensed entity and the territory clauses that applied during the ULA continue to apply to the perpetual licenses, so entitlement can be moved among the parts of the business and the geographies that were in scope, but not freely beyond them. Moving deployment into an entity or territory that was outside scope raises the same questions it would have raised at certification, and those scope mechanics are discussed in the context of corporate change in our exit material.
No. Moving certified licenses around the estate does not change the support fee, because support is anchored to the support base, not to where the licenses run. Reallocation is a question of using your certified quantity efficiently, and it is independent of cost reduction, which is governed by a different rule entirely. If your aim is to lower support rather than to redeploy entitlement, the binding constraint is the matching service levels rule, set out in the matching service levels rule, and reallocation will not move that lever. Keeping the two ideas separate avoids the common error of expecting redeployment to cut the bill.
The right way to frame reallocation is as estate management. It lets you serve new needs from licenses you already hold, avoid buying entitlement you already own, and keep deployment matched to where the business actually runs. None of that touches the support fee, which continues on the certified set regardless. Treating reallocation as a use optimisation, with support handled on its own track, keeps both decisions clear.
A well run certification often produces a certified quantity above current deployment, and that gap is headroom: licensed capacity you can grow into without a new purchase. Headroom is an asset, but only if you know it exists and track it. An organisation that has certified 540 processors and deploys 470 holds 70 processors of capacity it has already paid for. New projects, migrations, and growth can draw on that capacity until the certified ceiling is reached, at which point further growth needs deliberate buying rather than quiet expansion. The discipline that builds healthy headroom in the first place is the maximization work done before exit, which is why a thorough certification pays back long after the term ends.
An indicative insurer certifies 540 processors of a database product and exits with 470 deployed, leaving 70 processors of headroom. Over the following two years it refreshes a data centre, which moves entitlement onto newer, denser hardware without buying anything, and absorbs a new analytics platform that consumes 50 processors, drawing the live total to 520, still within the certified 540. A further project would push deployment to 560, above the ceiling, so that increment is licensed deliberately as a new purchase rather than discovered later in a review. Throughout, the support fee is unchanged, because it follows the support base. The figures are indicative; your ceiling, scope, and terms come from your own certification and agreement.
Reallocation only works safely if you know your live position. The single most valuable practice after certification is to track deployment of each certified product against its certified quantity continuously, so you always know how much headroom remains and when you are approaching the ceiling. That tracking turns reallocation from a guess into a managed activity, and it is the same discipline that keeps you safe in a review, because the number that proves you are within entitlement is the number you have been watching all along. The reason that review is likely, and why the tracking matters for defense as well as efficiency, is set out in why audit risk rises after certification.
As entitlement moves, the record of where it is deployed should move with it. An evidence file that reflected the estate at exit becomes less useful as the estate changes, so updating it as reallocation happens keeps it ready to demonstrate compliance at any moment. A current record is both an operational tool and a defense asset.
The important moment is when growth would push deployment above the certified quantity. That is the point at which new licenses are genuinely needed, and buying them deliberately, at negotiated terms, is far better than reaching the ceiling unawares and discovering the gap in a review. Reallocation buys time and flexibility up to the ceiling; beyond it, the answer is a planned purchase, not a return to an unlimited arrangement.
Certified licenses are a quantity you can deploy across the estate within the licensed entity and territory, so reallocation lets you use what you own efficiently, while support and cost stay on their own track. Read it with support costs after ULA certification for the cost picture and the matching service levels rule for the constraint that actually governs support reductions. Because your entity, territory, and licensing terms set the limits of reallocation, confirm what your certified entitlement permits against your own agreement before relying on it.
Yes. Certification produces perpetual licenses for a fixed quantity of a product, and that quantity can be deployed wherever you choose within the licensed entity and territory, on the product's normal terms. You can retire one server and stand the same entitlement up on another, provided total deployment stays within the certified quantity.
No. Moving certified licenses around the estate does not change the support fee, which is anchored to the support base, not to where the licenses run. Reallocation is about using the certified quantity efficiently, not about cost reduction, which is governed separately by the matching service levels rule.
We map your certified quantities against live deployment, quantify your headroom, and set up tracking so you reallocate within entitlement and buy deliberately only when you reach the ceiling.