SaaS Plan Labels Updated to V1 and V2

Modified on: Mon, 27 Apr, 2026 at 2:53 PM

To reduce confusion between different SaaS plans, HighLevel has updated plan labels across the platform.

  • Agency Plan is now labeled SaaS V1 Plan

  • SaaS Plan is now labeled SaaS V2 Plan


This is a label-only change. There are no updates to pricing, features, billing, or functionality.


TABLE OF CONTENTS


What’s Changed


The naming of SaaS plans has been updated to clearly distinguish between legacy and newer plan structures:

  • SaaS V1 Plan → Previously known as Agency Plan

  • SaaS V2 Plan → Previously known as SaaS Plan


These updates apply automatically to all existing and new products.


Where You’ll See This


You will see the updated labels in:

  • Payments → Products

  • SaaS product listings across the platform


Example: Updated Plan Labels


Below are examples of how the updated plan labels appear in your Products list.


SaaS V1 and SaaS V2 Plan Labels



Updated Labels Across Product List



Do You Need to Take Action?


No action is required.

  • Your existing products remain unchanged

  • Pricing and billing are unaffected

  • Subscriptions continue as normal


Frequently Asked Questions


Q: Does this change affect pricing or billing?

No. This is a label-only update. Pricing and billing remain the same.

Q: Do I need to update or recreate my plans?

No. All plans are automatically updated with the new labels.

Q: Are SaaS V1 and SaaS V2 different products now?

No. These are the same plans as before, with updated naming for clarity.

Q: Will my clients see any changes?

Only the plan name may appear differently. There are no changes to billing or functionality.

Q: Why was this change made?

The update helps clearly distinguish between legacy (V1) and newer (V2) SaaS plan structures.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article