HubSpot implementation playbook.
Built for multi-market enterprises.
A HubSpot implementation playbook runs six phases: Understand, Design, Build, Migrate, Launch and Adopt. Each phase has named owners on both sides, the decisions it must close, the deliverables it produces and an exit gate that must pass before the next begins.
Six phases, six exit gates.
A planning template, not a fixed schedule.
Understand
Agree the revenue number and the current state, market by market.
Exit: Scope, success measures and sponsor confirmed in writing
Design
Agree how the system works before anyone configures a property.
Exit: Design signed off by the sponsor and every process owner
Build
Configure HubSpot to the design, in a test environment first.
Exit: User acceptance testing passed by each team against agreed scripts
Migrate
Move mapped, cleansed data into HubSpot with nothing lost and nothing duplicated.
Exit: Trial migration reconciled object by object, and the cut-over plan approved
Launch
Go live with every user able to do their job on day one.
Exit: Go-live checklist complete and hypercare issues triaged to closure
Adopt
Make HubSpot the place work happens, then improve it from what the data shows.
Exit: Leadership runs its reviews from HubSpot dashboards
Each gate is a sign-off, not a date. The next phase starts when the gate passes.
Understand the business first.
Owners
Client: executive sponsor; heads of marketing, sales and service per market; IT and data owner. Azend: engagement lead, solution architect, RevOps consultant.
Key decisions
Which hubs and markets are in scope. Which revenue number the programme serves. Who signs off each phase.
Deliverables
Stakeholder interviews, current process maps, systems and data audit, requirements ranked by value.
Questions to ask in discovery
Where does a lead come from today, and who touches it next? Which reports does leadership use, and which does it trust?
Which systems hold customer data, and which must stay the source of truth? Which channels do customers actually use: email, WhatsApp, Viber or LINE?
Design on paper before building.
Owners
Client: process owners per team, data protection officer. Azend: solution architect, RevOps consultant, integration lead.
Key decisions
Lifecycle stages and their definitions. Pipelines and deal stages. Object model, including custom objects. Source of truth for each field. Teams and permissions by market.
Deliverables
Solution design, data model, integration architecture, migration map, reporting specification.
Design rules we hold to
Define each lifecycle stage once, with an entry rule a system can check. Keep one pipeline per sales motion, not one per person. Name an owner for every property.
Design consent and retention per market, to the data protection law that applies: MY PDPA, SG PDPA or the PH Data Privacy Act.
Build to the signed design.
Owners
Client: process owners for reviews, IT for system access. Azend: HubSpot consultants, developers, quality assurance.
Key decisions
What is configured and what is built custom. Which automations go live at launch, and which wait.
Deliverables
Configured hubs, properties, pipelines, workflows, integrations, dashboards and test scripts.
Sprints that end in a demo
Each sprint ends with a working demo to the process owner, not a status report.
Migrate clean data, once.
Owners
Client: data owner, administrators of the legacy systems. Azend: data lead, integration lead.
Key decisions
What history moves and what is archived. Deduplication rules. Cut-over by market or all at once.
Deliverables
Field mapping, cleansing rules, trial migrations, reconciliation report, cut-over plan.
Trial, reconcile, repeat
Run a full trial migration into a test environment. Reconcile record counts and samples for every object. Fix issues at source, then run it again.
Freeze edits in the legacy system only for the cut-over window. Our CRM migration checklist sets out every step.
Launch with every user ready.
Owners
Client: sponsor, team leads, super users per market. Azend: engagement lead, trainers, hypercare support.
Key decisions
Go or no-go. Launch order by market or team. Which legacy tools are switched off, and when.
Deliverables
Role-based training, quick-reference guides, go-live checklist, hypercare rota.
Train by role, inside the work
Train reps on their own pipeline, service agents on their own queue and managers on their own dashboards.
Super users in each market answer first-line questions in the local language, so support scales with the rollout.
Adopt, then improve on data.
Owners
Client: sponsor, team leads, RevOps owner. Azend: RevOps consultant, managed operations team.
Key decisions
Which adoption measures leadership reviews. What goes on the improvement backlog. When AI agents are introduced.
Deliverables
Adoption dashboard, monthly review, prioritised backlog, AI agent roadmap.
What we measure in adoption
Active users by team, records kept current by their owners, pipeline reviewed inside HubSpot, and the reports leadership actually opens.
The baseline is set at launch. Ongoing support runs through managed operations.
Eight risks, eight mitigations.
The risks we plan for on every implementation, and how each is closed.
Unclear ownership
Name one sponsor and one decision owner per process in Understand.
Scope creep
One change log, approved by the sponsor and tested against the revenue number.
Dirty data
Cleanse at source before the trial migration. Agree deduplication rules in Design.
Integration delays
Confirm system access, APIs and owners in Understand. Build integrations early in Build.
Low adoption
Train by role before launch. Measure adoption after it.
Markets treated as one
Design teams, currencies, languages and permissions per market from the start.
Data protection gaps
Design consent and retention to each market’s law. The data protection officer signs the design.
Agents switched on too early
Add AI agents once data and processes are stable, with people in the loop and each agent measured.
The checklist.
Every item true before you call this done.
Sponsor and decision owners named
One per process, with authority to sign off.
Revenue number agreed
Plus the success measures each phase serves.
Stages defined with entry rules
Lifecycle and deal stages, written once.
Data model signed off
A source of truth for every field.
Consent designed per market
To each market's data protection law.
Integrations tested end to end
With real records, in a test environment.
Trial migration reconciled
Object by object, before cut-over.
Users trained by role
With super users in each market.
Go-live checklist complete
Hypercare rota live and issues triaged.
Adoption reviewed by leadership
From HubSpot dashboards, not spreadsheets.
Questions.
How long does a HubSpot implementation take?
As long as its scope demands. Hubs, markets, data volume, integrations and decision speed set the clock. We set durations at scoping and plan each phase against them. Full answer
Can the phases run in parallel?
Yes, by market. A second market can be in Build while the first is in Adopt, provided the shared design is signed off.
Who should own HubSpot after go-live?
A named RevOps owner on the client side, with authority over the data model and the change log. Azend can support through managed operations.
Plan the six phases with us.
A strategy call maps your scope, owners and exit gates against one revenue number.