Most companies do not plan to leave their managed service provider. They get pushed there. Response times slip, invoices stop making sense, the same questions go unanswered, or the team that knew your environment moves on.
The good news is that you can switch AWS managed services provider without taking anything offline. The hard part is not the technology. It is knowing who owns what: the accounts, the billing relationship, the commitments, the access, and the documentation.
This guide explains how to switch, using AWS’s own documentation on accounts and organizations. You will learn:
- The signs that it is time to move, and the reasons that do not justify it
- How account and billing ownership changes what is possible
- A step by step plan, from audit to cutover to cleanup
- What to do about Savings Plans, credits, access, and downtime
- How to pick a replacement, with a checklist and common mistakes
Contracts and AWS features change, so confirm current details with AWS and with your providers before you act.

What Does It Mean to Switch AWS Managed Services Provider?
Switching AWS managed services provider means moving the day-to-day operation of your AWS environment from one managed service provider (MSP) to another. It covers contracts, account and billing ownership, access roles, monitoring, documentation, and support, and it should happen without downtime or loss of control over your accounts and data.
Notice what is not on that list: rebuilding your infrastructure. In most cases the workloads stay exactly where they are. What changes is who looks after them, who pays AWS, and who holds the keys.
When Should You Switch AWS Managed Services Provider?
One bad week is not a reason to leave. A pattern is. These are the signs that usually justify a move.
Signs It Is Time
- Slow or inconsistent response. Tickets sit for hours, or critical incidents wait on one person.
- Repeated outages with no root cause. You get apologies, not post-incident reviews.
- Billing you cannot explain. Management fees, markups, or support charges are unclear, and your AWS bill keeps growing.
- No proactive work. Nobody suggests cost savings, security fixes, or architecture improvements.
- Weak documentation. You could not rebuild your environment from what they have given you.
- Lock-in tactics. Accounts sit in their organization, root access is theirs, or exit terms are vague.
- Mismatch with your growth. You have outgrown a small shop, or a large provider treats you as a small account.
- Missing credentials. They cannot show independent validation, such as the AWS MSP Program, or relevant AWS competencies.
Reasons That May Not Justify a Switch
Before you leave, ask whether a conversation could fix the problem. A switch has real costs in time, risk, and attention. Consider staying if:
- The issue is one missed deadline, and the provider owned it and fixed the cause.
- Your needs are unclear, so a new provider would hit the same wall.
- The real problem is internal, such as approvals that take weeks.
- You are in the middle of a launch, an audit, or a migration.
Write down your complaints and give the provider a fair chance to respond in writing. If the answers are weak, you now have a clear record to support your decision and a list of requirements for the next provider.
A Timing Note for AMS Advanced Customers
If your provider is AWS itself through AWS Managed Services (AMS) Advanced, the timing is not entirely yours. According to AWS’s end of support page, AMS Advanced stopped accepting new customers on June 30, 2026, and reaches end of support on June 30, 2027. AWS recommends finishing any transition by March 31, 2027.
AWS lists AMS Accelerate, AWS Support Unified Operations, partner-led solutions, and self-managed operations as the alternatives. If you lean toward a partner, start early.
Who Owns Your AWS Accounts? It Changes Everything
Before anything else, find out how your accounts are set up. There are three common arrangements, and each one changes how hard the switch will be.
Arrangement 1: You Own the Accounts
Your company created the accounts, holds the root user, and pays AWS directly. The provider works through IAM roles you granted. This is the easiest case. You revoke their roles and grant the new provider’s, and nothing about billing or ownership moves.
Arrangement 2: The Provider Owns the Organization
Your accounts are members of an AWS Organization run by the provider, and the provider is the payer. This is common with resellers. The provider’s management account pays the bill and may control policies and the root user. Here, you will need to move your accounts out of their organization, and that takes planning.
Arrangement 3: Billing Transfer
AWS introduced Billing Transfer in November 2025. It lets a partner take financial responsibility for a customer’s AWS Organization while the customer keeps full control of its own management account. Press coverage of the launch reported that either side can revoke the transfer, so ask your provider how to end it cleanly and what happens to billing afterward.
Ask your provider for a written list of your accounts, the organization each belongs to, and who holds root access. If they cannot answer plainly, treat that as a finding.
What Changes Hands When You Switch
Moving providers touches more than logins. Use this table as a starting inventory.
| Item | Often controlled by | What to check |
| AWS accounts and root user | You or the provider | Who can sign in as root, and which email and MFA protect it |
| Billing and invoices | You or the provider | Who the payer is, and what markup applies |
| Support plan | Account or organization | Whether it stays with the account or comes from the payer |
| Savings Plans and Reserved Instances | The purchasing account | Which account bought each, and how sharing works |
| Credits and discounts | AWS and your agreements | The terms of each, and whether they move with accounts |
| IAM roles and access keys | The provider | Every role, user, and key they created or use |
| Infrastructure as code and runbooks | The provider or you | Where the code lives and who owns the repositories |
| Monitoring, alerts, and on-call | The provider | Which tools, dashboards, and paging rules they run |
| Backups and disaster recovery | The provider | Where backups are stored and who can restore them |
| Marketplace subscriptions and licenses | Whoever bought them | Renewal dates and whether they can transfer |
The Risks of Switching, and How to Lower Them
Switching has real risks, and most are manageable with planning.
- Downtime. Rarely caused by the switch itself, but by rushed access changes or alert gaps. Run both teams in parallel to reduce it.
- Lost knowledge. The old team knows why things are built the way they are. Capture it before they leave.
- Billing surprises. Moving accounts can change payer, support plan, discounts, and payment method.
- Security gaps. Old roles and keys left behind are a risk, and so are rushed new ones.
- Cost. Onboarding fees, overlapping contracts, and internal time all add up.
- Provider reluctance. A leaving provider may be slow with handover. Your contract and your account ownership are your best protection.
How to Switch AWS Managed Services Provider Step by Step
Use this order. It puts information first, access in the middle, and removal last, so you never lose control at any point.
- Audit your environment. List every account, organization, workload, tool, and open ticket.
- Read your contract. Note the notice period, minimum term, exit fees, and handover duties.
- Write your requirements. Decide what you need that you are not getting today.
- Shortlist and compare providers. Check MSP Program validation, competencies, and references.
- Plan the ownership move. Decide what, if anything, must change in account and billing ownership.
- Give the new provider limited access. Start with read-only roles, then add permissions.
- Transfer knowledge. Collect architecture, runbooks, code, and monitoring details.
- Run both teams in parallel. Test alerts, restores, and incident handling together.
- Cut over in a planned window. Move paging, contacts, billing, and support.
- Offboard the old provider. Remove roles and keys, rotate secrets, and review activity.
Step 1: Audit What You Have
Build one inventory before you talk to any new provider. Include:
- Every AWS account ID, its purpose, and the organization it belongs to
- Who holds root access and which email address is attached
- The payer account and the payment method
- Savings Plans, Reserved Instances, credits, and Marketplace subscriptions
- IAM roles and users the current provider created or uses
- Monitoring tools, alert rules, dashboards, and on-call schedules
- Infrastructure as code repositories and CI/CD pipelines
- Backup and disaster recovery setup, with the date of the last restore test
If the provider holds this information, ask for it in writing now. A provider with a good exit process will share it. If they resist, that tells you what you need to know.
Step 2: Review the Contract and Exit Terms
Your managed services agreement decides how smooth the exit will be. Look for:
- Notice period and minimum term. When can you give notice, and how long must you pay?
- Early termination fees. What is charged if you leave before the term ends?
- Transition assistance. Does the provider have to help with handover, and for how long?
- Ownership of work. Who owns scripts, templates, runbooks, and dashboards they built?
- Access removal. How quickly must they remove their access after termination?
- Billing terms. What happens to usage, support, and commitments in the final month?
If the contract is silent on handover, ask for a short exit letter that spells it out. Legal review is worth it here.
Step 3: Define What You Need
Write down why the current arrangement fails, and what the new one must deliver. Think about response times, coverage hours, security and compliance support, cost optimization, DevOps help, and reporting. These requirements become your shortlist criteria and your first contract schedule.
Step 4: Shortlist Providers and Check Credentials
Use AWS’s own tools to find candidates. The AWS Managed Service Provider Program validates partners through a third-party audit of technical skills and business health, and validated partners get an MSP badge. You can search for them in the AWS Partner Solutions Finder, where each listing shows competencies, program participation, certifications, and customer references.
Compare at least three, and send each the same questions. We cover the questions in the next section.
Step 5: Plan the Ownership Move
This step depends on which arrangement you have.
If you own your accounts, there is nothing to move. Skip to step 6.
If the provider owns your organization, your accounts must leave it. AWS documents two routes.
- Leave, then join. AWS’s guide to removing a member account says the account must have a support plan, verified contact information, and a valid payment method before it can leave. Once it leaves, the account owner is responsible for new AWS costs, and the account’s own payment method is used. AWS Support cannot remove a member account on your behalf.
- Direct transfer. Since November 2025, AWS has supported direct account transfers between organizations, where the new organization invites the account and the account accepts, with no standalone period. AWS’s migration guide says the migrating account’s support plan should match the payer account in the new organization.
Whichever route you use, plan for these items:
- Export billing and cost reports first, since organization-level history stays with the old organization.
- Check which account owns each Savings Plan and Reserved Instance, since AWS says the purchasing account owns them.
- Rebuild what lived at the organization level, such as service control policies, resource sharing, trusted access, and delegated administrators.
- Re-activate cost allocation tags in the new organization.
- Set up a valid payment method so there is no gap in billing.
Test the process on a non-production account first.
Step 6: Grant the New Provider Limited Access
Give the new provider cross-account IAM roles, not long-term access keys. Require multi-factor authentication for any human sign-in, and use an external ID in the trust policy for third parties, which protects against the confused deputy problem. Start with read-only access for discovery. Add change permissions only as the provider takes over each area.
Step 7: Transfer Knowledge
Schedule working sessions between the old and new teams. Cover architecture and diagrams, deployment process, known issues, past incidents, monitoring and alert rules, backup and restore steps, and anything fragile. Ask the new provider to run a review against the AWS Well-Architected Framework to create a baseline and a list of risks.
Step 8: Run Both Teams in Parallel
A parallel period of 30 to 60 days is common. The new provider shadows operations, receives the same alerts, and handles low-risk work first. Use it to test:
- A restore from backup
- A simulated incident, with a real page
- A routine change through your normal approval process
- A cost and security review
Step 9: Cut Over in a Planned Window
Pick a quiet period, freeze non-essential changes, and move in this order : paging and on-call, ticket intake, alternate contacts on each AWS account, then billing and support plan changes. Tell your own team who to contact and when. Keep the old provider on standby until the first full week passes without issues.
Step 10: Offboard the Old Provider
Only after the new team is in control, remove the old provider’s access. We list the full checklist in the next section.
A Sample Timeline
These ranges are estimates and vary with environment size and contract terms.
| Phase | Typical length | Main output |
| Audit and contract review | 1 to 2 weeks | Inventory, exit terms, requirements |
| Selection | 2 to 4 weeks | Shortlist, answers, decision |
| Onboarding and access | 2 to 3 weeks | Roles, tooling, knowledge transfer |
| Parallel run | 4 to 8 weeks | Tested alerts, restores, drills |
| Cutover | 1 to 2 weeks | New provider in control |
| Offboarding and review | 2 to 4 weeks | Old access removed, final review |
How to Avoid Downtime When You Change AWS Providers
Downtime during a handover almost never comes from the move itself. It comes from gaps: an alert that nobody receives, a role removed too early, or a change nobody realized was routed through the old team. These habits close those gaps.
- Overlap, do not swap. Keep both providers active until the new one has handled real work. Never cut the old provider’s access first.
- Freeze non-essential changes. Avoid launches, upgrades, and migrations during cutover week.
- Test the alert path end to end. Trigger a harmless test alarm and confirm the new on-call person is paged.
- Restore something. Do a real restore from backup before you trust it.
- Document the cutover plan. List the steps, owners, and a rollback for each.
- Keep a rollback window. Do not remove the old provider’s roles until a full week has passed without problems.
The AWS Infrastructure Handover Checklist
Use this table in your meetings with both providers. Each row should have a name and a date next to it before you call the handover complete.
| Area | What to hand over | How to confirm |
| Accounts | Account list, organization map, root user details | New and old teams agree on the list |
| Access | Roles, users, SSO settings, MFA devices | Access review shows only expected principals |
| Code | Infrastructure as code, CI/CD pipelines, templates | You own the repositories and can run a plan |
| Monitoring | Dashboards, alarms, log destinations, paging rules | Test alert reaches the new on-call |
| Backups and DR | Schedules, storage locations, restore steps | A restore test succeeds |
| Security | Findings, exceptions, compliance reports, scan results | New provider reviews and accepts them |
| Cost | Reports, tags, budgets, commitments, credits | Monthly bill matches the expected plan |
| Support | Support plan, contacts, open cases | Cases are closed or transferred |
| Runbooks | Incident, change, and escalation procedures | New team runs one in a drill |
| Vendors | Third-party tools, licenses, Marketplace items | Renewal and ownership are clear |
Handling Billing, Commitments, and Credits
Money is where switching surprises people. Plan it as carefully as you plan access.
Billing and Payer Changes
When an account leaves an organization, the owner becomes responsible for new AWS costs, and the account’s own payment method is used. When it joins a new organization, AWS’s FAQ says it inherits that organization’s billing, support plans, and policies. Confirm in advance who will pay, which payment method is on file, and when the first invoice from the new setup arrives.
Savings Plans and Reserved Instances
AWS says the account that purchased a Savings Plan or Reserved Instance owns it. If your provider bought commitments in their own account and shared them, you may lose that discount when your accounts leave. Ask for a list of every commitment, the account that holds it, its end date, and what it covers. Then decide whether to let it run out, buy your own, or negotiate a transfer or buyout.
Set up discount sharing in the new organization before the move, so that coverage continues.
Credits and Discounts
Credits, private pricing, and partner discounts are often tied to a specific account or agreement. Read the terms of each one, and ask AWS and your provider whether they continue after a change. Do not assume a promotional credit will follow you. If you are close to using credits up, time the cutover with that in mind.
Support Plans
Support plans may come through the payer account. Make sure your accounts have the plan you need on the day they move, so you are never without AWS support during an incident.
Security Cleanup After the Switch
The handover is not complete until the old provider’s access is gone. After the new team has been in control and stable, work through this list:
- Remove cross-account roles and trust relationships that name the old provider’s accounts.
- Delete IAM users and access keys created for the provider, and rotate any that cannot be removed.
- Remove SSO and identity provider access for the provider’s staff.
- Rotate secrets the provider could read, such as database passwords, API tokens, and certificates.
- Review key and bucket policies for statements that grant access to old principals.
- Revoke tool access, including monitoring, ticketing, source control, and VPN or bastion accounts.
- Update alternate contacts for billing, operations, and security on each AWS account.
- Run IAM Access Analyzer to find resources shared outside your account or organization.
- Review CloudTrail for activity by the old provider’s principals, to confirm access has really stopped.
Run the same exercise for the new provider in a few months. Access tends to grow over time, so review it on a schedule.
How to Choose Your Next Provider
A switch only helps if the next provider is a real improvement. Use what you learned from the first time.
Check Independent Credentials
Start with the AWS MSP Program, which validates partners through a third-party audit. Then check relevant competencies, such as DevOps, Security, or Migration, plus certifications and customer references on the partner’s listing in AWS’s partner finder. Ask when the last audit happened and which services it covered.
Questions to Ask Every Candidate
- Who will own the AWS accounts, the root user, and the billing relationship?
- What does your response time commitment look like, by severity, in writing?
- How do you access our accounts, and how can we revoke that access at any time?
- Where will infrastructure code and runbooks live, and who owns them?
- What is included in your fee, and what costs extra?
- What are the minimum term, notice period, and exit fees?
- What help do you give if we ever leave?
- Can we speak with a customer who switched to you from another provider?
Protect Yourself Next Time
Whatever the provider, a few terms prevent a repeat of this project:
- You own the AWS accounts and root users, and the provider works through roles you can revoke.
- Infrastructure code lives in repositories you control.
- Notice periods are short, and exit assistance is written into the contract.
- Documentation is a deliverable, not a favor.
- You receive regular reports on cost, security, and incidents.
Consider the Alternatives
A new MSP is not the only option. Depending on your size, you could hire in-house staff, use a hybrid model, or use an AWS operated service. For example, AWS lists AMS Accelerate and AWS Support Unified Operations as alternatives for customers leaving AMS Advanced. Compare the full cost of each, including your own team’s time.
Switch, Stay, or Go Another Way? A Comparison
| Option | Best when | Main risk |
| Stay and fix the relationship | Problems are specific and the provider responds to feedback | Same issues return |
| Switch to a new MSP | Problems are repeated, and you have clear requirements | Handover gaps, cost, time |
| Hybrid with your own team | You have some engineers and need 24/7 coverage | Unclear responsibilities |
| Bring operations in-house | You have scale and strong engineers | Hiring time and on-call burden |
| AWS operated service | You are an enterprise that wants AWS to run defined tasks | Narrower scope, AWS pricing |
Common Mistakes When You Switch AWS Managed Services Provider
- Starting without an inventory. You cannot move what you cannot list.
- Ignoring account ownership. If the provider holds root or the organization, plan that first.
- Cutting off the old provider early. Overlap is cheap compared with an outage.
- Forgetting commitments. Savings Plans and Reserved Instances can disappear from your accounts when they move.
- Skipping the restore test. A backup you have never restored is a guess.
- Leaving old access in place. Stale roles and keys are a quiet risk.
- Choosing on price alone. The cheapest fee often excludes the work you need.
- Letting the exit turn hostile. Stay professional, and rely on the contract and your account ownership.
One honest limit applies. Every environment is different, and contracts, AWS features, and pricing change. Use this guide as a framework, and confirm details with AWS, your current provider, and your legal advisor.
Decision Guide: Are You Ready to Switch?
- You own your accounts and root users: you can move quickly, starting with the contract and shortlist.
- The provider owns your organization: plan the ownership move first, and test it on one account.
- Your contract has a long notice period: start the shortlist now, and time the move to the end date.
- Your commitments sit in the provider’s accounts: inventory them, and plan for coverage gaps.
- You are an AMS Advanced customer: work backward from AWS’s recommended March 31, 2027 completion date.
- You are unsure of your requirements: run a short audit and a Well-Architected review first.
Practical Examples
These scenarios are illustrative, not real customer cases.
The clean exit. A startup owns its accounts, and its provider works through cross-account roles. It shortlists two validated MSPs, runs the winner in parallel for six weeks, and then removes the old roles. Billing never changes.
The reseller-owned organization. A mid-size company discovers that its accounts sit in its reseller’s organization. Before choosing a new provider, it creates its own organization, tests an account move on a development account, exports billing reports, and moves production in a planned window.
The hidden commitments. A team realizes its Savings Plans were bought in the old provider’s account. It lists each plan’s end date, lets the smaller ones expire, and buys its own plan for the baseline, so coverage does not drop after the switch.
Conclusion
You can switch AWS managed services provider without downtime, as long as you treat the move as an ownership project first and a technology project second. Confirm who owns your accounts and billing, read the contract, choose a validated replacement, overlap the two teams, and remove the old access only when the new team is in control.
Start this week by writing down every AWS account, who holds root access, and who pays the bill. That single page shapes every other decision in the switch.