Legacy software
monetization.
Perpetual-to-SaaS transitions modeled customer-by-customer, not by blanket cutover date. We design the per-customer runway and operate the multi-year rollout through LevelSetter.
A blanket sunset date is a breakup letter. Every perpetual customer carries different amortization, different maintenance economics, different module usage, and different tolerance for renegotiation. Treating them all the same is what creates the churn the transition was meant to avoid.
SPP models every customer individually and segments the install base into convert-now, bridge, and hold-perpetual cohorts. Continuous monetization on subscription, across the 24-to-36 month migration, renewable. The architecture compounds with every renewal cycle.
24-month migration.
paced to renewal cycles.
not blanket cutover.
Maintenance revenue is shrinking. The SaaS line is growing but the combined business is not. The default response is a sunset date and a price list.
The install base is the work.
When the transition becomes the work.
Maintenance ratio
is slipping
Annual maintenance was the predictable income. Renewals are softening, support costs climbing. Perpetual customers are aging out or negotiating down. The ARR line is not holding up.
Cloud is cannibalizing,
not converting
New buyers take the SaaS version. Existing perpetual customers stay put. The SaaS business is growing; the combined business is not. Internal incentives pull in opposite directions.
Investors want a
cleaner ARR story
Mixed perpetual-plus-SaaS revenue multiples get a discount. The board wants the recurring-revenue narrative. You need to migrate without detonating the install base or the EBITDA.
Every customer is
a custom negotiation
You have tried moving a few customers. Each one became a six-month negotiation because the value proposition for them is “pay more for the same thing.” You need a transition offer that actually makes sense to the customer.
A blanket cutover date
is a breakup letter.
The default playbook is to announce a sunset date, quote new subscription rates, and assume customers will accept. They don’t. Each customer has a different amortization horizon on their original license, a different maintenance rate, a different set of modules they actually use, and a different tolerance for renegotiation. A blanket approach treats them all the same, and the ones who feel treated unfairly become the ones who leave.
The work is modeling the transition customer-by-customer. What does this customer’s original deal look like amortized? What’s their realized annual cost today including maintenance? What SaaS terms represent an honest trade for them? Which customers get a multi-year bridge, which convert immediately, which stay on legacy indefinitely because the economics don’t favor moving them. That’s the architecture work for a legacy monetization transition.
Model every customer
before any offer.
We model every perpetual customer individually before any offer goes out, then operate the multi-year rollout through LevelSetter.
Map every customer’s
economic history
Original license fee, amortization period, maintenance paid, modules actually used, support escalation frequency, renewal history. Each customer becomes a row with real numbers. That’s the only honest starting point for an offer.
Segment by transition
economics, not by size
Some customers are ready to convert immediately (fully amortized, high-use, growing). Some need a 24-month bridge (mid-amortization, stable use). Some never convert (low-use, declining business, legacy contract is cheaper than SaaS). We build the segments from the data.
Design from each customer’s
realized price
Every perpetual customer is paying a different effective rate after years of volume discounts, carry-forward terms, partner-channel pricing, and renewal-history adjustments. Transition offers that start from list price detonate legacy revenue. We read the price differential customer by customer and design a migration that holds the economic baseline. The lift only happens where the customer is genuinely buying new capability.
Operate the multi-year
rollout continuously
Transitions are not a project, they’re a 24-to-36-month operating program. LevelSetter holds per-customer transition state, runs optimization on the price differentials to find the best transition path per customer, drives renewal-cycle conversations, flags drift from plan, and keeps finance aligned as the revenue mix shifts quarter by quarter.
Five questions before
you sign anything.
Every customer,
or just the top 20?
The top 20 customers generate the ARR narrative, but the long tail generates the churn risk. A firm that only models the top accounts leaves you with a revenue plan that looks great and a retention disaster waiting. Insist on full install-base modeling.
Non-convertible as a
segment, not a failure
Some perpetual customers will never convert, and that’s fine if the economics work for both sides. Firms that treat every non-conversion as a lost customer end up forcing bad offers through, which creates the churn they were trying to prevent.
Bridge offer,
not two end-points
Perpetual and SaaS are the boundary cases. Most customers need something in the middle for 18-24 months. Firms that only think in binary terms ship offers that feel coercive. Ask how they handle the bridge.
Operating layer for
the multi-year rollout
Transitions unfold over 2-3 years. State, pacing, and finance impact all need continuous management. A firm that hands you a transition plan in a deck is leaving the real work undone. We hand off LevelSetter with every customer’s state live.
Can they defend the
EBITDA through it?
Perpetual revenue often comes at 80%+ gross margin. SaaS replaces it at lower margin in the early years. If the transition plan does not include an explicit EBITDA defense strategy, you’ll show investors improving ARR and collapsing earnings at the same time. We model both.
A transition that
kept the base.
An on-premise software company engaged SPP for a perpetual-to-SaaS transition. The legacy base converted in 18 months. Enterprise retention held above 97%. The EBITDA trough was smaller than the board had modeled, defended through upfront payment structures and multi-year incentive offers tuned to each customer’s price differential.
Frequently asked questions
Transition the install base without breaking the relationships that built the business.
If maintenance is shrinking, the cloud product is cannibalizing instead of converting, or investors are pressing for a cleaner ARR story, that’s the conversation. Renewable. Each renewal is one we earn.