Why Migrate from EA to CSP? Organizations moving from Enterprise Agreement (EA) to Cloud Solution Provider (CSP) achieve 15-25% annual cost savings, faster support (hours vs. days), and greater flexibility to scale. However, the migration path is complex and requires careful planning. This guide walks through the proven process TrustedTech uses with customers migrating 100+ user deployments. Read our guide on the five strategic reasons organizations shift from EA to CSP.
1. Perform a Full Licensing and Subscription Audit Before You Begin
You cannot successfully migrate without understanding exactly what you own and how it’s being used.
Before transitioning, document all EA licenses including Microsoft 365, Dynamics, SQL Server, and CALs. You’ll also need to inventory your Azure subscriptions and resource consumption patterns, reserved instances and savings plans with their commitment terms, Software Assurance entitlements for hybrid benefit eligibility and support packages, and your current billing and cost allocation models.
Why This Matters: A Real Example
One financial services client discovered during their audit that they were maintaining 150 unused M365 E5 licenses alongside active CSP plans. The overlap cost them roughly $45,000 annually. A licensing audit identified this redundancy before migration, saving significant expense.
Best Practices
Use Microsoft License Advisor (MLA) or a CSP partner audit tool to inventory EA entitlements. Analyze Azure usage data for the past 12 months, looking for unused VMs, storage, and low-utilization reserved instances. Document Software Assurance benefits that may transfer to CSP or require repurchase, and export billing and usage history for finance reconciliation post-migration.
Start with a comprehensive Microsoft licensing audit before you plan your migration timeline.
What Kind Of Microsoft 365 Admin Are You?
Discover where your Microsoft 365 stack is wasting money, adding risk, or creating unnecessary complexity.
2. Understand CSP Licensing Differences: What Transfers and What Doesn’t
Not all EA entitlements have direct CSP equivalents. On-premises software, legacy SKUs, and certain Server CALs often cannot be transferred.
This is where many migrations derail. Teams assume every EA license maps 1:1 to CSP, only to discover they need to repurchase software mid-migration.
Key Licensing Gaps
| EA Entitlement | CSP Equivalent | Notes |
|---|---|---|
| Microsoft 365 E5 | Microsoft 365 E5 | Direct equivalent; pricing differs slightly |
| SQL Server Enterprise | SQL Server 2022 Enterprise | Must repurchase under CSP |
| Windows Server Data Center CALs | Azure Hybrid Benefit | Covered under AHB for qualifying VMs |
| Office Pro Plus | Microsoft 365 Apps (Plan 1) | Software Assurance does NOT transfer |
| Extended Security Updates (ESU) | ESU SKUs in CSP | Must repurchase when EA ends |
Common Mistakes
Assuming all Software Assurance transfers to CSP is a frequent error; it doesn’t for most products. Not budgeting for "catch-up" licensing is another trap: if you have mid-cycle EA remaining, you’re not "renewing" every license at CSP rates; some licenses become available mid-cycle at prorated costs. Finally, overlooking Server CAL requirements causes problems when organizations run both on-premises and cloud workloads. Server CALs (User or Device) don’t translate directly to CSP; you may need different licensing for hybrid scenarios.
Review the pros and cons of switching from EA to CSP and learn what Extended Security Updates mean for your infrastructure.
Best Practice: Work with your CSP partner 6-8 weeks before migration to create a license mapping matrix. For each EA SKU, document the CSP equivalent (if one exists), pricing, SA implications, and required activation month. Budget 10-15% contingency for licensing surprises.
3. Choose the Right Transition Timing and Avoid Mid-Term Breaks
Migrate at your EA expiration date. Mid-term transitions trigger termination fees and billing complexity.
Timing is one of the single biggest cost levers in an EA-to-CSP migration.
Scenario A: Migrate at EA expiration has minimal cost impact (no overlap, no penalty fees) and clean billing continuity.
Scenario B: Mid-term migration results in early termination penalties of 10-15% of remaining EA value plus overlap billing. For a $500K annual EA, the potential penalty is $50-75K.
When Mid-Term Makes Sense
Mid-term breaks are justified only when you’re consolidating after a merger and standardizing on CSP, when an EA partner exits and you need a better-equipped CSP partner, or when Azure overspend is uncontrolled and CSP’s flexibility is critical.
Best Practices for Timing
Plan 4-6 months before your target migration date to give your CSP partner time to set up infrastructure and coordinate with Microsoft. Align CSP subscription activation to your EA end date; avoid overlaps where both EA and CSP licenses are active. Notify Microsoft and your CSP partner in writing 90 days before migration. Build in a 1-2 week buffer post-migration for unexpected issues.
Learn why CSP transitions need a long runway to avoid costly penalties.
4. Establish a Strong CSP Partner Relationship
Under CSP, your partner controls billing, support escalation, and license provisioning. Choosing the right partner is as important as the technical migration itself.
Your EA was with Microsoft directly; CSP puts your partner between you and Microsoft. A weak partner relationship becomes a major pain point post-migration.
What to Look for in a CSP Partner
Your CSP partner needs mandatory capabilities including active Azure expertise (not just license resellers), ability to handle your user volume and deployment complexity, multi-tenant support and governance experience, and 24/7 support escalation path to Microsoft. Strategic differentiators include Azure Expert MSP certification, cost optimization and licensing advisory, governance and compliance frameworks (Azure Policy, cost allocation), proactive monitoring and optimization rather than just reactive support, and industry-specific expertise.
Red Flags
Avoid partners who focus solely on licensing cost with no deployment strategy, partners without documented Azure infrastructure, partners who haven’t successfully migrated other EA customers, and partners with slow support response times.
How to Vet a Partner
Ask for customer references from organizations that migrated from EA to CSP in the last 12-18 months and call them to ask about billing accuracy, support response times, unexpected costs, and whether they’d migrate again. Review their Microsoft specialization credentials: Azure Expert MSP certification, competency levels (Azure Infrastructure, Cloud Productivity, Data and Analytics), and customer references on the Microsoft partner portal. Request a migration pilot on a test tenant to evaluate how they handle the transfer, post-migration billing accuracy, and responsiveness to issues.
TrustedTech’s Approach
TrustedTech customers work with a dedicated implementation team for 60 days pre-migration and 60 days post-migration. We conduct a full licensing audit, provision CSP tenant infrastructure 30 days before migration, manage all Microsoft coordination, validate billing accuracy for 2 months, and establish cost allocation frameworks.
See our detailed guide on how to plan a successful Microsoft EA to CSP migration.
5. Create a Detailed License Mapping Matrix
Every EA SKU must map to a CSP equivalent or documented alternative. This matrix is your migration roadmap.
This step is often skipped, leading to licensing gaps, surprise costs, and support disruptions. For each SKU, document whether it will transfer exactly (Yes, No, Partial), what the alternative is if it doesn’t transfer (buy CSP equivalent, use hybrid benefit, sunset the license, etc.), when it needs to be active in CSP, and how much it will cost annually.
Example: Software Assurance Complications
Many organizations believe Server CAL Software Assurance transfers to CSP. It typically does not. With EA and Software Assurance, you own the User/Device CAL license and can use newer versions as they release during the SA period. With CSP, you rent CALs monthly. When SA expires, you cannot carry forward to a newer version without repurchasing.
Best Practice: Engage a Microsoft Licensing Specialist to validate your mapping matrix 8 weeks pre-migration. Budget 10-15% contingency for licensing surprises.
Explore how to reduce Microsoft 365 costs through smart licensing optimization once your mapping is complete.
6. Plan and Execute the Azure Subscription Transfer Carefully
Azure subscriptions transfer between EA and CSP are billing-context changes only. Resources and data stay in place; subscriptions move to your new CSP partner’s tenant.
This is often misunderstood. Many organizations fear a subscription transfer means re-provisioning resources. It doesn’t, but it does require careful coordination.
What Happens During Transfer
The subscription moves from EA to CSP billing context while RBAC, resource groups, and resources remain unchanged. Resource quotas reset (often an issue if you’re at or near subscription limits), billing stops under EA and starts under CSP, and support model transitions from EA support to CSP partner support.
Pre-Transfer Checklist
Export a full inventory of Azure resources (VMs, storage, databases), document all RBAC role assignments, review and export all cost allocation tags, verify subscription-level quotas (CPU cores, storage), confirm all connected services (ExpressRoute, Azure Stack) will remain functional, and back up custom configurations, scripts, and Azure DevOps pipelines.
Post-Transfer Validation
In week 1, confirm all VMs and services are running, validate RBAC assignments are intact, test Azure DevOps and build pipelines, and confirm monitoring and alerts are still active. In week 2, verify billing data in CSP portal matches expected costs, reconcile resource usage against pre-migration baseline, and confirm support tickets can be created through CSP portal.
Common Post-Transfer Issues
Azure DevOps pipelines fail when service connection credentials are tied to EA subscription; recreate service connections and update to new subscription context. Monitoring and alerts stop when they rely on subscription-specific rules; recreate alert rules in new subscription context. Reserved instances disappear because RIs do not transfer with subscriptions; have your partner repurchase RIs under CSP or map to new subscription. Quotas reset or hard limits get hit when post-transfer quota reset triggers limits; work with CSP partner to request quota increase.
Get our Azure implementation guide for the full scope of Azure work during your migration.
7. Test, Validate, and Update Post-Migration
Assume something will break after migration. Plan for 2-4 weeks of validation and remediation.
Post-Migration Testing
In configuration validation (week 1), ensure all Azure resources are running and accessible, all users can authenticate (Entra ID, MFA, conditional access), all RBAC is functional, all firewall rules and NSGs are working, and all storage accounts and databases are accessible.
For billing and cost validation (weeks 1-2), verify the CSP billing portal reflects correct usage, cost allocation tags are populated on all resources, monthly cost is within 5% of pre-migration baseline, and reserved instances and savings plans are active.
Service and applications validation (week 2) requires all applications and workloads running without errors, performance benchmarks matching pre-migration baseline, data pipelines and scheduled jobs executing successfully, and backup and disaster recovery systems functioning.
Support and escalation validation (week 3) involves testing support case creation through CSP partner portal, verifying support response times meet SLA expectations, confirming escalation path to Microsoft works correctly, and validating that your CSP partner can access and resolve Azure-level issues.
Common Post-Migration Discoveries
Azure DevOps and CI/CD pipelines need reconfiguration because service connections often lose credentials or scope. Monitoring and alerting are incomplete because subscriptions transfer but alert rules don’t always carry over. Cost allocation and tagging rules weren’t enforced, which is a good opportunity to implement Azure Policy for cost governance. Users have stale role assignments from the EA era, and RBAC transfers sometimes leave overly permissive roles.
8. Conduct Ongoing License Audits and Cost Optimization
CSP’s month-to-month flexibility only works if you actively review and optimize. Without ongoing audits, costs grow 10-20% annually.
Many organizations migrate to CSP for flexibility, then ignore their licenses and let costs drift. CSP requires active management.
Quarterly Optimization Activities
Review Azure resource utilization every quarter by identifying VMs with <20% CPU (downsize or stop), reviewing storage sizes for archiving or deletion opportunities, checking for unused app services, and estimating cost savings from rightsizing. Audit Microsoft 365 licenses by identifying inactive users (no login in 60+ days), deprovisioning licenses for terminated employees, assessing whether licensing tier reflects actual usage, and calculating cost savings from tier downgrades. Evaluate reserved instances and savings plans by reviewing current utilization (target 80%+), considering shorter-term commitments if utilization is dropping, and assessing RI or savings plan purchase for new workloads. Conduct cost anomaly analysis by comparing current month to 3-month rolling average, investigating cost spikes >15%, and auditing for unexpected resources.
Typical Optimization Results
Based on TrustedTech customer data from 50+ EA-to-CSP migrations, the average Year 1 savings is 18-22% through licensing optimization, average Azure cost reduction is 12-15% through rightsizing and reserved instances, and average total 3-year savings is 32-40%.
Automation and Governance
Set up Azure Policy to automatically tag resources, enforce naming conventions, and prevent oversized deployments. Use Azure Advisor for monthly optimization recommendations. Create budget alerts to set spending limits per department. Consider auto-purchase options: some CSP partners offer auto-RI purchase for recurring workloads to reduce management burden.
When to Revisit Licensing Tiers
Move E5 users to E3 if they don’t use advanced compliance, threat intelligence, or advanced analytics. Move E3 users to Business Standard if they don’t require on-premises Active Directory sync. Consider Business Basic for users needing just cloud storage and collaboration. Potential savings range from $15-30 per user annually by right-sizing.
Frequently Asked Questions
Q: How long does an EA-to-CSP migration take?
A: Typically 60-90 days from start to finish: 30 days planning and setup, 7-10 days for subscription transfer and cutover, 30-60 days for validation. Large, complex environments may take 4-6 months.
Q: Will my Azure resources migrate with the subscription?
A: Yes. Subscriptions are billing containers; resources stay in place. The only change is the billing context. No downtime or re-provisioning required.
Q: Can we keep our EA and add CSP at the same time?
A: Technically yes, but not recommended. Overlapping EA and CSP creates double billing ($2K-10K+ per month), complexity in cost allocation, and confusion about ownership. Migrate at your EA end date if possible; minimize overlap to 1-2 months max.
Q: What happens to my support if I move from EA to CSP?
A: EA support transitions to CSP partner support. Most CSP partners offer support equivalent to or better than EA support (24/7, faster response). Confirm support SLAs with your CSP partner before migration.
Q: Will my costs go down or up?
A: Typically down 15-25% for most organizations, depending on your current EA discount level, your CSP partner’s pricing, and your ability to optimize. Negotiate CSP pricing upfront; don’t assume CSP is automatically cheaper.
Q: Can I use Software Assurance benefits in CSP?
A: Partially. Software Assurance doesn’t transfer for most products. However, Azure Hybrid Benefit lets you bring Windows Server and SQL Server licenses to Azure (reduces cost), M365 SA may transfer under specific conditions, and Server CAL SA typically doesn’t transfer. Have your CSP partner validate SA eligibility.
Q: What if something goes wrong during migration?
A: Your CSP partner should have a documented rollback plan. If a subscription transfer fails, you can roll back to EA and try again. Coordinate the rollback plan before migration.
Q: How do I optimize costs after moving to CSP?
A: Set up quarterly cost reviews with your CSP partner. Focus on right-sizing Azure resources, purchasing reserved instances and savings plans, auditing and deprovisioning unused licenses, and using Azure Advisor to identify savings. See our comprehensive EA to CSP FAQs.
Migration Checklist by Phase
| Phase | Timeline | Key Activities | Outcomes |
|---|---|---|---|
| Discovery & Audit | Months 1-2 | Full licensing audit, usage analysis, SA review | Documented inventory, cost baseline |
| Planning & Partner Selection | Months 1-3 | Partner vetting, license mapping, migration schedule | Partner selected, transition plan, budget approved |
| Pre-Migration Setup | Month 3 | CSP tenant provisioning, infrastructure setup | CSP environment ready, Microsoft coordination initiated |
| Cutover | Week 1, Month 4 | Subscription transfer, billing transition | Subscriptions moved, billing activated, resources verified |
| Post-Migration Validation | Weeks 2-4, Month 4 | Testing, configuration validation, billing reconciliation | All systems operational, accurate billing |
| Ongoing Optimization | Months 5+ | Quarterly audits, cost reviews, governance | Sustained optimization, operational efficiency |
Ready to Migrate? Let’s Talk
TrustedTech has successfully migrated organizations from Enterprise Agreements to CSP, delivering an average of 18-22% Year 1 cost savings. Our dedicated EA-to-CSP migration team handles all the complexity.
See how we helped Nordic Investment Bank save 15-20% annually on licensing while gaining faster support. Ready to start your migration? Contact our team for a free assessment.
