The HubSpot Implementation Checklist: Every Phase, in Order

Most HubSpot implementations run into trouble not because the platform is difficult, but because businesses skip the groundwork. They jump straight into building pipelines and importing contacts before they have agreed on what they actually want HubSpot to do.

This checklist covers every phase of a HubSpot implementation in order, from the decisions you need to make before you touch the portal through to the checks you run on go-live day. Each phase includes the specific tasks to complete and a brief explanation of why they matter.

Use it as a working document. Tick off each item as you go, assign owners, and flag anything that needs a decision before you move forward.

Before you start: This checklist assumes you are implementing HubSpot from scratch or re-implementing after a messy first attempt. If you are migrating from another CRM, you will need additional steps around data extraction and field mapping.

Phase 1: Define Your Requirements (Before You Build Anything)

This is the phase most businesses skip. Skipping it is why so many HubSpot portals end up messy, underused, and untrustworthy within six months.

Before anyone logs into HubSpot, you need agreement on what success looks like and what the system needs to support. This is a business conversation, not a technical one.

Business and process alignment

• Define the commercial goal for this implementation (e.g. improve pipeline visibility, reduce manual reporting, align sales and marketing)
• Map your current customer journey from first contact to closed deal
• Document your sales process: stages, entry and exit criteria, typical deal length
• Identify where marketing hands off to sales (and agree on the definition of a qualified lead)
• List the reports leadership needs to see every week or month
• Identify the manual tasks your team wants to automate

Scope and hub selection

• Confirm which HubSpot Hubs you are activating (Sales Hub, Marketing Hub, Service Hub, Operations Hub)
• Confirm your HubSpot tier (Starter, Professional, Enterprise) and check it includes the features you need
• List any integrations required (e.g. accounting software, ERP, data warehouse, telephony)
• Agree on who owns the HubSpot portal internally and who has admin access

Why this matters: Implementations that skip requirements definition almost always need to be rebuilt. You end up configuring HubSpot around assumptions that do not match how the business actually works.

Phase 2: Portal Setup and Account Configuration

With your requirements agreed, you can start configuring the portal itself. This phase covers the foundational settings that everything else depends on. Getting these right early saves significant rework later.

Account and branding

• Set your company name, logo, and brand colours in portal settings
• Configure your time zone, currency, and date format
• Set up your company domain and verify it in HubSpot
• Connect your business email (Google Workspace or Microsoft 365)
• Configure your email sending domain for marketing and sales emails

Users, teams, and permissions

• Invite all users and assign appropriate permission sets
• Create teams that reflect your organisational structure (e.g. Sales, Marketing, Customer Success)
• Set object-level permissions (who can view, edit, delete contacts, companies, deals, tickets)
• Configure data privacy settings in line with UK GDPR requirements
• Enable two-factor authentication for admin accounts

Tracking and integrations

• Install the HubSpot tracking code on your website
• Connect your CRM integrations (see your integration list from Phase 1)
• Connect your calendar (Google or Outlook) for meeting scheduling
• Set up the HubSpot Sales Extension for your email client
• Verify that web analytics data is flowing correctly into HubSpot

Key checkpoint: Before moving to data setup, confirm that users can log in, permissions are correct, and your domain and email sending are verified. These are the most common causes of delays at go-live.

Phase 3: CRM Architecture and Data Structure

This is the most technically consequential phase. The decisions you make here determine how clean your data stays, how useful your reporting is, and how much manual work your team has to do. Poor CRM architecture is the root cause of most HubSpot problems we see in practice.

Object and property setup

• Audit the default HubSpot properties and remove or hide those you will not use
• Create custom contact properties for data your business needs to capture
• Create custom company properties relevant to your ICP (e.g. industry, employee count, region)
• Create custom deal properties that support your sales process and reporting
• Define required fields for each object so records are created consistently
• Set up property groups to keep the record view organised for users

Pipeline design

• Build your deal pipeline(s) with stages that match your actual sales process
• Define clear entry and exit criteria for each deal stage
• Set deal stage probabilities to support forecasting
• Create a separate pipeline for any distinct sales motions (e.g. new business vs. renewals)
• If using Service Hub, configure your ticket pipeline and support stages

Lifecycle stages and lead management

• Define and document your lifecycle stage definitions (Subscriber, Lead, MQL, SQL, Opportunity, Customer)
• Agree on the criteria that move a contact from one lifecycle stage to the next
• Set up lead status values that reflect your sales team's workflow
• Create contact and company association rules so records link correctly

Why this matters: Retrofitting CRM architecture after data has been imported is painful. Contacts end up with missing fields, pipelines do not reflect reality, and reporting becomes unreliable. Build the structure before you import anything.

Phase 4: Data Import and Migration

With your data structure in place, you can bring your existing contacts, companies, and deals into HubSpot. Data quality at this stage directly determines the quality of your reporting from day one.

Data preparation (before importing)

• Export your existing contact and company data from your current system
• Remove duplicate records before importing
• Standardise formatting across key fields (e.g. phone numbers, job titles, country names)
• Map your existing data fields to the HubSpot properties you created in Phase 3
• Remove contacts who have unsubscribed or are no longer relevant
• Segment your import into logical batches (e.g. active customers, prospects, cold contacts)

Importing records

• Import companies first, then contacts, then deals (in this order to preserve associations)
• Use HubSpot's import tool and validate the field mapping before confirming each import
• Check a sample of imported records manually to verify data accuracy
• Assign lifecycle stages and lead statuses to imported contacts where known
• Associate contacts with their correct companies and deals after import

Post-import data checks

• Run a duplicate check using HubSpot's duplicate management tool
• Review records with missing required fields and fill gaps where possible
• Confirm that company-to-contact associations are correct
• Check that deal records are linked to the right contacts and companies

A note on data quality: It is better to import fewer, cleaner records than to bring across years of messy data. A smaller, accurate database is more useful than a large, unreliable one. You can always add records later.

Phase 5: Automation, Reporting, and Hub-Specific Configuration

With clean data in a well-structured portal, you can now build the workflows, reports, and hub-specific features that make HubSpot genuinely useful. This phase is where the implementation starts to deliver value.

Automation and workflows

• Build internal notification workflows (e.g. alert sales when a contact becomes an MQL)
• Set up lead rotation or assignment rules if you have multiple sales reps
• Create deal stage automation (e.g. create a task when a deal moves to Proposal Sent)
• Build contact lifecycle automation so stages update based on behaviour or deal activity
• Set up any follow-up sequences for sales outreach
• Test every workflow with a real or test record before activating

Reporting and dashboards

• Build a pipeline report showing deals by stage and value
• Create a lead source report showing where contacts are coming from
• Set up a sales activity report (calls, emails, meetings by rep)
• Build a revenue forecast report using deal stage probabilities
• Create a leadership dashboard with the KPIs agreed in Phase 1
• Set up scheduled dashboard email reports for stakeholders

Hub-specific configuration

Different hubs require additional setup depending on your scope.

Complete the relevant rows for the hubs in your scope. Not every business will use all four.

Why this matters: Automation and reporting are where most businesses expect to see immediate ROI from HubSpot. Building them on top of clean data and a solid structure means they work reliably from day one, rather than producing misleading outputs.

Phase 6: Testing, Training, and Go-Live

The final phase is where most implementations either succeed or quietly fail. A portal that works technically but is not adopted by the team has not delivered value. Testing and training are not optional extras — they are what separates a successful implementation from an expensive one.

Pre-launch testing

• Test every active workflow end-to-end using a test contact
• Verify that web forms submit correctly and create records in HubSpot
• Check that the tracking code is firing on all key website pages
• Confirm that email sending is working and emails are not landing in spam
• Test meeting booking links and calendar sync
• Walk through a complete deal from creation to close-won and check all automations fire correctly
• Confirm that dashboards and reports are pulling accurate data
• Review integration data flows and check that records are syncing correctly

User training

• Run a role-specific training session for sales reps covering daily CRM use
• Run a separate session for marketing, covering lead management and campaign tools
• Train any administrators on portal settings, workflow management, and data quality
• Create a short internal reference guide covering your specific processes (not just HubSpot features)
• Document where to log support requests or flag issues post-launch

Go-live checks

• Confirm all users are active and can log in
• Archive or delete any test contacts, deals, or records created during setup
• Set a go-live date and communicate it to all users
• Identify a point of contact for post-launch questions
• Schedule a two-week post-launch review to address early issues

After go-live: HubSpot is not a set-and-forget system. Plan reviews at 30, 60, and 90 days to assess data quality, workflow performance, and user adoption. The first three months are where good implementations are consolidated, and poor ones start to deteriorate.

Common Implementation Mistakes to Avoid

Even with a checklist, implementations go wrong in predictable ways. These are the issues we see most often.

• Skipping requirements definition. Building before you have agreed on what you need always results in rework. The portal ends up reflecting assumptions rather than reality.
• Importing dirty data. Bringing across years of unclean records creates a data quality problem that compounds over time. Clean before you import.
• Over-engineering the build. Complex workflows, excessive custom properties, and elaborate automations are harder to maintain and more likely to break. Start simple and add complexity only when there is a clear reason for it.
• Treating go-live as the finish line. HubSpot requires ongoing management. Without a clear owner and a regular review cadence, portals degrade quickly.
• Configuring HubSpot around the software, not the business. HubSpot should reflect how your team actually works. If your implementation forces your team to change its process to fit the tool, adoption will suffer.

The businesses that get the most from HubSpot treat implementation as the start of an ongoing programme, not a one-time project.

Need Help With Your HubSpot Implementation?

This checklist covers what needs to happen. How long it takes and how smoothly it goes depends on the complexity of your processes, the quality of your existing data, and whether you have someone with the experience to make the right decisions at each phase.

If you are working through this and realise the scope is larger than expected, or you want to avoid the common mistakes, Pixcell can help. We work with B2B businesses across the UK to design and implement HubSpot properly, from requirements through to go-live and beyond.

• HubSpot Implementation and Onboarding - structured implementation delivered in four weeks

• Fractional RevOps and HubSpot Support - ongoing ownership and optimisation after go-live
• HubSpot Audit - if your portal is already live but not working well, start here

If you are not sure where to start, the HubSpot Audit is the right first step. It gives you a clear picture of what is working, what is not, and what to prioritise.