A move from SPLA to the Cloud Solution Provider program, the CSP, looks on paper like an upgrade. In practice the transition itself is where the exposure concentrates. The moment you are changing how every workload is licensed is the moment workloads can fall between two programs, periods can overlap or gap, and the old SPLA record can be left undefended. The migration is worth doing. The transition is worth managing as the risk event it is.
The risk is in the seam, not the destination
Neither SPLA nor CSP is unusually risky once you are settled inside it. The danger lives in the seam between them, during the weeks or months when some workloads have moved and others have not. A workload that has been pulled out of SPLA reporting but is not yet correctly provisioned in CSP is, for that interval, running on software that is no longer being licensed under either program. Multiply that across an estate moving piece by piece and the cutover becomes the single most exposed period in the whole journey.
The four risks that recur
- Coverage gaps, where a workload leaves SPLA before it is live in CSP and runs unlicensed in the interval
- Double running, where a workload is reported under SPLA and provisioned under CSP at once, wasting margin
- An undefended SPLA tail, where the final reported months are never reconciled and remain open across the 36 month lookback
- Lost evidence, where the people and records that supported the old SPLA position move on before the lookback closes
Coverage gaps are the most expensive
Of the four, a coverage gap is the one that turns into a finding. SPLA compliance is verified for every monthly cycle, so a month where a workload was consumed but reported under neither program is exactly the kind of gap an audit is built to surface. It is priced as back fees at the price file rate plus a negotiable uplift of 25 to 125 percent. The defense is sequencing: never remove a workload from SPLA reporting until its CSP provisioning is confirmed live, so there is always one program covering it. A short overlap that wastes a little margin is far cheaper than a gap that becomes a penalty.
A worked view of the seam
The figures below are indicative and chosen only to show how sequencing changes exposure, not to quote any real outcome.
| Approach | During cutover | Exposure |
|---|---|---|
| Remove from SPLA, then provision CSP | workload uncovered for an interval | gap, priced as a finding |
| Provision CSP, then remove from SPLA | brief overlap | small margin cost, no gap |
| No final SPLA reconciliation | tail left open | lookback exposed for years |
| Sequenced with reconciliation | continuous coverage | minimized |
Indicative illustration of how sequencing changes exposure, not a quoted outcome.
Defending the SPLA tail while you move
Because SPLA is verified across a 36 month lookback, the program you are leaving stays auditable long after the move. The transition is the right time to close it properly, while the people and data are still in place. That means a final reconciliation of your last reported months, retention of the authentication counts, customer mappings, and version mappings that support them, and a clear record of the cutover date for each workload. Done during the move, this is straightforward. Attempted years later in response to an audit letter, it is a reconstruction.
Manage the transition as a controlled event
The way to defuse these risks is to run the transition as a deliberate, sequenced program rather than a rolling improvisation. Map every workload, decide its destination, provision before you decommission, keep continuous coverage, and close the SPLA tail with evidence retained. None of this is difficult in isolation. The exposure comes from doing it ad hoc, workload by workload, with no one holding the whole picture.
For the structure of the move itself and how the two programs differ, read migrating from SPLA to CSP hoster. For how an unreconciled tail becomes a demand, see back fees versus penalty uplift in SPLA.
The next step
The transition window is short, but it is where a SPLA to CSP move is won or lost. If you are planning or midway through a migration and want the cutover sequenced so no workload is ever uncovered and the SPLA tail is defended, a strategy call will map the order of operations and the evidence to keep. Our guarantee stands behind the work: we reduce your exposure or we reimburse our service fee.
Win the move in the seam.
Book a strategy call to sequence the cutover so no workload is ever uncovered and your SPLA tail is reconciled and defended across the lookback.
Book a Strategy CallWhen the exposure is real, our SPLA to CSP migration service moves you across without opening new exposure.