HubSpot Unbound 2026: What Matters for You and What Has Changed So Far
HubSpot UNBOUND 2026, held in Boston from September 16 to 18, repositioned HubSpot as an Agentic Customer Platform built around Growth Context, a layer of business ...
What we do · Build
HubSpot ImplementationCRM MigrationsGTM EngineeringHubSpot Reporting & AnalyticsWhat we do · Run
HubSpot Managed ServicesGTM as a ServiceRevOps as a ServiceAI & Agent Hub White-Label Partner ProgramInsights
ArticlesCase studiesRevenue Operations guideGTM Engineering guideHubSpot implementation guideB2B sales guideHubSpot migration guideHubSpot implementation guide
A HubSpot implementation is more than turning on features. It is deciding how your business will run inside the CRM: the data model, the pipelines, the automation, the integrations and how your team will use it every day. This guide walks through each phase, with the checklist we use on real projects.
Before you start
Most HubSpot problems start on day one. A portal set up in a hurry, or by someone learning HubSpot while building it, ends up with duplicate properties, pipelines nobody trusts and workflows that fight each other. The team stops using it, and the subscription keeps being paid.
Implementations that work have three things in common: the business process is agreed before anything is configured, the data model is designed once and shared by every hub, and adoption is planned as carefully as the setup. The checklist below follows that order.
If you are still evaluating the platform, start with What is HubSpot. If you are comparing HubSpot's own onboarding with a partner, see HubSpot onboarding vs Solutions Partner onboarding.
The implementation checklist
Each phase depends on the one before it. Building automation before the data model is right is the most common reason projects need to be redone.
01 · Scope
Document how leads become customers today, which teams use the CRM, which reports leadership needs and which systems must connect. Agree on what is in the first release.
Done when: a signed scope with goals, users and success metrics.
02 · Data model
Contacts, companies, deals, tickets and custom objects where needed, with naming rules, required fields and ownership. Every hub will read this model.
Done when: a data dictionary the whole team can read.
03 · Migration
Map fields from the old system or spreadsheets, deduplicate, keep history and associations, and test with a sample before the full import.
Done when: records in HubSpot that match the source.
04 · Process
Deal and ticket pipelines with stage rules, lifecycle stages, lead status, routing and the handoffs between marketing, sales and service.
Done when: a process every rep follows the same way.
05 · Automation
Workflows for routing, follow-up and alerts, then integrations with email, calendar, billing, ERP or product data. Keep each workflow with one clear job.
Done when: manual work removed without side effects.
06 · Reporting
Dashboards for leadership, sales managers and reps, built on the definitions agreed in scope, so every number has one meaning.
Done when: reports the leadership uses in its meetings.
07 · Adoption
Role-based training with the team's own data, a launch date, office hours in the first weeks and a short list of what each role must do in HubSpot every day.
Done when: the team works in HubSpot, not around it.
More detail on the process in CRM implementation process.
Hub by hub
One portal, several hubs, one data model underneath. These are the essentials of each.
Objects, properties, associations, permissions, teams and data quality rules. The foundation every other hub reads.
Data quality alertsForms, lead capture, lifecycle stages, lead scoring, email, nurturing and campaign attribution.
Deal pipelines and stage rules, routing, sequences, meetings, quotes and forecasting.
Sales automation done rightTicket pipelines, help desk, SLAs, knowledge base and customer feedback.
Website and blog on a theme marketing can edit on its own, with languages, SEO and tracking set up from the start.
Launching a Content Hub websiteAI agents and assistants turned on only where the data and playbooks are ready, with permissions and credits under control.
See AI Agent HubThe mistakes that cost the most
Each of these is cheap to avoid during the implementation and expensive to fix a year later.
Building pipelines before marketing, sales and leadership agree on the stages and what each one means.
Migrating duplicates and empty fields from the old system and promising to clean them later.
Creating a field for every request instead of designing the data model, until nobody knows which one to use.
Several workflows changing the same property, with no naming rules or owner, until the results become unpredictable.
Workflow troubleshootingOne generic session at launch, with no role-based training or support in the first weeks.
After go-live
Go-live is the start, not the end. The business keeps changing, new people join, new tools get connected and requests for fields and workflows keep coming. Without someone owning the portal, quality drifts back to where it started.
Three habits keep a portal healthy: a monthly data quality review, rules for who can create properties and workflows, and a backlog where requests are prioritized instead of built on demand. Our articles on workflow governance and the data quality command center show how we run it.
If you would rather have a senior team look after the portal every month, see HubSpot Managed Services.
From the blog
HubSpot UNBOUND 2026, held in Boston from September 16 to 18, repositioned HubSpot as an Agentic Customer Platform built around Growth Context, a layer of business ...
HubSpot supports native HubSpot Video, which needs Marketing, Service or Content Hub Professional or Enterprise and adds in-player CTAs, forms and CRM analytics, and ...
Use a HubSpot private app for a single account you control, especially when the integration needs webhooks, and a public app when it will be installed on multiple ...
To run GTM, GA4, and Microsoft Clarity on a HubSpot site while respecting consent, connect the native opt-in cookie banner to Google's consent mode, load the consent ...
HubSpot Content Hub is a full development platform beyond its visual editor: developers build themes and modules locally, sync them with the HubSpot CLI, add logic with ...
Launching and managing a HubSpot Content Hub website means treating it as an ongoing product: separate structure from content, build in performance, test changes before ...
Common questions
In our projects most portals go live in about 30 days: a week each for discovery and data model, migration and integrations, automation and reporting, and training and go-live. Portals with several hubs, a large migration or custom integrations can take six to eight weeks. Scoping first is what keeps the timeline honest.
Scope and goals, the data model, data migration, pipelines and lifecycle stages, automation and integrations, dashboards, and training and adoption, in that order. The checklist on this page details each phase.
Yes, for a simple setup with one hub and little data. As soon as there is a migration, several teams, custom objects or integrations, mistakes in the data model become expensive, and an experienced partner usually pays for itself.
HubSpot onboarding teaches your team the tools. A Solutions Partner designs and builds the portal around your process, migrates your data and connects your systems. See HubSpot onboarding vs Solutions Partner onboarding.
Yes, and it is the best moment to do it, because the data model is being designed anyway. History, associations and owners can be kept when the migration is planned field by field. See CRM Migration.
Train by role with real data, define the few things each role must do in HubSpot every day, give support in the first weeks and use HubSpot reports in the team meetings. When leadership runs the meeting from HubSpot, the team keeps it up to date.
Want it done right the first time?
Implementation across every hub by a Diamond partner, on clean data, with your team trained.