Histories of property changes on any record are simple, straightforward, and easily accessible. There is never a question of how your data is changed over by time, or who and what.
Most integrations are easy to connect, intuitive to use, and fairly robust in their functionality.
Support is fantastic. They have a lot of product to support, and while they don't always get it right, you get a transparent experience. You speak to humans who understand the pains you're going through, what you're trying to accomplish, and what blockers exist in the way. They are leagues beyond most software support teams I've ever worked with.
I'm a Salesforce administrator. I'm used to that ecosystem. Shifting to the HubSpot ecosystem requires getting creative. While you're used to a virtually-unlimited schema in Salesforce, HubSpot essentially has four objects in its model; those objects speak to their analogs, and only their analogs, in Salesforce.
Getting HubSpot talking to all the places in Salesforce you need to is often an exercise in doing all the necessary data manipulation in Salesforce, and getting it to a place where the connector can see it.
This would be a manageable-enough task if HubSpot had the full set of data manipulation functions other tools had.
Want to timestamp something? Good luck - you can't create a datetime property unless your dev team does so via the API.
Want to multiply a property by 2 in a HubSpot workflow? The functionality does not exist.
Text parsing beyond a contains function? You won't find any.
Date literals? These do not exist.
The end result is a dissatisfying set of Hobson's choices when it comes to taking any data, and translating it into other ways the business needs to use it. As far as in-app DML is concerned, you have very little flexibility.
HubSpot is not a viable tool for larger-sized enterprises without significant customization through HubSpot's extremely robust APIs. If you do not have development resources in your org, there is a very painful ceiling to what you can do with data.
HubSpot essentially acts as a layer for our BI tools, between our in-app products and Salesforce, with a pinch of automated emailing in between. Its analytics are invaluable to our process, and most of the properties from the analytics package are mapped to external tools for further analysis and/or automation.