How to choose an MSP after an acquisition without losing years of records

When choosing an MSP after an acquisition, pick the provider that will take over admin access, confirm backups and archived mailboxes, and run a documented handover from the old MSP before changing anything else. Ask every candidate in writing how they handle retention, former employees' data, offboarding and data return, then compare the answers side by side.

The short answer: choose the MSP that will run the handover

After an acquisition, the most important job for a new managed service provider (MSP) is not the help desk. It is taking over admin access, backups and archives from the outgoing provider without losing years of email and files. Choose the candidate that answers handover questions in writing, puts every admin role and subscription in the company's name, and proves a restore works before the old MSP is gone.

Service catalogs look alike from one MSP to the next. Handover discipline does not, and it decides whether the company still has its history a year after closing.

What does a new MSP inherit after a deal?

A new provider takes over whatever the seller and the old MSP left behind, which often includes:

  • Admin roles for email, files, firewalls and business apps, sometimes held inside the old MSP's own partner accounts.
  • Backup jobs and cloud backup subscriptions licensed to the old MSP rather than to the company.
  • Monitoring agents and security tools that stop working, or are pulled, when the old contract ends.
  • An old file server, NAS or retired accounting server holding the only copy of the early years.
  • Former employees' mailboxes, which may be retained, archived or quietly deleted to save license cost.
  • Documentation such as passwords, network diagrams and vendor contacts, stored in the old MSP's tools.

What to have ready before you shortlist

  • The current MSP contract: termination notice, any data-return clause, and offboarding fees.
  • Admin access status for each core system; if the company does not yet hold top-level admin rights, start with getting admin rights back from a seller or old provider.
  • A system list: email and files, accounting or ERP, CRM, field service or industry software, phones and backups.
  • Records that sit outside IT's view, such as a former bookkeeper's files; getting records back from a former bookkeeper covers that track.
  • Compliance obligations. The FTC Safeguards Rule reaches many non-bank businesses, including mortgage brokers, finance companies, collection agencies and tax preparation firms, according to the FTC's Safeguards Rule guide. The rule text requires covered firms to keep a written information security program with elements such as a designated Qualified Individual, encryption of customer information and a written incident response plan, so a covered company needs an MSP that can support that program.
  • A budget and the earliest date the old contract can end.

This is general information, not legal, tax or financial advice. Confirm with your own counsel whether the Safeguards Rule or other rules apply to the company you bought.

The handover-first scorecard: questions for every candidate

Send the same questions to each MSP and score the written answers.

QuestionA strong answerA red flag
Whose name will admin accounts and subscriptions be in?The company's, with named company admins and delegated MSP accessOnly the MSP's partner account
What do you back up, and how do you prove restores?Servers, endpoints and cloud email and files, with scheduled restore tests and reportsThe platform vendor handles that
What happens to former employees' mailboxes and files?Retained or archived under a written policy the owner approvesDeleted by default to save licenses
How will you take over from the outgoing MSP?A written plan covering credentials, documentation, agent removal and backup transferWe will sort it out as we go
What happens to old servers and storage?Image or export, verify, then decommission with owner sign-offWipe the hardware to tidy up
Who owns the documentation you create?The company, exportable at any timeLocked in the MSP's tools
What do you return if we end the contract?All data, credentials and documentation within a defined period at a stated costNo data-return clause
Have you separated tenants or merged companies after a deal?Can walk through the steps and pitfallsOnly greenfield onboarding
Who can reach our systems?Named staff, with any subcontractors disclosedAn unnamed offshore desk with admin rights
What security baseline do you set in the first month?Multi-factor sign-in everywhere, separate admin accounts, loggingSold as optional add-ons

From shortlist to completed handover, step by step

  1. Freeze deletions before anything moves. Ask the old MSP in writing to pause deletions, license reductions and retention changes until the handover is signed off.
  2. Sign with the new MSP, data-return clause included. Price the handover as a defined project rather than leaving it inside a monthly fee.
  3. Run discovery in the first weeks. The new MSP documents every system, admin role, backup and archive and checks it against your system list.
  4. Take over admin rights. Create company-controlled admin accounts first; reduce the old MSP's accounts but keep them until verification.
  5. Prove the backups. Get new backups running, then restore one old mailbox and one old file share and keep the report.
  6. Preserve the archives. Export or archive former employees' mailboxes and old servers under a written retention decision the owner signs.
  7. Offboard the old MSP. Remove its agents and accounts, collect the documentation, and get written confirmation of any copies it still holds under the contract.
  8. Review after thirty days. Walk the scorecard again and confirm every account, subscription and document is in the company's name.

Common mistakes when switching MSPs after a deal

MistakeWhy it hurtsFix
Ending the old contract before the handoverBackups and documentation leave with the old providerOverlap the contracts until restore tests pass
Choosing on hourly rate aloneLow-cost plans often exclude backup, archives and projectsScore the handover answers, then compare price
Deleting former employees' mailboxes to cut license costYears of customer and project history are goneArchive under a signed retention decision
Accepting MSP-owned admin accountsThe company cannot act without the providerCompany-named admins with delegated MSP access
Wiping the old serverEarly files and accounting data are lostImage, export and verify first

Illustrative example: an elevator contractor's switch

Illustrative and fictional: a family-office-backed buyer acquires an 85-person commercial elevator service company. The seller's MSP holds the only admin login for email and the field service software, backups are licensed to the MSP, and eleven years of maintenance tickets sit on a server in the shop.

The buyer picks the second-cheapest of three bidders because it is the only one that puts a handover plan, a restore test and a data-return clause in writing. The old server is imaged before it is retired. Buyers backed by family capital will recognize the pattern from family office direct investment risks, and elevator service company maintenance histories explains why those tickets matter.

How a new MSP can spot a data licensing opportunity

An MSP that has just mapped every system knows how many there are, how far back each one goes and whether exports still work. Companies with strong records usually run many systems, often 10-15 or more, across email, chat, CRM, finance, support and operations, with years of history and archives kept intact.

That makes the MSP a natural person to mention SourceX to the owner when the company looks like a fit: it is based in the US, has had 50+ full-time employees at peak (contractors excluded), can show a multi-year record of operations, controls the rights to what it holds, and has an owner or executive able to sign. Who qualifies has the details. The MSP's role ends at the introduction. It never exports, uploads or describes confidential records; SourceX qualifies the company, the company builds a data inventory, and nothing is delivered without a signed agreement and the company's authorization.

MSPs that register as partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. It is never deducted from the client's payment, and the MSP should disclose it to the client. The network opportunity finder helps an MSP think through which clients to raise it with.

Next step

Send the scorecard to your shortlist this week and overlap the old and new contracts until the restore test passes. If you are an MSP or adviser who sees qualifying companies during handovers, register as a partner. An owner who prefers to go first can apply at sourcex.si/apply.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
  4. Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

Should I keep the seller's MSP after closing?

Keep them through the handover even if you plan to switch, because they hold the credentials, documentation and backup history. Decide on the long-term provider using the same written questions you send to new candidates. Some incumbents perform well once admin roles move into the company's name; others treat access as leverage, which is a strong reason to replace them carefully.

How much notice does an outgoing MSP need?

Whatever the current contract says, so read the termination and data-return clauses before announcing a change. Notice periods, offboarding fees and the format for returning data vary widely between providers. Give notice only after the new MSP has completed discovery and the company holds its own admin accounts, so the outgoing provider cannot leave with the only working access.

Who should own the admin accounts and the backup subscription?

The company should. Admin accounts should be named company users with multi-factor sign-in, and the MSP should work through delegated access that can be removed. Backup subscriptions should be billed to and held by the company, so backups and their history survive any change of provider. Ask for this in the contract, not as a verbal promise.

Do Microsoft 365 or Google Workspace keep our data without a separate backup?

They keep data according to the retention settings and licenses in place, and those settings can be changed or lapse. Do not assume old mail or deleted files will still be there. Ask each MSP what it backs up beyond the platform's own retention, how long backups are kept, and to show a restore of an old mailbox before you rely on it.

Can our new MSP tell whether our records could be licensed?

It can give an early read, because it sees how many systems the company runs, how far back they go and whether exports still work. It cannot decide fit or rights. SourceX qualifies the company on size, history, data breadth and rights, and the company completes its own data inventory. The MSP never exports or shares records as part of an introduction.

Free resources

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment