The renewal call I keep having
It goes like this. The renewal quote lands in somebody's inbox. The seat count is the same as last year — it is always the same as last year — and the owner or the finance person does the math in their head and goes quiet for a second.
Then they say the thing I have heard more times than I can count: "Half these people barely touch the system. Just downgrade the ones nobody uses and cut the bill."
And I have to ask the question that decides everything: "Which kind do you own — subscription, or perpetual?"
Because there is no downgrade lever on either side of that fork. Not "it's complicated." Not "your partner won't like it." You cannot downgrade an SAP Business One license you already own. There is no form, no portal button, and no partner trick that turns a license into a cheaper type and refunds you the difference.
What you can do is completely different depending on the answer — and this is where the real money hides.
Why the downgrade idea sticks around
Because in the rest of your software life, changing your mind works. Cloud subscriptions let you drop a tier, cut seats, and watch the bill shrink. That is the mental model everybody brings to ERP, and it is a reasonable one. It just doesn't survive contact with how these licenses were bought.
Even on subscription, changes land at renewal — not mid-term, not the day you ask. And on perpetual there is no tier to slide at all. You didn't rent those licenses. You bought them.
Owners sit on ghost seats for years partly because the one move they believe in doesn't exist, and nobody told them which moves do. Here they are.
What the waste actually looks like
It is almost never a dramatic story. It is housekeeping that never happened.
There is the seat still assigned to the person who left the company two springs ago. Nobody removed it, nobody reused it, and it has ridden along on every count since.
There is the role-changer. She ran purchasing when you bought her seat. Now she runs the floor and touches the system for five minutes a day — while a new purchasing hire starts next month, and the reflex will be to buy one more seat.
There are the "just in case" seats from the growth push that stalled. You bought for the team you planned to have. The plan changed. The seats didn't.
None of these need a downgrade. They need a list, a login check, and thirty honest minutes.
The levers that actually exist
1. Audit the usage first — whichever kind you own. Make a login review a habit, not a rescue: every assigned seat, who it belongs to, and whether that person has actually been logging in over a real stretch of time. This is not about catching employees — nobody is in trouble for not using software. It is a budget tool. Every lever below runs on what this audit tells you.
2. Reassign before you buy. When somebody new needs access, the first question should be "whose seat is sitting idle?" — not "how many more do we need?" A departed employee's seat, a role-changer's leftover seat: that is inventory you already paid for. Shops that keep a simple list of free seats stop buying duplicates. Shops that don't, buy the same capacity twice and call it growth.
3. Know which side of the fork you're on. If you are on subscription, renewal is a genuine decision point: the count resets there. Walk in with the audit and renew at the number your team actually uses — not last year's number out of habit. If you are on perpetual, renewal resets nothing. You own those licenses, and maintenance runs on all of them. SAP's own license guide says it flatly: returning licenses does not reduce the number of contracted users, and the number of contracted users is the basis for the maintenance contract. Shelving a perpetual seat saves you exactly zero. That is why levers 2 and 4 are the whole game for perpetual shops.
4. Buy the right type for the next person. License type is a purchase decision, and it is the one place type really saves you money. When you buy a seat for a new user, match the type to the work that person will actually do all day — the person entering orders and checking stock has different needs from the person running financials and administering the system. On subscription you can revisit that choice at renewal. On perpetual it is forever, so get it right the first time.
Make it a ritual, not a rescue
The companies that stop bleeding on licenses treat this like the month-end close: boring, scheduled, and short. Once a year, put the user report on a screen with your operations lead and your finance person. Thirty minutes. Four questions. Who left? Who changed jobs? Who actually logs in? Who are we about to hire?
If you're subscription, that meeting sets your renewal number. If you're perpetual, it catches the free seats before you buy duplicates and sharpens every purchase decision from here on. Either way, run it every year and the ghost seats never accumulate. Skip it for five years and you get the renewal call I described at the top — a quote full of people who don't work there anymore, and an owner asking for a lever that doesn't exist.
The bottom line
You cannot downgrade your way out of license waste. Nobody can.
If you're subscription, the audit is your renewal weapon — use it to renew at the count you actually run. If you're perpetual, your seats are yours and the maintenance meter runs on all of them, so your money is saved by reassigning what you own and buying right the first time.
Either way, the seats nobody logs into are still worth hunting down. Just hunt them with levers that exist.
Frequently asked questions
Can I downgrade a Professional User license to a cheaper license to cut costs?
No. A license you already bought stays the type it is — there is no downgrade path that converts it to a cheaper tier or refunds the difference, on subscription or perpetual. Where license type saves you money is at purchase time: when you buy a seat for a new user, match the type to the work that person will actually do every day.
We own perpetual licenses. Can we hand back the unused ones and cut our maintenance bill?
No. On perpetual, you own the licenses, and maintenance is based on the number of contracted users — whether they log in or not. SAP's license guide is explicit that returning licenses does not reduce the number of contracted users, and that contracted count is the basis for the maintenance contract. Your levers are different: reassign the idle seats to people who need them instead of buying more, and buy the right count and type on your next purchase.
We are on subscription. When can we reduce our seat count?
At renewal. That is when subscription counts can be right-sized. Go in with a usage audit — who actually logs in, whose seat is idle — and renew at the count your team really uses instead of letting last year's number roll forward by default.
How do I find out which seats we are wasting?
Run a usage audit. List every assigned seat, check who has actually been logging in over a meaningful stretch of time, and flag the seats assigned to people who left, changed roles, or rarely touch the system. Thirty minutes with your operations lead and your finance person will show you exactly where the waste sits.
Somebody left the company. What should happen to their seat?
Reassign it. When the next person needs access, give them the departed user's seat instead of buying an additional one. This matters most on perpetual, where every seat you own carries maintenance either way — an idle owned seat given to a new hire is money you did not spend twice.
