How to Configure Downgrade Settings in GoHighLevel
When managing SaaS accounts in GoHighLevel, it is essential to control how client downgrades behave, just like organizing workflows in ClickUp. Proper downgrade settings help you protect data, prevent feature conflicts, and maintain a clean billing structure whenever a client moves to a lower plan.
This step-by-step guide explains how to configure downgrade rules in your SaaS configurator so that each subscription change in GoHighLevel is handled safely and predictably.
Why GoHighLevel Downgrade Settings Matter
Downgrade settings determine what happens to a client account when it moves from a higher tier plan to a lower tier plan. Configuring these rules in GoHighLevel helps you:
- Automatically assign the correct lower plan when a downgrade occurs.
- Control which snapshots are applied to downgraded accounts.
- Decide whether to remove features, add-ons, or locations.
- Reduce manual cleanup after clients change their billing level.
Without clear downgrade rules, clients may keep access to features they no longer pay for, or lose access in ways that disrupt their workflows.
Accessing the SaaS Configurator in GoHighLevel
To manage downgrade behavior, you must work inside the SaaS configurator of your GoHighLevel agency account. Follow these steps to get started:
- Log in to your agency-level GoHighLevel account.
- Open the left sidebar and navigate to the SaaS configuration area (SaaS Configurator / SaaS Mode, depending on your interface).
- Locate your SaaS pricing plans. These are the plans you offer to your sub-accounts.
- Select the specific plan for which you want to configure downgrade behavior.
Once you have opened the desired plan, you will see options related to both upgrades and downgrades. This article focuses on the downgrade section.
Understanding GoHighLevel Downgrade Options
Within each SaaS plan, GoHighLevel allows you to define what should happen if a client downgrades from that plan to a lower one. Typically, you will find options such as:
- Selecting a lower plan the client should move into.
- Defining how locations or seats are handled.
- Choosing snapshots or automations that should apply.
- Setting rules for feature removal.
These options ensure that when a subscription change is triggered by your billing platform, the GoHighLevel account reflects the new, lower tier accurately.
Plan Selection for Downgrades in GoHighLevel
One of the core downgrade settings is selecting the target plan. In the SaaS configurator, you can choose which plan the client will fall back to when they move down a tier.
To configure this:
- Inside the plan settings, scroll to the Downgrade or On Downgrade section.
- Open the dropdown list of available SaaS plans.
- Select the lower plan that should be applied when this plan is downgraded.
- Save your changes.
This setting ensures that the correct lower-tier plan is automatically applied when a downgrade is triggered, avoiding accidental upgrades or wrong plan assignments.
Snapshots and Automations on Downgrade
Depending on your configuration, GoHighLevel may allow you to assign a snapshot or automation to run whenever a downgrade occurs. This is useful when you want to:
- Switch the account to a simpler template for lower-tier users.
- Remove complex pipelines or funnels that are only available on higher plans.
- Adjust automations that no longer apply to downgraded accounts.
When configuring this area, review which assets belong only to higher plans and ensure that your downgrade snapshot or automations remove or disable them accordingly.
Step-by-Step: Configure a Downgrade Rule in GoHighLevel
Use the following process as a clear checklist for configuring a downgrade rule for one plan in GoHighLevel:
- Open SaaS Configurator: Sign in as an agency admin and go to the SaaS configuration section.
- Select the Source Plan: Click the SaaS plan from which clients may downgrade.
- Locate Downgrade Settings: Scroll down until you find the section dedicated to downgrade behavior.
- Choose Target Plan: From the dropdown, select the lower plan that the account will move into when downgraded.
- Configure Assets: If available, select a downgrade snapshot or automation that simplifies the account and removes higher-tier assets.
- Review Location Limits: Verify that any limits on locations, users, or features align with the new lower-tier plan.
- Save Changes: Confirm and save your configuration.
- Test With a Sample Account: Create or use a test account, assign it the higher plan, then trigger a downgrade to confirm everything behaves as expected.
Best Practices for Managing GoHighLevel Downgrades
To keep your SaaS structure clean and prevent confusion for your clients, use these best practices when configuring downgrade behavior in GoHighLevel:
Align Features With Each GoHighLevel Plan
Make a clear list of which features belong to each plan level. Then, when you set downgrade rules, verify that downgraded accounts lose access only to the items they should, without breaking core workflows.
- Check funnels, pipelines, and automation rules.
- Review integrations or add-ons that are premium-only.
- Ensure calendars, forms, and other tools still function on lower plans.
Test Downgrades Before Going Live
Always run tests using internal or dummy accounts:
- Apply the higher-tier plan to a test sub-account.
- Trigger the downgrade to the lower-tier plan.
- Confirm that the correct snapshot, limits, and features are applied.
- Verify that billing and access line up with your pricing page.
Thorough testing reduces support tickets and improves the client experience.
Document Your GoHighLevel Downgrade Rules
Maintain internal documentation so your team understands how each downgrade works. Include:
- Which higher plan downgrades to which lower plan.
- What changes in features and limits.
- Any snapshots or automations triggered during downgrades.
This documentation helps support teams quickly answer client questions about what happens when they move to a lower plan.
Troubleshooting GoHighLevel Downgrade Issues
If a client downgrade does not behave as expected, use this quick troubleshooting checklist:
- Verify the downgrade target plan is correctly selected for the source plan.
- Confirm that any connected billing platform is sending the correct downgrade event.
- Check that snapshots or automations related to downgrades are active and properly configured.
- Test with a new sub-account to rule out legacy settings or manual overrides.
If issues persist, refer to the official downgrade configuration documentation for GoHighLevel, available at this support article for more detailed, product-specific steps.
Next Steps and Additional Resources
Properly configured downgrade settings keep your SaaS plans clean, predictable, and aligned with your pricing. With the right rules in GoHighLevel, every downgrade can be automated and safe, minimizing manual intervention and client confusion.
If you need strategic help designing SaaS plans or optimizing your GoHighLevel setup for better scalability and revenue retention, you can explore specialized consulting resources at Consultevo.
After you finish configuring your downgrade settings, review your upgrade rules as well to ensure that both directions—upgrading and downgrading—are fully aligned with your overall SaaS strategy.
Need Help With ClickUp?
If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.
“`