HubSpot implementation that your team actually adopts

We treat migration as an editorial exercise. Records are profiled first to see what is genuinely there. Duplicates are identified and merged with documented rules. Free text fields that should be controlled values get mapped to picklists. Phone numbers and states are normalised. Contacts with no activity for years are imported into a suppressed status or left behind entirely, depending on your retention obligations. Associations between contacts, companies and deals are rebuilt properly, because a contact without a company association is invisible to half the reporting you will want.

Consent history migrates too, and this is not optional for Australian senders. HubSpot's subscription types and legal basis fields need populating from your old system so that a person who opted out three years ago does not receive a welcome email because their consent state was left behind. The Spam Act 2003 obligations we cover in email automation apply from your first send in the new portal, not from a grace period.

Every migration runs into a sandbox or a staging import first, with record counts reconciled against the source before anything touches production.

Sometimes it clearly does. A vehicle for an automotive dealer, with a service history and an owner who changes. A property for a real estate agency, associated with vendors, buyers and multiple deals over time. A course intake for a training organisation. A subscription or contract with its own renewal date, value and status. In each case the entity has its own lifecycle, its own reporting needs and relationships to more than one contact, which is exactly what a custom object is for.

Often it does not. We are frequently asked for a custom object when a well designed set of properties on an existing object would do the job, and the custom object would add complexity, licensing cost and reporting friction for no benefit. The test we apply is whether the thing has a life independent of the deal or contact it attaches to. If it does not, it is a property. If it does, and you find yourself keeping a spreadsheet beside HubSpot to track it, that spreadsheet is the evidence. Businesses in property and automotive hit this pattern more than most.

Those questions are usually consistent. Where is pipeline coming from and is it enough. How long does a deal take by stage and where does it stall. What is the conversion rate from enquiry through to closed business by source. Which customers are at risk. Answering them properly requires the plumbing described earlier, since a source report is only as good as your campaign tagging and a stage duration report is meaningless if deals are moved in bulk on the last day of the month.

Where the reporting needs to combine HubSpot data with finance, delivery or operational systems, we usually surface it outside HubSpot in Power BI or Looker Studio rather than fighting the native reporting to do something it was not designed for. Marketing sourced pipeline should reconcile with the lifecycle work in marketing automation, and if the two disagree, that is the first thing worth fixing.

If your commercial model is unusual, HubSpot will resist. Complex quoting with configurable products, project delivery with milestone billing, layered account hierarchies with contracted pricing, or heavy inventory dependence all sit outside what the deal object handles gracefully. You can extend a long way with custom objects and integration, but there is a point where you are building an application inside a CRM. Past that point a purpose built CRM or an integration with your ERP is cheaper and more stable.

And if the real problem is that nobody follows a sales process, changing platform will not create one. HubSpot enforces nothing you have not defined. We have told prospective clients that their existing CRM is fine and that the money would be better spent defining the process and cleaning the data, which is the CRM automation conversation rather than a migration. It is a shorter project and it usually produces the improvement they were hoping the new platform would deliver.