HubSpot Will Swap Your Idle Seat for Credits Instead of Letting You Cancel It. The Credits Expire Before Most Accounts Spend Them.
HubSpot's new seat-to-credit swap keeps ARR and seat count intact at renewal. The catch: unused credits expire monthly with zero rollover.
Seat waste is supposed to end one of two ways: the admin keeps paying for seats nobody uses, or they cut the seats at renewal and you eat the contraction. HubSpot just shipped a third option. As of October 15, 2026, a Super Admin can swap an unassigned seat for HubSpot Credits instead of removing it — no support ticket, no renewal negotiation, done in the billing portal in under a minute. On the surface it looks like the cleanest fix to seat-based churn anyone's shipped: the seat count stays the same, the invoice stays the same, and the admin gets something to show for the license they weren't using. Read the mechanics closely, though, and it's not a fix. It's a different clock on the same problem.
What HubSpot actually shipped on October 15
The feature itself is narrow and well-documented. Only a Super Admin can trigger a swap, and it only applies to unassigned seats — a seat sitting on the account with nobody logged into it. The dollar value of that seat becomes a budget you can apply toward HubSpot Credits, toward a different seat type already included in your subscription, or split between both. HubSpot's own example: a $45/month Core Professional Seat converts into $45 of spending power. Swap it entirely for credits and you get credits rounded up to the nearest pack. Put it toward two $90 Sales Seats instead and you owe the $135 difference at checkout. Mix the two — $90 toward a Service Seat, $45 toward 5,000 credits — and the math just splits the same way.
One detail matters more than the mechanics: the swap only runs one direction. HubSpot is explicit that credits can't be converted back into seats. Once that $45 seat becomes a credit balance, there's no undo button if the account later decides it actually needed the seat back. That's a meaningfully bigger commitment than it looks like from the checkout screen, and it's the first sign that this isn't really a "flexibility" feature — it's a conversion with a one-way valve.
Why this looks like a retention win on paper
Run the three outcomes for an idle seat side by side and it's obvious why a credit swap is the option procurement teams will reach for first.
| What happens to the idle seat | Effect on next invoice | Shows up as churn/contraction? | Where the risk moves |
|---|---|---|---|
| Admin removes it at renewal | ARR drops by the seat price | Yes — immediately, on your dashboard | None left — the loss is realized and visible |
| Admin swaps it for credits | ARR unchanged | No — invoice total is identical | Deferred into a monthly use-it-or-lose-it balance |
| Vendor offers a right-size renewal | ARR drops to match actual usage | Yes — but negotiated, not forced | Resolved at the table, not hidden in a billing portal |
From a vendor's seat, row two is obviously the best-looking outcome of the three — nothing moves on any metric anyone reports upward. That's precisely why it's worth being suspicious of it. A number that doesn't move isn't the same as a problem that got solved; sometimes it's a problem that got relocated somewhere your reporting doesn't reach.
The expiry mechanism is where the real exposure sits
Credits reset on a monthly cycle tied to the account's usage period, and whatever's left when that period ends is gone — not banked, not partially carried, just zeroed out. HubSpot's included-credit allotments scale by tier: Starter accounts get 500 credits a month, Professional gets 3,000, and Enterprise gets 5,000, based on the highest-edition subscription on the account.
Source: HubSpot Knowledge Base, "Understand HubSpot Credits and Billing" (2026).
That gap between tiers is the size of the budget an account now has to spend down every single month, on top of whatever it already got from a seat swap, or lose it. For a team that swapped two idle seats worth $90 into a Professional account's pool, that's not a one-time windfall — it's a recurring obligation to find $90 worth of AI-feature usage every 30 days, indefinitely, or watch the same amount quietly evaporate on a cycle nobody on the team is tracking. HubSpot even sets a default account-level spend cap of 150% of total monthly credits — an account with 3,000 included plus 5,000 purchased gets a 12,000 default ceiling — which tells you the feature is built around active, ongoing consumption, not around banking a one-time conversion.
This is the same underlying failure as the seat waste we covered in our seat-based churn piece, just wearing a different costume. Zylo's 2026 SaaS Management Index puts industry-wide license utilization at 53% — roughly half of purchased seats sit idle or under-used. A credit swap doesn't fix that ratio. It takes the dollar value that was sitting idle as an unused login and re-labels it as a balance sitting idle in a wallet that expires monthly instead of a seat sitting idle on a user list. The underlying usage gap — the thing procurement was actually trying to fix — hasn't moved at all.
Where this differs from the other credit-churn mechanisms we've covered
It's worth being precise about which credit problem this is, because "credits and churn" shows up in SaaS billing in more than one shape, and they fail in opposite directions. The credit exhaustion churn we wrote about earlier this year is a usage problem: prepaid AI credits run out mid-cycle, a feature silently stops working, and the customer churns because the product broke under them without a failed payment ever firing. The HubSpot seat swap is the mirror image — the customer isn't running out of credits too fast, they're not using enough of them, and the resulting waste is just as real but invisible in the other direction. One fails loud (a feature stops working); the other fails quiet (a budget line disappears unnoticed). Dunning tooling built to catch the first kind will never catch the second.
It's also a different mechanism from the one behind our piece on seat pricing's decline as AI agents replace human seats. That trend is about the actual headcount needing a license shrinking because an agent now does the work. This is about the dollar value of a seat that was already idle getting rerouted into a different wallet instead of removed — the headcount story and the seat-value story can both be happening on the same account at the same time, for completely different reasons, and a dashboard that only tracks seat count will conflate them.
What this means if your product runs anything like it
If you're building or evaluating a similar swap-for-credits mechanism — and expect more B2B SaaS platforms to copy this once it normalizes idle-seat absorption as a billing feature rather than a renewal conversation — the fix isn't to avoid the feature. It's to not let the expiry run silently.
- Surface utilization before the reset, not after. An admin should see "you've used 1,200 of your 5,000 credits with 6 days left" with enough runway to act, not a retroactive summary after the balance already hit zero.
- Track credit utilization as a churn-health signal, the same way you'd track seat activation. An account converting seats to credits and then burning under 20–30% of the resulting balance for two consecutive cycles is showing the exact leading indicator that seat-based churn research already established works for idle seats — it just needs a credits-shaped version of the same dashboard.
- Give the swap a cooling-off window before it's irreversible. A one-way conversion with no path back to a seat removes the one thing that made right-sizing seats work in the first place: the ability to correct course once real usage data comes in.
And if you're on the other side of this — a customer with idle seats, deciding whether to swap them — run the math before you click through checkout. Our dollar retention rate calculator will tell you what a straight seat cut is actually worth in ARR terms; compare that number to what you're likely to spend down in credits before the next reset, not what you could theoretically spend if usage went up.
None of this shows up as a cancellation yet, which is exactly the point. A credit swap that goes unused for a few cycles doesn't trigger a save flow, because nobody clicked anything that looks like leaving. It shows up eleven months later as a line item a finance team finally questions at the next full contract renewal — by which point it reads, correctly, as money paid for nothing. A cancellation flow that only asks "why are you leaving" at the moment someone clicks cancel never catches that account; one that tracks unused credit value as its own at-risk signal, the same way it already should be tracking unused seats, catches it months earlier — while there's still a renewal conversation left to have instead of just a contract to lose.
Frequently asked questions
What is HubSpot's seat-to-credit swap?+
It's a self-serve billing feature, live since October 15, 2026, that lets a Super Admin convert the dollar value of an unassigned seat into HubSpot Credits or a different seat type, without contacting their account team. A $45/month Core Professional Seat, for example, converts into $45 of budget — applied as credits, put toward a different seat, or split between the two. Leftover value rounds up to the nearest credit pack.
Do unused HubSpot Credits roll over to the next month?+
No. Per HubSpot's own documentation, credits reset monthly in line with the account's usage period, and unused credits expire at the end of each period rather than carrying forward. An account that swaps a seat for 5,000 credits and uses 1,200 of them doesn't keep the other 3,800 — it starts the next month back at its base allotment.
Can you swap HubSpot Credits back into seats?+
No, and HubSpot states this plainly: the swap only runs one direction. Once a seat's value has been converted to credits, it can't be converted back into a seat. That makes the decision closer to canceling a seat than downgrading one — there's no undo if the credits turn out to be the wrong move for that account.
Does swapping a seat for credits count as churn?+
Not on any standard metric. ARR is unchanged, the seat count on the invoice is unchanged, and no cancellation event fires. But if the account never uses enough AI-feature volume to spend down the credits it bought, it's paying the same amount for a shrinking share of realized value every month — which is exactly the setup that produces a contraction or cancellation decision at the next full renewal, just with a multi-month delay before it shows up anywhere you'd be watching.
Stop losing subscribers today
One script tag. One function call. A live cancellation flow in under 10 minutes.
Start free trial →