Compliance Continuity During a SPLA Exit

Leaving SPLA, whether for a Cloud Solution Provider model or for customer owned licences, does not close the door on your SPLA past. The 36 month lookback still reaches back into the months you reported. The risk during an exit is a gap: a period where reporting stops before the new model is clean. Continuity is the defense.

Why an exit is an audit moment

SPLA is pay as you consume, verified for every monthly cycle across a rolling 36 month lookback. When you stop reporting under SPLA, those past months remain in scope for years. A change in licensing model is also exactly the kind of event that draws attention, because transitions are where reporting discipline tends to slip. The exit itself is fine. The danger is treating the switch as a clean break and letting the old record go stale while the new one is still forming.

The continuity gaps that create risk

During a migration, exposure tends to appear in the seams between the old model and the new one.

• A final SPLA month reported late or estimated because attention moved to the new model
• Workloads that ran on both models during cutover, double counted or not counted at all
• Authentication evidence and customer mapping for the closing months left incomplete
• Historical SPLA records archived in a way that makes them hard to produce later
• Assumption that the new provider or model absorbs the old compliance obligation, which it does not

How to keep continuity through the exit

1. Report the last SPLA months as carefully as the firstDo not let the closing cycles slip. They are the freshest, most testable months in the lookback.
2. Map the cutover preciselyFor any workload that moved, record the exact month it left SPLA and entered the new model, so nothing is counted twice or dropped.
3. Preserve the full recordKeep your monthly SAL reports, sealed authentication counts, customer mapping, and version mapping in a form you can produce on request for the full 36 month window.
4. Close the SPLA agreement cleanlyConfirm the final reporting obligations are met and documented, so there is no ambiguous tail.
5. Assign ownership of the legacy recordGive someone clear responsibility for the historical SPLA evidence even after the program ends.

A worked view of the continuity window

The view is indicative and shows where attention belongs, not a quote.

Phase	Continuity risk	The defense
Final SPLA months	Late or estimated reporting	Report on time with full evidence
Cutover period	Double counting or gaps	Month by month migration map
Post exit	Records go stale	Preserved, producible legacy record

The next step

An exit done with continuity in mind leaves nothing for a future auditor to reconstruct against you. If you are planning to leave SPLA, build the migration around an intact record rather than a clean break. Our SPLA audit defense guide sets out the reporting standard that protects the lookback, and the related articles below cover reporting discipline and the settlement. Download the guide and plan the exit before you make the switch.

Related reading

If the timeline is already running, our SPLA to CSP migration service moves you across without opening new exposure.