MSP client acquired: why to introduce the owner before integration

What should an MSP do when a client is being acquired?

Introduce the current owner to a SourceX assessment before the acquirer's integration plan retires the client's systems. Once cutover happens, mailboxes get merged, old tenants shut down and your managed contract may end, so the window to preserve and assess years of records is usually before the integration plan locks, not after.

This playbook is written for MSP owners, account managers and vCIOs who learn about a deal from a client: a quiet note in a QBR, a request to "pause new projects", or a sudden question about contract assignment.

Why does an acquisition put the records at risk?

Acquirers consolidate. The target's email, chat, ticketing, ERP and file shares are mapped to the buyer's equivalents, migrated selectively and then switched off. Anything not mapped gets archived at best and deleted at worst. The people who knew what each system held often leave during the same period.

For the MSP, the same event may end the relationship. The buyer may have its own provider, a master agreement may not assign, or the work may shrink to migration support. That is also why you hold a useful role right now: you know which systems exist, how old they are and who can export them.

Whether a company that has been acquired can still qualify depends on the records. The program accepts companies that are still operating, acquired or wound down, as long as the data still exists, the rights to license it are clear, and the company met 50+ full-time employees at peak (contractors excluded).

Timeline: when to act around an acquisition

Deal timelines vary, so treat the stages as a pattern rather than a schedule.

Who is the right person to talk to?

Pick the person who can actually authorize a license. That is the owner, CEO, CFO or another authorized representative, not the IT contact alone.

• Before closing: the selling owner or CEO, who still controls the company.
• After closing: the acquirer's executive responsible for the integration, or the selling company's former owner if the agreement leaves rights with them.
• Where counsel is involved: the deal attorney, who knows who holds the rights to historical records.

If you are unsure who holds the data rights after the transaction, ask in a neutral way and let counsel answer. This is general information, not legal, tax or financial advice; the purchase agreement, not the MSP, decides.

The 3-question trigger test

Before you raise anything, answer three questions.

• Do records exist? Can the client's email, chat, ticketing, finance or project history from several years still be exported?
• Who owns them now? Does the client, the buyer or a third party hold the right to license them after closing?
• What is the deadline? When will the systems be retired, and is that date before the deal is signed or after?

Three clear answers make the conversation worth having. If the first is no, stop. If the second is unclear, send the question to counsel.

How the introduction works without touching client data

1. You tell the right executive that licensing operational records is an option and that it is time-sensitive.
2. They apply at sourcex.si/apply using your referral link, or you submit the company through the referral form after you register as a partner.
3. SourceX qualifies size, history, data breadth and rights.
4. The company completes a data inventory of its systems and what can be exported.
5. Price and terms are agreed, buyers review, and the company signs only if it chooses to.
6. Delivery follows an executed agreement, with redaction rules agreed first.

You never export, upload or describe the records. Your job is to make the introduction and keep systems alive long enough for the company to decide.

What to say

Do not mention anything the owner has not told you in confidence. If the deal is private, wait for the owner to raise it.

What to preserve during integration

Preserve the capability to export, not the contents on your own machines.

Vendor-specific limits vary, so check how each platform handles exports and read SaaS contract data export rights for the contract side. If your clients run Google Workspace or Acumatica, see the pages for Google Workspace partners and Acumatica partners.

How does the partner reward work for an MSP?

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 becomes payable only after the buyer pays and SourceX receives its fee; a lead, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. The reward is a share of SourceX's fee and is never deducted from what the company receives. Read the program terms and compare roles in channel partner vs referral partner.

When not to raise it

• The deal is confidential and the owner has not brought it up.
• A court, trustee or assignee controls the assets and has not been involved.
• The data mainly belongs to the client's clients.
• The company had fewer people than the baseline even at its peak.
• Systems were already deleted before you knew about the deal.

Next step

List the clients likely to be acquired or merged in the next year using the network opportunity finder, and check each against the who qualifies page. Then register as a partner. The managed service provider overview and the guide to additional revenue streams for MSPs cover the wider picture.