I would start a HubSpot rollout by agreeing what the team needs to do in it. That means defining the process, preparing the records and naming the people responsible for decisions.
The checks below cover both a new setup and an existing account that needs attention. They give you a way to review the work before expanding it.
1. Building before agreeing the process
Map how a lead arrives, becomes qualified and passes to sales. Define who owns each handover and what evidence allows a deal to move forward. Include rejected leads and purchases completed outside HubSpot.
Use real examples to resolve disagreements before configuring stages. A short process document gives the team something concrete to test against.
2. Assuming onboarding includes every implementation task
HubSpot describes its onboarding as technical and strategic guidance tailored to your goals, products and technology stack. The delivery scope still needs to be explicit.
Check who configures the account, cleans and migrates data, builds integrations, tests changes and trains users. Record what your own team must deliver. Avoid estimating the schedule from the word “onboarding” alone; the work and dependencies determine it.
3. Importing without a record-matching plan
Review duplicates, field formats and missing values before importing. Decide how records will be identified and associated. HubSpot supports Record ID for existing records, with Email and Company domain name among the other identifiers available for contacts and companies. Follow the import requirements for your objects.
I would test a small sample, then check updates, new records and associations before importing the rest. Preserve relevant subscription and suppression information during migration; excluding someone from a campaign does not automatically mean deleting their CRM history.
4. Leaving lifecycle and deal stages undefined
Lifecycle stages describe a contact or company's relationship with the business. Deal stages describe progress through a sales process. Agree what qualification, sales acceptance and becoming a customer mean in your setup.
If purchases happen elsewhere, decide how that evidence reaches HubSpot. The lifecycle stage guide covers the native settings, automation options and care needed when correcting existing records.
5. Automating rules the team has not tested
Begin with a process people can explain and records they trust. Add automation where its inputs, expected result and owner are clear.
Test normal records, missing information and records that should be excluded. Check repeat enrollment and what happens when another system updates the same field. Keep workflows focused enough to investigate, and agree how to stop one if it behaves unexpectedly. Automation can support adoption; its rollout needs the same review as the rest of the setup.
6. Treating training as the end of adoption
Name an internal owner for questions and changes. Give that person time to maintain the setup, with a sponsor who can resolve disagreements about business rules.
Train people on their actual tasks and reports. After launch, review incomplete handovers, missing activity and work still happening elsewhere. Use those findings to adjust the process and training. Include CRM training in the plan for new colleagues.
7. Creating properties without a clear use
Check the meaning of an existing property before adding another. For a new property, record its purpose, owner, allowed values and where the value comes from. Decide who needs to see or edit it.
Review forms and record layouts around the task the user is doing. Remove unused fields only after checking their dependencies in workflows, reports and integrations. A field that looks empty may still be part of an active process.
8. Connecting systems without ownership rules
For each integration, document which system owns each field, the sync direction and what happens when values disagree. Check associations and record matching alongside property updates.
Test conflicting updates and sync failures before enabling the connection broadly. My data quality case shows how I separate a detected mismatch from the decision to correct a record. Finding a difference is the start of the review.
9. Overlooking marketing contact settings and billing
First check whether your subscription uses marketing contacts. In that model, marketing contacts count towards the paid contact tier; non-marketing contacts do not. Marketing status is a billing designation, separate from email subscription preferences. HubSpot explains which tools use marketing contacts.
Review the settings for imports, forms and connected tools before adding records. Monitor the current count, tier limit and next update date. Under the documented marketing-contact model, exceeding the tier triggers an upgrade. Changing contacts to non-marketing takes effect on the next update date. Purchased tiers can only be downgraded at renewal under these rules. Check the billing rules for your account, including the maximum marketing contacts setting.
I would resolve this before a large import. Keep subscription preferences intact and agree who can change marketing status.
Agree what is ready for launch
Choose a first process the team can complete from start to finish. Confirm the records, ownership and reports support it, then give users a route to report problems. Keep unfinished work in an owned list with clear priorities.
If you are reviewing an existing setup, start with a sample of recent leads or deals and follow their handovers. Questions about what you find? You're welcome to compare notes.