The current maximum of 10 custom objects per location is too restrictive for businesses that use HighLevel as a comprehensive CRM and long-term client management platform.

I am building a financial services CRM that needs to manage multiple repeatable relationships and records, including employment history, properties, mortgages, liabilities, assets, vehicles, credit history, business relationships, insurance policies, lending opportunities, and other financial records.

These are fundamentally different data entities and should not be forced into Contact custom fields or combined into unrelated objects simply because the system has reached a 10-object limit.

I have already reached the maximum of 10 custom objects while building the core architecture, before completing important areas such as P&C insurance, life insurance, annuities, investment/retirement accounts, and additional lending records.

Please consider significantly increasing the custom object limit, ideally with a higher or scalable limit based on plan level or as a paid add-on. Even increasing the limit to 25, 50, or allowing additional object capacity as an add-on would make HighLevel much more suitable for advanced CRM implementations.

HighLevel already provides powerful custom fields, associations, workflows, APIs, and AI capabilities. Allowing more custom objects would make these capabilities substantially more valuable for businesses that need relational and repeatable data structures.

This limitation is currently affecting my ability to continue building my business architecture inside HighLevel, even though I would prefer to keep HighLevel as my primary CRM platform.

Thank you for considering an increase to the custom object limit.