Maintenance revenue vs subscription revenue: how acquirers value legacy software

How buyers classify each software revenue line#

Buyers classify each software revenue line by how likely it is to recur without new selling effort, and that classification drives how much they will pay for it. The table below shows how acquirers commonly treat the revenue types found in legacy and hybrid software companies; individual buyers apply their own definitions, so ask each one.

Why maintenance revenue gets a closer look#

Maintenance revenue gets a closer look because it rests on an install base that no longer grows unless the company still sells new perpetual licenses. Each lost customer is gone for good, and the remaining base ages along with the product.

Buyers also look at what keeps the revenue flowing. Annual price increases can hold maintenance revenue flat while customer counts fall, which looks stable on a summary chart and fragile in a cohort table. Customers who pay maintenance but stay on versions the company no longer patches may be paying out of habit and could stop at the next budget review.

Finally, buyers weigh the cost to serve. Maintenance on legacy software often depends on a few engineers who understand an old codebase, old build tools and the database or operating system versions customers still run. If those engineers leave, the cost of keeping the promise rises.

Signals that raise or lower the credit buyers give maintenance revenue#

The signals that move maintenance revenue toward or away from recurring treatment are mostly visible in records you already hold. Prepare them before a buyer asks, because a buyer who has to dig for them will assume the worst.

Revenue recognition differences buyers will check#

Revenue recognition differences matter because buyers and their quality of earnings advisors restate revenue on a consistent basis before applying any multiple. Under ASC 606, a license to functional intellectual property such as software generally gives the customer a right to use the software in its form at the grant date, so revenue is recognized at a point in time unless specific conditions about ongoing changes are met.

That means perpetual license sales tend to arrive in lumps, while maintenance and support are generally treated as services delivered over the support period. Bundled deals, multi-year prepayments and discounts allocated across license and maintenance can blur the picture. Treatment depends on your contract terms, so confirm it with your accountants and auditors before the data room opens.

Records to prepare before the first buyer meeting#

The records to prepare before the first buyer meeting are the ones that let a buyer rebuild your revenue from source rather than from a summary. Most already exist in your billing system, CRM, license server and help desk; the work is joining them by customer so each line can be traced.

A buyer who can trace maintenance revenue to named customers, versions and renewals tends to argue less about classification. A buyer who receives only totals will apply its own, more cautious assumptions.

• 1A customer-level revenue file splitting license, maintenance, subscription, hosting and services by year.
• 2Maintenance renewal records by cohort, with the price each customer paid each year.
• 3A version census showing which release each customer runs, from license keys or support tickets.
• 4Support ticket volumes by customer and version, from Zendesk, Freshdesk or your own help desk.
• 5Contracts for multi-year maintenance, hosting and any non-standard terms.
• 6A list of engineers who can maintain each legacy component, with a named backup for each.
• 7Any end-of-support notices already issued and the customers they still affect.

Should you convert maintenance customers to subscription before a sale?#

Converting maintenance customers to subscription before a sale can raise the share of revenue buyers treat as contracted and recurring, but it costs something in the short term. Conversion programs often trade an upfront license payment for smaller recurring fees, can trigger churn among customers who were happy with the old arrangement and take engineering effort if the subscription comes with hosting.

Buyer type matters. A growth-focused buyer may prefer to see conversion under way, with early cohorts proving that customers accept it. A buyer that specializes in legacy software may prefer a stable maintenance base and its own conversion playbook. Talk to likely buyers about their preference before committing to a program that changes your numbers mid-process.

Illustrative: a lumber yard software vendor prepares for diligence#

Illustrative: a fictional vendor sells on-premises point-of-sale and inventory software to independent lumber yards and building supply dealers. Most revenue comes from annual maintenance on perpetual licenses, and a newer cloud edition has a growing base of subscribers.

Before approaching buyers, the CFO builds a renewal table by the year each customer first bought a license, separating price effects from customer losses. The support lead pulls a version census from Zendesk tickets and the license server, showing which customers run supported versions. The CTO documents who can maintain the old desktop client and its database layer.

Bidders treat maintenance from customers on supported versions as recurring, discount the remainder and ask for a retention plan for the two engineers who know the desktop client. The cloud subscriptions are valued separately, and the vendor's existing data license is reviewed as a distinct contract.

Where data licensing revenue fits in a valuation#

Data licensing revenue, such as fees for licensing support conversations, code reviews or issue histories to AI developers, typically sits outside core recurring revenue in a buyer's model. Buyers look at the term, exclusivity, renewal rights and any continuing obligations, and they may value it as a separate line rather than add it to the maintenance base.

SourceX helps companies license operational records using the SourceX five-step transaction, in which Supply, Rights, Preparation, Approval and Delivery each need the company's sign-off. Because records are licensed rather than sold, ownership stays with the company. SourceX publishes no price list; the SourceX Enterprise Data Value Framework names the drivers, among them uniqueness, recency and rights, that move value up or down. A short, non-exclusive, well-documented license is easier for any acquirer to diligence.