The HubSpot Implementation Checklist We Use on Every Client Project

Most HubSpot portals we inherit were not badly built. They were built in the wrong order. Someone imported 40,000 contacts before the properties existed, switched on sequences before the sending domain was authenticated, and drew a deal pipeline before sales leadership agreed what "qualified" means. Six months later the team is paying to undo it.

This is the HubSpot implementation checklist we work through on every new client project, in the order we run it. It assumes a B2B team of 10 to 250 people on Sales Hub and Marketing Hub Professional or above. Skip a phase and you will feel it in the reporting by the end of the quarter.

Phase 1: Decide What the Portal Must Answer Before You Configure Anything

Write down the five questions the leadership team needs HubSpot to answer every Monday. Typically: how much qualified pipeline did we create, which channels created it, how fast do inbound leads get a reply, what will close this quarter, and which customers are at risk of not renewing.

Every property, pipeline stage and dashboard you build later should trace back to one of those questions. If it does not, leave it out. This is the single cheapest control against the junk-drawer portal problem.

• Agree lifecycle definitions in writing. Map each value of the default lifecyclestage property (Subscriber, Lead, MQL, SQL, Opportunity, Customer) to an observable event, not a feeling.
• Agree lead status values. Keep hs_lead_status to five or six values that sales will actually update, such as New, Attempting, Connected, Qualified, Disqualified.
• Name the owner of each object. One person signs off changes to contacts, companies, deals and tickets. Without that, property sprawl starts in week two.

Phase 2: Account Foundations, Users and Compliance Settings

These settings are dull, and they are the ones most often skipped. Each one is far harder to fix once live data and sends are flowing.

• Users and permissions. Create teams under Settings > Users & Teams, keep Super Admin to two named people, and use permission sets so reps cannot bulk-delete or export the full database.
• Domains and tracking. Install the tracking code, connect your website domain, and authenticate the email sending domain with SPF, DKIM and DMARC before any marketing email goes out.
• Cookie consent banner. Configure it under Settings > Privacy & Consent so tracking respects consent under PECR, which the ICO treats as a separate requirement from UK GDPR.
• Lawful basis and subscriptions. Turn on data privacy settings so the hs_legal_basis property is captured on forms and imports, and build Subscription Types that match how you actually email people. Our UK GDPR checklist for HubSpot covers the full set, including PECR Regulation 22 soft opt-in for existing customers.
• Marketing contacts. Decide the rule for setting hs_marketable_status before the first import, or you will pay for every cold record in the database from day one.

Phase 3: Data Model and Pipeline Architecture

Build the structure that data will land in before any data arrives.

• Properties. Create custom properties in Settings > Properties inside named groups (for example "Marketick – Qualification"), use dropdowns instead of free text wherever reporting depends on the value, and write a description for every property.
• Associations. Set association labels such as Decision Maker, Champion and Billing Contact so deals carry buying-committee context rather than a single random contact.
• Deal pipeline. Keep it to five to seven stages, each with a clear exit criterion. Use conditional stage properties so a rep cannot move a deal to "Proposal Sent" without filling amount, close date and decision maker.
• Renewals. If you sell annual contracts, build a separate renewal pipeline from the start. Mixing renewals into new business inflates win rates and hides churn.

If you are still weighing platforms at this stage, our HubSpot vs Salesforce comparison for scale-ups sets out where each one breaks.

Phase 4: Data Migration, Integrations and Automation

Only now do records come in. Treat migration as a project with its own sign-off, not an afternoon of CSV uploads.

• Clean before you import. Deduplicate on email for contacts and on company domain for companies. Our guide on cleaning up duplicate contacts in HubSpot explains the unique-ID setup that stops duplicates returning.
• Import in object order. Companies first, then contacts, then deals, then activities, using the legacy system ID in a unique-value property so every association can be rebuilt and checked.
• Run a test import of 200 records. Check owners, lifecycle stage, associations and hs_legal_basis on a sample before loading the full file.
• Connect integrations deliberately. For each app (finance, calendar, enrichment, product data), decide which system wins when values conflict and which fields sync. Enrichment tools left on default settings will overwrite clean data.
• Build the first five workflows only. Lead assignment by territory or round robin, lifecycle stage progression, speed-to-lead task creation, deal stage task reminders and a closed-lost reason prompt. Name each workflow with its object and purpose so the list stays readable at 50 workflows.

Phase 5: Reporting, Training and the 30-Day Review

• Build one dashboard per Monday question from Phase 1, using only properties you created on purpose.
• Train by role, not by feature. A 45-minute session for reps covers their daily view, logging calls, moving deals and booking meetings. Managers get forecasting and pipeline reviews.
• Hold a 30-day review. Pull a list of deals missing amount or close date, contacts with no owner, and workflows with enrolment errors. Fix the root cause rather than the records.

If the review shows the same gaps recurring, the issue is usually process maturity rather than configuration. Our RevOps maturity model helps place where your team sits before you add more tooling.

The Order Matters More Than the Tick Boxes

Nothing on this list is secret. The value is in the sequence: definitions before properties, properties before pipelines, pipelines before data, data before automation. Teams that follow it usually go live with reporting the board accepts in the first month. Teams that reverse it spend the next two quarters on clean-up work they could have avoided.

Frequently Asked Questions

What should be on a HubSpot implementation checklist?

At minimum: agreed lifecycle and lead status definitions, users and permission sets, domain and email authentication, consent and lawful basis settings, custom properties and association labels, deal and renewal pipelines with stage requirements, a staged data migration, the first core workflows, role-based dashboards and a 30-day review.

Should we migrate data before or after building pipelines?

After. Build properties, associations and pipelines first so imported records land in the right fields and stages. Importing first means mapping data into structures that will change, which creates rework and broken reports.

How do we handle UK GDPR and PECR during a HubSpot implementation?

Turn on data privacy settings before any import, capture hs_legal_basis for every contact, set up Subscription Types and the cookie banner, and only rely on soft opt-in under PECR Regulation 22 for genuine existing customers.

Do we need a HubSpot partner to implement HubSpot?

Not always. A small team with a capable admin can follow this checklist in-house. A partner earns their fee on migration from another CRM, complex integrations, and getting sales and marketing to agree definitions.

How many workflows should we build at launch?

Around five: lead assignment, lifecycle progression, speed-to-lead tasks, deal stage reminders and closed-lost reasons. Add more once the team is using the basics and the data from them is clean.