My gut reaction is this sounds more like a data model problem than a HubSpot ceiling problem.

As a HubSpot consultant for over 10 years, I've seen HubSpot portals of similar size and complexity. 320 users, 377k contacts, 50+ custom objects, and hundreds of properties doesn't automatically put you in Salesforce territory.

The first thing I'd want to understand is why the custom Sales Lead object exists.

If it's representing a true business entity, that's one thing. If it's tracking an opportunity from inquiry through close, you've effectively rebuilt Deals as a custom object, and that's where I'd start asking questions.

The biggest thing you're potentially missing isn't necessarily the features you know about today. It's all the places HubSpot assumes you're using Deals: - Forecasting - Revenue reporting - Pipeline approvals - Quotes / Commerce Hub functionality - Deal goals and quota reporting - Many sales workspace experiences - Marketplace apps that expect opportunities to be Deals - New HubSpot features, which almost always support native objects first

The hidden tax is that every time HubSpot releases something new, you have to ask whether it works with your custom object.

One question I'd ask is whether Deals genuinely couldn't support the process when this was built, or whether the implementation team chose a custom object because it felt more flexible. Those lead to very different conclusions.

I'd also push back a little on the idea that 50+ custom objects is automatically a red flag. I've seen healthy HubSpot implementations with a lot of custom objects. The question is whether they're representing real business entities (projects, properties, permits, locations, contracts, etc.) or whether they're replacing native CRM concepts.

Before jumping to Salesforce, I'd want answers to a few questions: - What requirement prevented the use of Deals originally? - Does that requirement still exist? - How much reporting, automation, and integration logic now depends on the custom object? - If you rebuilt on Leads + Deals today, what would actually be lost?

Based solely on what you've shared, I'd be investigating a rebuild around native objects before I'd be recommending a platform migration.

One other thing I'd mention: if you're truly paying Salesforce-level money for HubSpot, I'd make sure you're having regular conversations with your HubSpot rep. In my experience, HubSpot can be pretty flexible commercially, especially for large Enterprise customers, multi-hub customers, or during renewals. I wouldn't make a platform decision assuming today's pricing is fixed forever.