GoHighLevel SaaS Mode Plan Upgrades & Downgrades (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 27 September 2026 · 9 min read
Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend. Full disclosure.
GoHighLevel SaaS Mode plan upgrades look simple from the sub-account settings screen — pick a new plan, confirm, done. Underneath, HighLevel is rewriting a Stripe subscription, re-evaluating which features and apps the sub-account can see, and in some configurations doing nothing to the invoice until the next billing date.
Downgrades are the messier half. A HighLevel SaaS plan downgrade is usually scheduled rather than instant, and several things a client stops paying for do not switch themselves off. This guide walks through the mechanics on both sides — HighLevel's side and Stripe's — so you can design a plan ladder and an SOP that don't leave you carrying costs a client has already stopped paying for.
Quick Facts
| SaaS Mode requires | HighLevel's Agency Pro plan, US$497/month (HighLevel Support Portal, Sept 2026) |
| Agency plan tiers | Starter $97/mo, Unlimited $297/mo, Agency Pro $497/mo (gohighlevel.com pricing page, Sept 2026) |
| Stripe's default proration | create_prorations — applies automatically unless you set it to none or always_invoice (Stripe Docs, 2026) |
| Downgrade timing | Scheduled for the next billing cycle by default; client keeps current features until then (HighLevel Support Portal, Sept 2026) |
| SaaS V2 proration | Not supported for tier or interval changes on HighLevel-billed subscriptions (HighLevel Support Portal, Sept 2026) |
| Failed agency payment window | 21 days of continued access, retries for up to 30 days (HighLevel Support Portal, Sept 2026) |
| GST on rebilled SaaS in Australia | 10% standard rate applies to sales made to Australian customers (ATO, 2026) |
What actually happens when a SaaS Mode client changes plans
A plan change in HighLevel's SaaS Configurator touches two systems at once: the sub-account's entitlements inside HighLevel, and the underlying subscription that bills the client. A plan change updates the "subscription tier, billing, and feature access," with plan-based settings deciding which features and apps become available once it takes effect (HighLevel Support Portal, Sept 2026).
Whether that access shows up straight away depends on one toggle: "Add New Plan Features and Apps Upon Upgrading" in the SaaS Configurator. Turn it on and an upgraded client gets the new tier's features immediately; leave it off and feature access may need manual intervention.
SaaS V1 versus SaaS V2: why the mechanics differ
SaaS V1 bills through Stripe directly, so proration follows whatever your Stripe price configuration allows. SaaS V2 bills through HighLevel's own system and explicitly does not support proration for tier changes, interval changes, or a combined change in the same action (HighLevel Support Portal, Sept 2026).
On V2, budget for the change to land cleanly on the next invoice with no partial-period math. On V1 with a selling sub-account, HighLevel keeps the Stripe subscription aligned when a supported change occurs — but a manual edit made directly in Stripe doesn't sync back automatically, so verify the sub-account's plan access matches what Stripe now says.
How Stripe handles the billing side of a plan change
For agencies on SaaS V1, Stripe's proration engine does the real work behind every upgrade or downgrade. The default proration_behavior is create_prorations, which credits unused time on the old price and debits remaining time on the new price, calculated to the second (Stripe Docs, 2026).
Stripe's own example: a customer moving from a $10 to a $20 monthly plan halfway through the cycle is billed an extra $5 net. A downgrade works the same way in reverse, except the credit usually exceeds the debit — which is why downgrades often produce a credit balance rather than an immediate charge.
Three settings change what the client sees on their card that day:
create_prorations(default) — calculates the proration but only invoices it immediately under specific conditions.always_invoice— invoices the proration right away, useful for an upgrade you want charged same-day.none— disables proration for that change; the client pays the full new amount only at the next renewal.
One trap worth knowing: if there's an unpaid invoice for the current period, Stripe still calculates the proration credit as if it will eventually be paid — which can hand a client a credit for time they never actually paid for (Stripe Docs, 2026).
Upgrade vs a HighLevel SaaS plan downgrade: side by side
The two directions are not mirror images of each other. An upgrade tends to be immediate and self-funding; a HighLevel SaaS plan downgrade tends to be deferred and can leave the agency holding costs the client has already stopped paying for.
| Aspect | Upgrade | Downgrade |
|---|---|---|
| Billing effect (V1/Stripe) | Credit for unused time on old price, debit for new price — usually a net charge | Credit for unused time typically exceeds the new debit — usually a net credit, not a refund |
| Timing | Can take effect immediately via self-service flow | Scheduled for the start of the next billing cycle by default |
| Sub-account changes | New features/apps available immediately, if the agency has enabled that setting | Current plan and features stay active until the scheduled effective date |
| Agency must do manually | Verify feature access if the auto-enable toggle is off; confirm Stripe/sub-account stay in sync on manual edits | Audit usage-based charges, seats and rebilling entitlements that don't reverse on their own; confirm the effective date |
What doesn't automatically reverse on a downgrade
This is the part agencies get burned by. A downgrade changes the price and the plan-based feature list — it does not claw back everything a client has already used or added on top.
- Extra user seats added on the higher plan don't get removed; someone still has to deactivate them.
- Premium actions and paid apps stay on unless the agency or client switches them off.
- AI and phone/SMS usage billed through the agency wallet keeps accruing — HighLevel resets the plan, not what's already been consumed against it.
- Rebilling entitlements configured for the old tier can stay attached until someone re-applies the new tier's snapshot.
If you rely on usage-based rebilling for Conversation AI or Twilio/LeadConnector minutes, this is the most common reason a downgraded client still costs you the same margin. See our breakdown of how GoHighLevel Stripe invoices and subscriptions flow before building your ladder.
Designing a plan ladder so upgrades are the obvious move
The agencies with the fewest downgrade conversations aren't the ones with the best retention scripts — they're the ones whose plan ladder makes the next tier an obvious yes. Three things do most of that work.
Price the gap, not just the plan
Each rung should solve one named pain (more seats, more automations, rebilled AI minutes), not a vague "more of everything." A client should be able to say why they moved up in one sentence. If your own tiers aren't this precise yet, see our breakdown of how GoHighLevel's pricing plans compare before setting your client-facing ladder against it.
Make the upgrade path visible inside the product
A locked feature with an in-app upgrade prompt converts better than an email asking for a call. Permission sets tied to each tier should reflect this — see our guide to structuring sub-account permissions and user roles by plan.
Treat retention discounts as a scalpel, not a habit
SaaS V1 lets you configure a retention discount — a percentage off for a set duration, offered right before a downgrade completes. Used sparingly, it works; offered every time, it trains clients to threaten a downgrade for a discount, a slower version of the churn problem in our piece on reducing SaaS Mode churn.
Not on HighLevel yet? Start with a free 30-day trial here — long enough to build and test your plan ladder in a dummy sub-account before you put it in front of a single client.
The agency money view: margin, cash flow and dunning collisions
Every plan tier should have a documented margin — what the client pays minus HighLevel cost, wallet-funded usage and Twilio/Mailgun pass-through. When a client downgrades mid-cycle, you've often already incurred usage costs for that cycle at the higher tier's volume, while Stripe credits them back part of what they paid.
That mismatch is real money on any account doing meaningful AI or SMS volume. It's why some agencies set proration_behavior to none on downgrades and let price drop only at the next renewal — no credit, no reconciliation headache, at the cost of a slightly less "fair" client experience.
When a plan change and a failed card land in the same week
HighLevel automatically pauses a SaaS sub-account when its Stripe subscription status becomes canceled, past_due, incomplete, or incomplete_expired — and pausing drafts every workflow in that sub-account, which the client must republish once reactivated (HighLevel Support Portal, Sept 2026). A plan change and a card failure landing in the same week can leave a client simultaneously mid-downgrade and locked out — a confusing ticket if your team isn't checking both.
At the agency level, a failed subscription payment gives 21 days of continued access before restriction, with retries running for up to 30 days (HighLevel Support Portal, Sept 2026). Client-level dunning on individual sub-accounts is a separate, Stripe-driven process and should be checked per account.
A practical plan-change SOP
Keep this short enough that a support VA can run it without escalating every time.
- Confirm the billing model — SaaS V1 (Stripe) or V2 (HighLevel-billed) — before promising a specific proration outcome.
- Check for an unpaid invoice first; a change against an unpaid balance can generate an unexpected credit.
- Apply the change in the SaaS Configurator, not directly in Stripe, unless you'll manually verify sync afterward.
- Audit seats, premium actions, add-ons and rebilling entitlements the new tier doesn't include.
- Confirm GST on the new AUD price if you rebill Australian clients directly.
Pair the SOP with a Workflow that fires on the plan-change event and sends an internal notification — Slack, email, or a task — so a human confirms the audit happened.
Common mistakes to avoid
- Assuming a downgrade instantly removes extra seats, premium actions or paid add-ons.
- Promising an exact refund or credit amount before previewing the actual Stripe proration.
- Editing a subscription directly in Stripe instead of the SaaS Configurator, breaking sync between the two.
- Never testing plan-change behaviour on a dummy sub-account before a paying client hits it.
- Offering an automatic retention discount on every downgrade request, training clients to threaten churn.
- Ignoring GST on rebilled AUD subscriptions because HighLevel's own invoices are in USD.
If you want a plan ladder, SaaS Configurator setup and rebilling structure that doesn't leak margin on every downgrade, book a strategy call with the HL Growth Partner team.
Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.
Frequently asked questions
Does a GoHighLevel SaaS Mode plan upgrade take effect immediately?
It depends on your setup. With "Add New Plan Features and Apps Upon Upgrading" enabled, feature access updates right away; otherwise it may need manual confirmation.
What happens to the price when a client downgrades mid-cycle?
HighLevel schedules the downgrade for the next billing cycle by default, so the client keeps their current plan and price until then.
Do user seats and features automatically reduce on a downgrade?
No. Extra seats, premium actions and paid add-ons don't get removed automatically — the agency has to manually audit and deactivate anything the new tier doesn't include.
What's the difference between SaaS Mode V1 and V2 billing?
V1 bills through Stripe, so proration follows your Stripe price configuration. V2 bills through HighLevel's own system and doesn't support proration for tier or interval changes at all.
Can a client cancel a scheduled downgrade?
Yes. Before the effective date they can select "Keep My Plan," and accepting an agency-configured retention discount cancels the downgrade automatically.
What happens if a client's card fails during a plan change?
HighLevel automatically pauses the sub-account when the Stripe subscription status becomes canceled, past_due, incomplete, or incomplete_expired, which also drafts every workflow until it's reactivated.
Do I need to charge GST on rebilled SaaS Mode subscriptions in Australia?
If you rebill Australian clients directly for your own branded plans, standard GST (10%) applies to that sale, separate from HighLevel's own USD billing.
How do I test plan-change behaviour safely before offering it to clients?
Run an upgrade and downgrade against a dummy sub-account and a test Stripe price, and use Stripe's preview-invoice feature to see the exact proration before touching a paying client.
Related Articles on HL Growth Partner
Billing and money mechanics
Onboarding, retention and offboarding
- SaaS free trial funnel setup
- Shortening time-to-value in onboarding
- Client offboarding and data export
