What Do You Need Back From Your Old IT Provider?

🔄 Provider Handover Guide

What Do You Need Back From Your Old IT Provider?

The hardest part of changing IT providers is not choosing the new one. It is getting your own systems back from the old one. Here is the full handover list, in writing, before you give notice.

  • Most businesses do not hold admin credentials to their own domain, tenant or firewall — their provider does
  • Ask for the handover list before you give notice, while you still have leverage
  • Domain and DNS control is the most urgent item — losing it takes down email and website together
  • Backups held in a provider-owned tenant can disappear when the contract ends
  • Overlap both providers two to four weeks; it costs one month and removes nearly all the risk
⭐ 5.0 Google RatingMicrosoft PartnerSOC 2 Ready24/7 Live SupportMSP 501 Top 50

Free IT Assessment

No obligation. We evaluate your environment and deliver a clear action plan within 24 hours.

20+Years in Business
8minAvg. Response Time
99.9%Uptime Guarantee
0hrsContracted Downtime
#36MSP 501 Nationally
#4MSP in California
Straight Answers — Advanced Networks

Straight Answers
What you are owed, in writing
24/7 Monitoring — Advanced Networks

Clean Cutover
Access moved, nothing goes dark
Your Account Manager — Advanced Networks

Second Opinion
We review before you commit
Start Here

Changing IT Providers Without Losing Access

Most businesses discover mid-transition that they do not hold the administrative credentials to their domain registrar, their Microsoft tenant, or their firewall. Their provider does, and always has. That is normal, and for day-to-day operations it is fine. It becomes a problem the moment the relationship ends.

This page is the checklist of what you are owed, what to do when it is not forthcoming, and how to sequence the change so nothing goes dark.

  • Request a documentation and credential review at any time — you do not have to announce you are leaving
  • Check your agreement for a transition-assistance clause before you serve notice
  • Handover is a transfer of access, not a change to running systems — downtime is avoidable
  • What happens on the incoming side is covered in our guide to MSP onboarding
30–90
days typical notice periodCheck Your Contract First
7
categories to reclaimThe Handover List
2–4
weeks of provider overlapRemoves Most of the Risk
#1
most urgent single itemDomain & DNS Control
The Handover List

What You Are Owed on Exit

Ask for all of this in writing, before you give notice. Every item below is yours, not your provider’s.

🌐
Domain & DNS
Registrar login, or confirmation the domain is registered in your company name with you as administrative contact. Full DNS zone export. The most urgent item on this list.
☁️
Microsoft 365 or Google Workspace
Global administrator credentials, and confirmation the tenant is billed to you rather than resold under your provider’s agreement. Resold tenants need a formal partner-relationship change, not just a password.
📡
Network Equipment
Firewall, switch and wireless controller admin credentials, current configuration exports, and any active support or licence contracts with renewal dates and account numbers.
🖥️
Servers & Endpoints
Local administrator credentials, virtualization host access, and a list of installed management agents so they can be removed cleanly.
💾
Backups
Where backups live, how to access them, retention settings, and whether the storage account is yours or theirs. This one catches people out.
💼
Line of Business Apps
Vendor names, account numbers, support contacts and admin credentials for every business application. The most commonly missed category and the most painful to rebuild.
📄
Documentation
Network diagrams, asset inventory, licence records, and the password vault or its export.
📧
Email Security & Filtering
Tenant-level spam and phishing filtering configuration, quarantine access, and any third-party mail-flow rules pointed at your domain.
🔑
Remote Access & VPN
VPN configuration, user accounts and certificates, plus any remote-access tooling installed on your machines that needs removing cleanly.
When It Goes Wrong

When the Outgoing Provider Stops Cooperating

Most handovers are professional. Some are not. Four things help, in this order.

01
Quote Your Own Contract
Many agreements contain an explicit transition-assistance clause with a defined period. Pointing to it in writing resolves most stalled handovers on its own.
02
Go Direct to the Vendors
Your domain registrar, Microsoft, and your firewall manufacturer all have documented account-recovery processes that work without the incumbent. They take time and require proof of ownership.
03
Settle Billing First
In practice most disputes are about unpaid invoices rather than the data itself. Clear any billing questions before you request the handover.
04
Accept a Rebuild
Your new provider may need to reset credentials, redeploy agents and re-document from scratch. It adds a week or two. It is not a disaster.
05
Document Every Request
Date every request and keep the thread. A written trail resolves most disputes, and it is what a registrar or vendor will ask you for if you have to go around the incumbent.
06
Ask Before You Give Notice
Request the documentation and credential review while you are still a paying client. Your leverage disappears the moment you serve notice.
Ownership

What You Own Versus What They Own

The distinction that catches people out. The first five are yours and stay when the provider goes. The last five leave with them.

📁
Your Data
In every system, including backups
🌐
Your Domain
Registrar and DNS control
☁️
Your Tenant
Microsoft 365 or Google Workspace
🖥️
Your Hardware
Servers, endpoints, network gear
📄
Your Documentation
Diagrams, inventory, licence records
🛠️
Their RMM Agents
Removed from your machines on exit
🎫
Their Ticketing System
Export your history before you go
🔌
Their Remote Tooling
Access revoked, agents uninstalled
🧾
Partner-Bought Licences
Usually cannot transfer — re-procured
🗄️
Their Backup Platform
Get your data out before it ends
Timing

How Long to Run Both Providers

Two to four weeks of overlap costs one extra month of fees and removes almost all of the risk.

01
Check Your Notice Period
Thirty to ninety days is standard. The notice clock and the overlap window are two different things — you can serve notice and keep paying through the overlap.
02
Know Your Renewal Date
Some agreements auto-renew unless notice lands in a specific window. Knowing the date is often the difference between leaving cleanly and paying for another year.
03
Ask About Licensing
Software bought under a provider’s partner agreement usually cannot transfer. Your new provider re-procures it, sometimes at a different price. This can change the economics of the move.
04
Avoid the Hard Cutover
The alternative to overlap is the old provider’s access ending Friday and the new one starting Monday having never seen your environment. Do not do that.
05
Verify Every Item First
Before the old access ends, confirm you can actually log in to each item on the handover list. A credential that does not work is the same as one you never received.
06
Move DNS on Its Own
Do not change registrar, mail routing and firewall in the same window. Sequence them so one mistake cannot take everything down at once.
Frequently Asked Questions

Provider Handover Questions, Answered

What LA businesses ask us most when they are planning a move.

Can my IT provider hold my data hostage?
They cannot lawfully withhold data you own, and most agreements say so explicitly. In practice, disputes are usually about unpaid invoices rather than the data itself. Settle any billing questions before you request the handover, and put the request in writing.
What if my provider registered our domain in their own name?
It happens more than it should. Registrars have transfer-dispute processes, and evidence that your business has paid for and used the domain generally carries the day, but it is slow. Check who the registrant is now, not when you need to move.
Do we have to tell them we are leaving before asking for credentials?
No, and it is usually better not to. Requesting a documentation and credential review is a reasonable thing for any client to ask at any time.
Will changing providers cause downtime?
It should not. Handover is a transfer of access, not a change to running systems. Downtime risk comes from a rushed timeline or a missing credential discovered at the wrong moment, both of which are avoidable by asking for the list first.
What if we are mid-contract?
Read the termination and transition clauses. Early exit sometimes carries a fee, and some agreements auto-renew unless notice lands in a specific window.
Should we tell our staff before the switchover?
Yes, shortly before. They need the new support contact details and a heads-up that ticket routing is changing. Beyond that the transition should be invisible to them, and if it is not, something has been sequenced badly.

Keep reading: Managed IT Pricing in Los Angeles · In-House IT vs Managed IT Costs · Co-Managed vs Fully Managed IT · Onsite IT Support · Managed IT Services Los Angeles

Get Started Today

Want a Second Opinion Before You Move?

We will review your current setup, tell you exactly what to request from your incumbent, and flag anything likely to be a problem — whether or not you end up working with us.