- Asset sale or stock sale decides what the buyer takes over: chosen assets and contracts, or the whole company with its history.
- Buyers look at recurring revenue, client concentration, contract terms, documentation and owner dependency.
- Read every client agreement for assignment and change-of-control clauses before you talk to buyers.
- Client environments, logs and tickets stay under the client's control. Plan the handover of access, not just the revenue.
How is an MSP sold: asset sale or stock sale?
A managed service provider (MSP) is a company that runs IT for its clients under contract. CISA and its partner agencies define MSPs as "entities that deliver, operate, or manage ICT services and functions for their customers via a contractual arrangement, such as a service level agreement" (CISA). That definition matters in a sale: most of what a buyer pays for is a set of contracts.
There are two basic deal shapes. In an asset sale, "a seller transfers to a buyer a portion or all of the assets of an entity" (Wex): the client contracts, tools, staff and brand the buyer picks. In a stock sale, "a seller transfers stock of a corporation to a buyer" (Wex): the company changes owner, and its contracts, history and liabilities stay with it.
Tax follows the shape. For an asset sale, the IRS says "the sale of a trade or business for a lump sum is considered a sale of each individual asset rather than of a single asset", and "both the buyer and seller of a business must use the residual method to allocate the consideration to each business asset transferred" (IRS).
| Asset sale | Stock sale | |
|---|---|---|
| What the buyer takes | Chosen contracts, tools, staff, brand, goodwill | The whole company, including its past |
| Client contracts | Must be assigned to the buyer one by one | Stay with the same company; change-of-control clauses may still apply |
| Old liabilities | Mostly stay with the seller unless taken on | Go with the company; covered by warranties and indemnities |
| Tax | Price split across assets (residual method) | Usually treated as a sale of shares |
What do buyers look at when an MSP is for sale?
Recurring revenue comes first. A law firm that works with MSPs writes that "recurring revenue is typically the first thing buyers look at, and they want to see at least 70% of income flowing from managed service agreements with auto-renewing contracts" (Bronston Legal).
Client concentration comes next: how much revenue depends on the largest clients. The same firm says "no single client should exceed 20% of revenue" (Bronston Legal). "They want documented SOPs and a standardized tech stack" (Bronston Legal). SOPs are standard operating procedures: the written way the team does each job.
| What buyers check | What they want to see | What lowers interest |
|---|---|---|
| Recurring revenue | Most income from managed service agreements that renew | Project, hardware and break-fix income |
| Client concentration | No single client a large share of revenue | One or two clients carrying the business |
| Contracts | Signed, current, assignable agreements | Expired terms, unsigned changes, consent-to-assign clauses |
| Documentation | Runbooks, client network documentation, procedures | Knowledge held by one or two engineers |
| Owner dependency | Named account owners and a team that runs without the founder | Founder as lead engineer and main client contact |
How do you prepare an MSP for sale?
Start early. "Ideally, preparation begins one to three years before you plan to sell" (Bronston Legal).
Check your vendor agreements too, not only client agreements. An M&A adviser (a firm that runs company sales for owners) tells sellers to "request the specific transfer and assignment provisions from each material vendor agreement" (Glacier Lake Partners).
- A client list with monthly recurring revenue, contract start and end dates, renewal terms and any consent-to-assign or change-of-control clause.
- Signed copies of every client agreement and amendment. Fix any client on an expired term.
- Vendor and license list: which transfer with the company, which need consent, which are tied to a person.
- Security clean-up: remove old staff accounts, enforce MFA on every account that reaches a client, record past incidents honestly.
- A transition plan: who owns each client relationship after closing, and how long you stay on.
What happens to client contracts and client data when an MSP is sold?
General information, not legal advice. Contracts first: "many standard service agreements contain language that either prohibits assignment without client consent or includes a change-of-control provision that gives the client the right to terminate if the business changes hands" (Bronston Legal). In an asset sale each contract must be assigned to the buyer; in a stock sale the contract stays put, but a change-of-control clause can still let the client leave. Due diligence also tends to find "clients operating month-to-month after the original term expired" (Bronston Legal).
Data is different from revenue. Client guidance from the Canadian Centre for Cyber Security tells MSP clients: "Your organization is the data owner and is legally responsible for data security." It tells them to ask "who retains legal ownership of the data" in several cases, including "if the service provider is acquired by an organization that does not evaluate security or that raises concerns from the perspective of supply chain integrity?" (Canadian Centre for Cyber Security).
Access is the risk. MSP work "usually require[s] both trusted network connectivity and privileged access to and from customer systems", and CISA warns that "disabling MSP accounts can be overlooked when a contract terminates" (CISA). A sale plan should say, client by client, whose accounts stay, whose are removed and when.
| Item | Who usually controls it | What happens in a sale |
|---|---|---|
| Client contracts | The MSP and the client, under the agreement | Assigned (asset sale) or kept (stock sale), subject to consent and change-of-control clauses |
| Client networks, files and backups | The client | Stay with the client; the buyer gets access only as the client allows |
| Tickets and logs about client systems | Shared: held by the MSP, about the client | Move with the business for service, under the client agreement |
| The MSP's own systems, procedures and tools | The MSP | Sold with the business |
Worked example: preparing a small MSP for buyers
This is an illustration written for this page, not a real company. Northfield IT is a fictional MSP with 140 clients and 14 staff. It bills $118,000 a month, of which $92,000 (78%) comes from managed service agreements. Its largest client, a law firm, pays $21,000 a month: 23% of recurring revenue.
The owner reads all 140 client agreements. 31 of them (22%) say the contract cannot be assigned without the client's written consent, including the largest one. 12 clients are on terms that expired more than a year ago. Runbooks exist for the backup and patching work but not for the law firm's custom systems, which only the owner understands.
| Finding | Action over the next 18 months | Result shown to buyers |
|---|---|---|
| Largest client at 23% of recurring revenue | Sign two new clients at $4,500 a month each | Largest client at 21% of $101,000 recurring |
| 31 contracts need consent to assign | Move clients to a new agreement at renewal with a standard assignment clause | Consent list shrinks to the clients who refused, shown openly |
| 12 clients on expired terms | Re-sign on current agreements | Every client on a signed, current term |
| Law firm systems known only to the owner | Owner and a senior engineer write runbooks and network documentation | Named engineer owns the account |
The example sets no price. It shows the same business before and after preparation.
Common mistakes when selling an MSP
An M&A adviser writes that "the most common post-close failure mode is customer attrition driven by relationship disruption, not operational failure" (Glacier Lake Partners). Most of the mistakes below lead there.
- Finding consent-to-assign clauses during the buyer's due diligence instead of a year earlier.
- Treating client data, backups and logs as assets of the MSP that can be sold or reused.
- Leaving old staff and vendor accounts active in client environments through the sale.
- Owner holding every key relationship and every unusual system, with no written runbooks.
Which MSP records matter in a sale?
Beyond contracts and financials, an MSP holds years of operating records: the ticket history in its PSA (professional services automation) tool, alerts from its RMM (remote monitoring and management) tool, runbooks, configuration backups and change notes. If you move or archive a ticket system, the Zendesk export guide shows how to get the full history out.
CISA expects MSPs to "log both internal and customer network activity, as appropriate and contractually agreed upon" (CISA). That split is the useful one for a seller: records about the MSP's own internal systems are the MSP's; records about client systems are held under each client agreement. For the wider picture of how IT service firms use their records, see IT services and MSPs.
Are an MSP's tickets, runbooks and config archives also a data asset?
Sometimes, and in part. AI data buyers have asked Origin for the records of companies that run and defend their own infrastructure: incidents joined to the ticket, chat thread, config diff and outcome that fixed them; configuration history going back years; ordered logs of what happened and what was done; and the runbooks, on-call records and postmortems of the same period. The company must own the records, and they must cover its own infrastructure, not a client's unless the client has agreed.
For an MSP that line runs through the middle of its archive. Most ticket history, runbooks and configuration backups describe client environments, so each client's agreement decides whether any of it can be used, and in practice that means the client's written agreement. The MSP's own internal infrastructure records (its own network, its own tools, its own incidents and fixes) are its own. See support tickets as AI training data and the hub for infrastructure and incident records.
Origin is an independent data partner. The company decides what is shared and signs any license itself, and a buyer may pay Origin when a deal closes.
- Client environments: anything about a client's systems stays out unless that client has agreed in writing.
- Secrets: passwords, keys and tokens in tickets, runbooks and config backups come out first, and are rotated (remove secrets from git history).
- Personal data: names, emails and phone numbers of client staff and your own staff are removed or replaced with consistent pseudonyms.
- Sale terms: if a sale is under way, the purchase agreement says who owns the records after closing.
Does your company hold records like these? See what your data is worth.
Common questions
How do I sell my MSP?
Prepare one to three years ahead: separate recurring from one-off revenue, re-sign clients on current agreements, check assignment and change-of-control clauses, document runbooks and hand client relationships to named staff. Then choose an M&A adviser or approach buyers directly, sign confidentiality agreements, agree terms in a letter of intent, and complete due diligence and the client transition.
What is the difference between an asset sale and a stock sale of an MSP?
In an asset sale the buyer takes chosen assets, such as client contracts, tools and staff, and each contract must be assigned. In a stock sale the buyer takes the whole company, so contracts and past liabilities stay with it. Tax also differs: an asset sale is treated as a sale of each asset, with the price allocated by the residual method.
What do buyers look for when buying an MSP?
Buyers look first at recurring revenue from managed service agreements, then at client concentration, signed and current contracts that can transfer, documented procedures, a standard technology stack and how much the business depends on the owner. Security practice matters too: MFA on client access, removal of old accounts, incident history and cyber insurance in force.
Do MSP client contracts transfer to the buyer automatically?
Not always. In an asset sale each contract must be assigned, and many MSP agreements forbid assignment without the client's consent. In a stock sale the contract stays with the same company, but a change-of-control clause can still give the client the right to end it. Read every agreement for these clauses before the sale starts.
What happens to client data when an MSP is sold?
Client data stays under the client's control. Managed-service guidance tells clients they are the data owner and should ask who keeps ownership if their provider is acquired. The buyer gets access only as each client agreement allows, and the sale plan should list which accounts in each client environment stay and which are disabled.
How long does it take to prepare an MSP for sale?
One to three years is a common recommendation. That allows time to move clients onto current, assignable agreements, reduce dependence on the largest clients, write down how unusual systems work, hand relationships to staff and clean up access. A rushed sale tends to surface these issues during the buyer's due diligence, when they are harder to fix.
Can an MSP use its ticket history and runbooks outside the sale?
Only in part. Most ticket history, runbooks and configuration backups describe client environments, so each client's agreement decides, and client records stay out unless the client agrees in writing. Records about the MSP's own internal systems, tools and incidents belong to the MSP, after secrets and personal data are removed.
Sources and further reading
- CISA and partners: Protecting Against Cyber Threats to Managed Service Providers and their Customers (AA22-131A)
- Canadian Centre for Cyber Security: Cyber security considerations for consumers of managed services (ITSM.50.030)
- Cornell Legal Information Institute (Wex): asset purchase agreement
- Cornell Legal Information Institute (Wex): stock purchase agreement
- IRS: Sale of a business
- Bronston Legal: How much is your MSP worth? What buyers find when they look
- Glacier Lake Partners: Selling an MSP or IT managed services business
