Implementing HubSpot

A standard mid-market B2B HubSpot implementation takes 10 to 14 weeks from kickoff to go-live. Companies that try to do it in two weeks usually do it twice. Not because the software is hard, but because the decisions around it take time: who owns which field, when is a lead an MQL, and which manual work do you automate first?

Below: the plan we follow, the migration checklist and the mistakes that cost the most money.

The plan in four phases

Weeks 1–2 — Discovery and architecture

Define your data model: which objects, which properties, which associations. Define your lifecycle stages and agree MQL-to-SQL criteria together with sales. Decide who owns which field.

This is the boring phase and the phase where success is decided. One rule that saves you a lot of cleanup later: one writer per field. Decide whether the user, the workflow or the system may set a lifecycle stage — and stick to it.

Weeks 3–4 — Portal configuration

Build the structure before you import data. This is the most ignored rule: migrate too early and you'll re-map and re-import after every change to properties, stages or naming.

Concretely in this phase:

• create objects and properties (only if you can name the report they land in)
• set up pipelines and deal stages — every stage describes a buyer action, not a seller action
• agree and document naming conventions
• configure permissions and teams
• connect inbox, calendar and domain

Weeks 5–6 — Data migration

See the checklist below. Budget more time than you think, especially when coming from several sources.

Weeks 7–8 — Automation

Build the five workflows that remove 80% of the manual work first. Resist building thirty; within six months they become a maze nobody dares touch.

Set explicit unenrolment criteria on every workflow. A nurture without an endpoint is spam on a schedule.

Weeks 9–10 — Reporting

Build one dashboard per role: leadership, marketing, sales, service. Not one dashboard with forty reports.

A revenue dashboard needs four reports in practice: pipeline per stage, won revenue per month against target, conversion rate per stage and average cycle time. Everything else is decoration.

Weeks 11–14 — Testing, training and go-live

Train per role. Marketers need attribution reporting, salespeople need deal management and the mobile app. One generic training for everyone doesn't work.

Go live in phases: email, calendar and the core database first, then product-usage or analytics integrations. That also gives you a visible new win a month after launch — exactly when enthusiasm dips.

Data migration without damage

1. De-duplicate before import. Cleaning duplicates inside HubSpot is far harder than not putting them there.
2. Standardise formats. Phone numbers with country codes, countries spelled one way, job titles normalised.
3. Validate required fields. Email, lifecycle stage and owner on every record.
4. Import in the right order: companies → contacts → deals → activities. Otherwise associations drop.
5. Run a test import of 50 records first and check them manually, field by field.
6. Keep your source files. Always. You'll need them if something goes wrong.
7. Don't migrate dead data. Contacts that did nothing for five years aren't an asset: they raise your contact tier, lower your email reputation and create GDPR risk.

The six things to get right first

Lifecycle stages. Define what makes each stage and which sources fill it. Then build one workflow that sets the stage and forbid manual changes.

Lead scoring. Combine explicit signals (role, company size, country) with implicit ones (pages, emails, demo request). Start with ten criteria, not fifty. After three months, evaluate which actually correlated with won deals and drop the rest.

Deal stages. Every stage describes a buyer action. Not "quote sent" but "quote discussed in substance". That stops your pipeline from lying optimistically.

One nurture workflow. Trigger, three to five emails at least three days apart, clear unenrolment criteria and an endpoint.

A revenue dashboard. The four reports above, nothing more.

Forms that convert. Fewer fields than you'd like. Fill the rest automatically with enrichment — that's what Breeze Intelligence is for. More in Breeze and AI.

The ten most expensive mistakes

1. Jumping to Professional without going through the Starter phase.
2. Marking every contact as a marketing contact.
3. Migrating data before portal configuration is finished.
4. Running two systems side by side "during the transition" — that becomes permanent.
5. Leaving auto-renewal switched on.
6. Creating a hundred custom properties with no reporting purpose.
7. Giving everyone a sales seat instead of core seats.
8. Building lead scoring without data to base it on.
9. Agreeing no naming convention.
10. Switching on AI agents against an empty knowledge base.

DIY, partner or HubSpot onboarding?

All three can work; it depends on your situation.

• DIY suits a Starter portal with one pipeline and a marketer with time. HubSpot Academy is free and surprisingly good.
• HubSpot onboarding (the mandatory fee on Professional and Enterprise) gives you guidance, but someone on your side still has to build.
• A partner pays off from Professional with multiple teams, or when migrating from a legacy system. Choose on three things: demonstrable experience in your sector, willingness to teach you to run it yourself, and a fixed price per phase instead of open-ended hours.

That's how we work: a fixed price per phase, and at the end the knowledge sits with your team — not only with us. Want to talk it through? Get in touch or book a free call.

Frequently asked questions

How long does a HubSpot implementation take?

For a mid-market B2B track, 10 to 14 weeks including migration, training and aftercare. A simple Starter portal with one pipeline can be live in a few days.

What does a HubSpot implementation cost?

A mid-size B2B implementation typically costs €10,000 to €40,000 in partner hours, on top of licences and a possible onboarding fee of $1,500 to $7,000.

Can I migrate data from Salesforce, Pipedrive or Excel?

Yes. Order and data quality determine the result: de-duplicate and standardise before import, and import in the order companies → contacts → deals → activities.

What's the single biggest success factor?

Clarity before configuration. One owner per field, one writer per lifecycle stage, and five workflows that genuinely remove manual work.