Selling a business with outdated technology: what buyers discount and what to keep

Do outdated systems hurt the sale price of a business?

Outdated systems usually lower what buyers pay only to the extent they add cost, risk or integration work the buyer must absorb. Buyers price that work as a discount, a longer earnout, a special indemnity or a request for a transition period. Old systems that still work and hold clean history are often a smaller problem than owners fear.

The practical advice for most owners is to stabilize, document and export, not to launch a major migration mid-process. The older archives may also hold something an upgrade would throw away: multi-year records that AI developers license.

How do buyers price legacy systems?

Buyers look at four things and put a rough cost on each. The table shows what they ask and what you can answer without spending money.

A buyer with its own platform will plan to migrate you regardless, so your system's age often matters less to them than whether the data can be exported cleanly. A buyer without one cares more about continuity. Neither reads an upgrade started halfway through diligence as a plus.

Should you upgrade your ERP before selling?

Usually no, unless the system is failing. A migration started during a process creates parallel books, retraining and cutover risk, and it can make trailing financials harder to tie out. Buyers' quality-of-earnings teams then spend time on the migration instead of the business.

Use this rule of thumb:

• If the old system works and finance can close the books on schedule, leave it alone and document it.
• If a vendor is ending support within the next year, price the replacement as a known item and share the quote with buyers.
• If the migration is already underway, finish a stable phase before launch of the process, or pause and disclose.
• If a small fix removes a visible blocker, such as a broken export or unsupported plug-in, do that fix.

What is lost if old systems are decommissioned?

Retired systems often hold the longest histories a company has: closed tickets, old CRM opportunities, archived email, project files and approval trails. Once the subscription ends or the tenant is deleted, those records may be gone or difficult to recover. Buyers rarely ask for them, so no one decides to keep them.

That is a loss for another reason. AI developers building agents need records of how real work was done and what the outcome was. Several years of connected history, including archived systems, makes a company a stronger candidate for a data license. A company keeps ownership, and the license is a one-time payment for an agreed dataset, typically exclusive for AI training for an agreed term. Nothing is binding until the company agrees price and terms and signs.

This does not mean old technology is valuable in itself. It means the contents of an old system may be, if rights are clear and someone can still export them.

A short pre-sale routine for old systems

1. List every system that holds business records, including retired ones, with its owner and the years it covers.
2. Confirm that someone can still log in as an administrator and run a full export for each.
3. Keep subscriptions or read-only access alive for archive systems until the sale closes, and ask counsel about the handover terms.
4. Record what personal data of the owner sits in the systems, and plan its removal. The guide on removing owner personal data from company systems before a sale covers this.
5. Add the list to the data room and to the closing handover, using the IT handover checklist.

This routine costs time, not capital, and it serves both the sale and any later licensing conversation.

What to say to a buyer who raises the systems

Answer with facts and a plan, not a defense. Buyers respond to specifics: the system map, the support dates, who administers each tool, and the cost estimate you already have.

Do not promise a migration the company has not scoped, and do not agree a price reduction before you know what the buyer's own platform plan costs. Your advisor will usually handle that negotiation, and the seller should review any term that makes the seller responsible for system replacement after closing.

Illustrative example

Illustrative: a fictional 120-person distribution company runs a 15-year-old ERP, a retired helpdesk tool still readable by one admin, and current email and chat. The owner plans to sell in 12 months. Instead of migrating, the owner has IT write a one-page system map, run and store full exports from the helpdesk, and keep the ERP vendor contract through closing. A buyer sees a documented, supportable stack. The owner also has a clear inventory if the company later explores a data license. No price effect is promised, and the outcome depends on the buyer.

How does this fit buyers and advisors?

Your advisor decides the sale process; see the notes on where AI data buyers fit in an M&A buyer list. Sector examples show the same pattern in different industries, such as selling a machine shop and selling a translation or localization company, where older job-management and project systems hold much of the history.

Who this does not apply to

A data license is not a fit if:

• The company has fewer than 50 full-time employees at peak (contractors excluded).
• The records mainly belong to clients who have not agreed.
• The archives were deleted or nobody can export them.
• The data is mostly consumer personal data or protected health information without a lawful basis.

The company fit checker gives a preliminary, non-binding screen, and who qualifies lists the baseline. Whether you license before, during or after a sale is a decision for you and your advisors.

Next step

If the company has years of records spread across current and retired systems, run the fit checker above. Advisors and other connectors can register as a partner to introduce a company, and owners can apply directly at sourcex.si/apply.