The decision to leave an Enterprise Agreement for CSP is rarely made on technical grounds alone. Usually it is driven by one of three things: headcount volatility that makes a three-year commitment feel risky, a desire for monthly billing flexibility, or Microsoft account team pressure to migrate during renewal rather than renegotiate. Sometimes it is the right call. Often it is not.
What almost no one tells you is that the migration itself carries significant compliance and cost risk — risk that exists entirely in the gap between when your EA expires and when your CSP subscriptions become fully operational. After managing over 500 Microsoft licensing engagements, including more than 80 EA-to-CSP transitions, I have seen every type of migration failure. This guide gives you the framework to avoid them.
Before You Commit: The Migration Viability Test
Migrating from EA to CSP is irreversible in the short term. Once your EA expires and you move to CSP, you lose negotiating leverage that took years to build, Software Assurance benefits stop accruing, and the perpetual licences you hold remain yours but are frozen at their current version. That is not necessarily a problem — but it needs to be a conscious choice, not a default.
Before committing to migration, every organisation should run through four viability gates:
Gate 1: Software Assurance Inventory
Software Assurance provides version upgrade rights, licence mobility for server products, deployment planning services, extended security updates, and Azure hybrid benefit access. None of these are available through CSP. Before migrating, you need an exhaustive SA benefit inventory covering:
- SQL Server and Windows Server licence mobility: If you run SQL Server or Windows Server in third-party hosted environments (non-Azure), your SA licence mobility rights allow this at no additional cost. In CSP, you lose this — and the penalty for unlicensed hosted deployment is substantial.
- Extended Security Updates (ESU): If you run Windows Server 2012/2012R2 or SQL Server 2012/2014 and have not migrated to Azure, your EA SA provides paid ESU access through Microsoft's annual programme. Once EA expires, you must purchase ESUs separately or accept the compliance exposure.
- Step-up rights: If any users have Office Professional Plus or Windows Enterprise step-up rights through SA, these stop accruing immediately when SA ends. Users remain entitled to the version current at SA expiry but get no further upgrades.
- Azure Hybrid Benefit: AHB for Windows Server and SQL Server — your most valuable SA benefit — does continue to be accessible through CSP for licences you acquired under EA, but only for the covered licence count at the time SA expires. New deployments after migration require Azure pricing without AHB unless you have active SA elsewhere.
The SA inventory alone regularly reveals six-figure entitlement value that would be abandoned in an uninformed migration. Run a complete SA value assessment before making any transition decision.
Gate 2: Perpetual Licence Rights
When your EA expires, you retain perpetual licence rights to the versions covered at the time of expiry. This is significant for organisations running on-premises workloads. The key rules:
- Office Professional Plus: Perpetual rights to the version current when SA expires (typically the version two years prior to the current release cycle)
- Windows Server: Perpetual rights to the Standard or Datacenter version active at SA expiry; Standard retains two-VM virtualisation rights; Datacenter retains unlimited VM rights
- SQL Server: Perpetual rights to the edition and version current at SA expiry; virtualisation rights depend on the edition
- Exchange Server and SharePoint Server: Perpetual rights to the on-premises version at SA expiry — relevant if you are running hybrid deployments
These rights are yours permanently but need to be documented before transition. Microsoft does not proactively provide perpetual licence entitlement summaries. You must extract and retain a complete VLSC entitlement record before your EA expires. Once the EA closes, VLSC access for that enrolment becomes read-only and eventually archived.
Gate 3: Azure Footprint and MACC Status
If your organisation has a Microsoft Azure Consumption Commitment (MACC) within the EA, migration to CSP has direct financial consequences. MACC commitments — typically negotiated as part of large EA renewals — provide access to deal desk discounts, co-investment funding, and Azure reserved instance bundling that substantially reduce effective Azure costs.
In CSP, Azure is purchased through the CSP partner as Azure Plan consumption. There is no MACC framework in CSP. Organisations transitioning from a £2M+ MACC EA to Azure via CSP typically see effective Azure costs increase by 15–25% in Year 1 even before accounting for the loss of reserved instance bulk purchasing leverage. If your MACC is material, it almost always justifies EA renewal over CSP migration for your Azure workloads.
Gate 4: Headcount Trajectory
CSP's primary advantage is seat flexibility. If your user count is genuinely stable or declining slowly, this advantage evaporates and you are left paying CSP's premium pricing (typically 12–18% above a negotiated EA for M365 E3) for flexibility you never exercise. Run a 36-month headcount projection before using flexibility as a migration justification.
Migration Timing Strategy
The worst time to migrate from EA to CSP is at EA expiry with no preparation. The best time is 12–18 months before expiry, allowing you to run a structured parallel period and ensure continuity.
| Timeline Marker | Action Required | Priority |
|---|---|---|
| 18 months before expiry | Decision: migrate vs renew. Run viability test (Gates 1–4 above). Commission independent cost comparison over 3 years. | Critical |
| 12 months before expiry | If migrating: select CSP partner(s). Issue RFP, evaluate on licensing expertise not just price. Negotiate CSP discount structure. Begin SA benefit documentation. | Critical |
| 6 months before expiry | Run parallel deployment test. Confirm M365 tenant migration path. Resolve any Azure subscription reassignment. Negotiate CSP annual terms and price protection clauses. | High |
| 90 days before expiry | Download complete VLSC entitlement records and licence keys. Confirm perpetual licence inventory. Notify Microsoft of non-renewal intent to prevent auto-renewal. | Critical |
| 60 days before expiry | Activate CSP subscriptions in parallel with EA if possible. Test licensing coverage continuity. Resolve any product gaps between EA and CSP coverage. | High |
| EA expiry day | Confirm all users transitioned to CSP subscriptions. Verify no service interruption. Archive EA documentation. Confirm perpetual licence server access. | Critical |
| 30 days post-expiry | Conduct first CSP licence count audit. Verify no over-assignment. Confirm Azure subscription billing correctly transferred. Close out any EA true-up obligations. | High |
The Five-Phase Migration Playbook
Every successful EA-to-CSP migration I have managed follows the same five-phase structure. The phases can compress in timeline but should never be skipped. Skipping phases is the primary cause of post-migration compliance exposure and cost overruns.
Entitlement Capture and Baseline
Weeks 1–4The foundation of a clean migration is a complete, verified entitlement record from your current EA. This is not the same as your most recent true-up — it is a comprehensive catalogue of every licence, SA status, perpetual right, and benefit that your organisation holds under the agreement.
- Export full VLSC licence summary (enrolment details, product list, SA expiry dates, deployment summaries)
- Download all product activation keys — both MAK (multiple activation) and KMS keys — and store securely offline
- Document all SA benefits by product: licence mobility, step-up rights, ESU eligibility, home use programme, e-learning vouchers
- Map Azure Hybrid Benefit coverage: which Windows Server and SQL Server deployments rely on AHB from current SA?
- Identify all licences with licence mobility attached — particularly SQL Server in hosted/colocation environments
- Record the exact version of each perpetual licence entitlement (the version current at SA expiry, not the latest version)
CSP Architecture Design
Weeks 3–8You cannot simply map your EA products 1:1 to CSP equivalents. Some EA products have no CSP equivalent. Some CSP products cover different user populations than their EA counterparts. And the licence assignment model in CSP — subscription-based, per-seat — requires a clean user directory before transition.
- Map each EA product to its CSP equivalent: confirm which products are available in CSP and which are not (note: many Server and CAL products are not available via standard CSP)
- Products with no CSP path (on-premises server products without cloud equivalents) must be handled via perpetual licence post-expiry or Hybrid Use rights — document these separately
- Design the CSP subscription structure: one CSP partner or multiple? Direct CSP or indirect? Annual or monthly billing?
- Determine Azure treatment: Azure Plan via CSP (standard CSP path) or separate MCA/direct channel for Azure? This decision has significant cost implications.
- Clean your Azure AD/Entra ID user directory before migration to avoid assigning licences to inactive accounts — this is one of the most common sources of post-migration overspend
CSP Partner Selection and Commercial Negotiation
Weeks 6–10The CSP partner you select will become your primary contact for billing, licensing support, and escalation. This is a multi-year relationship, not a commodity transaction. Most organisations underinvest in CSP partner selection and pay for it within 12 months when a licensing question arises that the partner cannot answer.
- Issue an RFP to at least three CSP partners — evaluate on licensing expertise, Microsoft specialisation certifications, and support capability, not solely on price
- Require partners to demonstrate specific Microsoft licensing competency, particularly for your most complex products (SQL Server, Windows Server, Dynamics 365, or whatever your environment requires)
- Negotiate your CSP discount structure explicitly — the default CSP partner margin is typically 8–12%; negotiate for additional rebates tied to volume and commitment
- Agree support SLAs in writing: response times for billing queries, licensing questions, and escalations to Microsoft should all be contractually defined
- Evaluate whether to use a single CSP partner (simpler management) or multiple partners (competitive tension, specialist coverage) — for most organisations under £2M CSP spend, single-partner is the right answer
- Negotiate price protection: ask for annual price caps or price-match guarantees for the initial 2–3 year period
Parallel Run and Validation
Weeks 10–14If your EA expiry timeline allows, running a 4–6 week parallel period — where CSP subscriptions are active and verified before EA expiry — eliminates the continuity risk that ruins most migrations. The parallel run costs something in duplicate licensing but is almost always worth it.
- Activate CSP subscriptions for a pilot user group (typically 50–100 users) to validate licence assignment, activation, and service access before full cutover
- Verify that all M365 services activate correctly under CSP — particular attention to Compliance add-ons, Defender configurations, and any tenant-level settings that may be affected by subscription type change
- Test Azure Hybrid Benefit application under the CSP Azure Plan — confirm that your Windows Server and SQL Server AHB registrations carry forward correctly
- Validate CSP billing reporting matches your internal headcount data — any discrepancies now are far cheaper to resolve than post-transition billing disputes
- Run a licence compliance check against your deployment scan to confirm CSP seat counts match actual deployment at the point of transition
Cutover, Closeout, and Post-Migration Governance
Weeks 14–20The cutover itself is rarely the hard part — it is the closeout obligations from the EA and the establishment of ongoing CSP governance that organisations consistently underestimate.
- Submit your final EA true-up accurately — any underpayment becomes a post-expiry invoice obligation; any overpayment is difficult to recover once the EA is closed
- Formally notify Microsoft of non-renewal at the contractually required notice period (typically 60 days before anniversary, check your specific EA terms)
- Establish CSP monthly billing review process: unlike EA's annual true-up, CSP bills monthly and seat counts can drift upward without a monthly review discipline
- Implement licence harvesting as a standard process — in CSP, unused licences continue billing until actively cancelled; there is no annual reconciliation that creates a natural clean-up event as with EA true-ups
- Schedule a 6-month post-migration review to compare actual CSP spend versus the pre-migration 3-year cost model — this identifies whether the migration financial case is playing out as expected
Products That Cannot Move to Standard CSP
This is the area where most EA-to-CSP migrations develop unexpected compliance exposure. Not every Microsoft product available under an EA is available via standard CSP channels. The following categories require specific handling:
| Product / Scenario | EA Treatment | CSP Treatment | Migration Path |
|---|---|---|---|
| SQL Server on-premises | Core licences + SA, licence mobility | Not available via CSP | Retain perpetual rights post-EA expiry; purchase ESU separately if needed; migrate to Azure SQL for new deployments |
| Windows Server on-premises | Core licences + SA, unlimited VMs (DC) | Not available via CSP | Retain perpetual rights; purchase ESU separately; consider Azure Stack HCI for new deployments |
| Exchange Server / SharePoint Server | Server + CAL + SA, hybrid rights | Not available via CSP | Retain perpetual rights; migrate remaining workloads to Exchange Online / SharePoint Online via CSP M365 subscriptions |
| Remote Desktop Services / RDS CALs | RDS CALs with SA | Not available via CSP | Retain perpetual rights post-EA; migrate to Azure Virtual Desktop (AVD) via Azure Plan for new deployments |
| Project / Visio desktop | Desktop licences + SA | Available via CSP as subscription | Transition to Project Plan / Visio Plan subscriptions via CSP — verify users need full desktop vs web app |
| Visual Studio subscriptions | Enterprise/Professional + SA | Available via CSP | Transition to VS subscriptions via CSP; verify Azure credit entitlements carry forward; watch for double-purchase with Azure DevOps |
| Dynamics 365 on-premises | Server + CAL model + SA | Not available via standard CSP | Migrate to Dynamics 365 cloud subscriptions via CSP or MCA; perpetual on-premises rights are retained but new licensing must be cloud |
The Five Most Expensive Migration Mistakes
After 80+ EA-to-CSP transitions, the failure patterns are consistent. These are the five that cause the most financial damage:
1. Migrating Without Running a 3-Year Cost Model
The flexibility argument for CSP is compelling until you price it. A 3-year cost model comparing total licensing costs under EA versus CSP — incorporating actual expected headcount changes, Azure spend, SA value, and partner margin — almost always tells a different story than the headline CSP per-seat price suggests. Organisations that skip this model routinely discover 18 months post-migration that they are spending 15–22% more than they would have under a renegotiated EA.
2. Losing Perpetual Licence Keys Before Expiry
The licence keys for your perpetual entitlements are stored in VLSC while your EA is active. Post-expiry, VLSC access is retained for 5 years for the enrolled organisation, but the experience for retrieval degrades significantly. The operational reality is that if you have a server rebuild or disaster recovery event 18 months post-migration and cannot find your Windows Server 2022 Datacenter activation key, you are in a genuinely difficult position. Download everything before you close the agreement.
3. Failing to Address Azure Separately
Treating Azure as just another product to move to CSP is a mistake for any organisation spending more than £500,000 per year on Azure. Azure via CSP through a standard partner has no MACC framework, no deal desk negotiation, and effectively no commercial leverage. Large Azure consumers should maintain a direct Azure relationship — through EA, MCA-E, or direct Microsoft Azure agreement — even when moving M365 to CSP.
4. Choosing a CSP Partner on Price
The cheapest CSP partner is frequently the most expensive one within 24 months. The partner's value is not in billing administration — it is in licensing guidance when complex questions arise and escalation capability when billing disputes occur. A partner saving you 1% on CSP margin who cannot answer whether your SQL Server deployment is correctly licensed under AHB will cost you that 1% saving many times over in a single licensing event.
5. Not Notifying Microsoft of Non-Renewal in Writing
Many EAs contain auto-renewal clauses that activate unless written notice of non-renewal is given by a specific date (typically 60 days before anniversary). Missing this notice date means your EA renews for another year at terms you did not intend to accept. Check your specific EA terms and calendar the notice date at least 90 days before it falls due.
Planning an EA to CSP Migration?
The difference between a clean migration and a costly one is preparation. Our advisors have managed 80+ EA-to-CSP transitions covering every product category and complexity level. We help organisations capture full entitlement value before expiry, negotiate the right CSP structure, and avoid the compliance gaps that routinely follow uninformed migrations.
Migration Assessment
A full viability analysis: SA inventory, perpetual rights catalogue, Azure impact assessment, and 3-year cost comparison before you commit.
Get AssessmentEA Renewal Review
Not sure whether to migrate or renew? We benchmark your EA pricing and identify negotiation leverage before you make the decision.
Review Our EA ServiceCSP Partner Evaluation
Selecting the wrong CSP partner is a three-year mistake. We evaluate and shortlist partners based on licensing competency, not just commercial terms.
Get Partner HelpWhen to Bring in Independent Advice
Not every EA-to-CSP migration requires independent advisory support. A straightforward transition for a 200-seat M365-only organisation with no on-premises server footprint and no Azure spend can be managed internally with good preparation. But several situations strongly warrant independent support:
- On-premises server footprint: If your environment includes SQL Server, Windows Server, Exchange Server, or SharePoint Server with SA, the entitlement complexity almost always justifies independent support. The cost of getting the perpetual rights or licence mobility transition wrong substantially exceeds advisory fees.
- Azure spend above £500,000 per year: The commercial structure of Azure in CSP versus EA requires a detailed analysis that goes beyond standard product comparison. The MACC implications alone warrant independent review.
- Multi-enrolment or multi-entity EA: Organisations with multiple EA enrolments, subsidiaries, or affiliates on the EA face additional complexity in determining which entities move to CSP and which perpetual rights follow each entity.
- Contentious EA history: If your relationship with your Microsoft account team has been adversarial or if there are outstanding true-up disputes, having independent advisors manage the transition communication reduces the risk of commercial games-playing at expiry.
The key principle is the same as it is for EA negotiations: independent advice eliminates the conflict of interest that exists when your guidance comes from someone who earns a commission on what you buy. In EA-to-CSP transitions, this matters because the CSP partner you select has a direct financial interest in maximising your CSP subscription count, which is not always aligned with minimising your total cost.