Feature Comparison: Transitioning from Legacy Plan to Team Plan in SonarQube Cloud

We are considering changing our current (legacy) subscription plan to the new Team plan. We tried finding details on the features available in both plans but couldn’t locate a proper comparison. Could you please direct us to a resource where we can find a feature comparison between the paid legacy plan and the Team plan?

We also looked at Subscription plans | SonarQube Cloud Documentation, but we’re still a bit unclear about what features we might lose if we switch from our current plan to the new Team plan.

1 Like

Hey there.

Those features are mentioned here:

Organizations on the legacy paid plan

If your legacy paid plan organization is billed on a monthly basis, it will still benefit, for a given period, from some features that were moved to the Enterprise plan:

  • Report of security alerts in GitHub. (docs)
  • Support of the ABAP, APEX, COBOL, JCL, PL/I, and RPG languages.
  • Centralized project management (docs)

I added links to the docs for the first and third points, since they’re a bit more vague.

Thanks for your response regarding this question.

We have already reviewed that section; however, we hope the newly added documentation will provide further clarity.

If we proceed with the Team plan, will we have 1.9M LOC support from the start, or would we need to pay extra as before?

The cost of the team plan varies based on the Lines of Code threshold selected for your organization. In very simple terms, 1.9M LoC costs more than 1M.

Is there a place where we can refer the pricing information related to LOC?

LOC-specific pricing information is available in the UI when modifying your plan

1 Like