Blog · Automation

HubSpot onboarding: an eight-week plan, built on HubSpot’s own rules

HubSpot onboarding goes well when the decisions come before the set-up: who owns the account, what the lifecycle stages mean, what data is worth bringing across. This plan works through those decisions in order, ties each step to HubSpot’s own documentation, and ends with a checklist for agencies and in-house teams.

What is HubSpot onboarding?

HubSpot onboarding is the work of setting up a HubSpot account so a business can use it every day: deciding who controls it, bringing data across from old systems, building the lifecycle stages, pipelines and automation that match how the business sells, and training the people who will use it. It ends when the teams use HubSpot without help, not when the settings are filled in.

The guides that rank for this topic, such as Marketveep’s and Elefante RevOps’, describe the phases well. This plan adds the decisions each phase depends on, and ties each step to HubSpot’s own documentation, so an agency or in-house team can see why the order matters.

The plan at a glance

A typical onboarding for one or two HubSpot hubs takes about eight weeks: two of decisions, two of data, two of building, one of training and a review. Larger accounts take longer, but the order is the same.

An eight-week HubSpot onboarding plan
  1. 1Weeks 1 to 2: decideGoals, owners, Super Admin, seats, lifecycle stages and pipelines agreed in writing.
  2. 2Weeks 2 to 3: cleanOld data exported, duplicates resolved, required columns completed.
  3. 3Weeks 3 to 4: importCompanies, contacts and deals imported in order, with associations checked.
  4. 4Weeks 4 to 6: buildProperties, pipelines, forms, subscription types and core workflows.
  5. 5Weeks 6 to 7: trainEach team trained on the parts it uses, with written notes.
  6. 6Week 8: reviewWhat is used, what is not, and the next quarter’s changes.

The order matters more than the timing. Building workflows before lifecycle stages are agreed means rebuilding them; importing before deduplication means fixing duplicates by hand afterwards. Each phase below starts from the decisions the previous one settled.

Weeks 1 to 2: decide ownership and structure

The first two weeks produce decisions, not settings. Every later step depends on them, and they are much cheaper to change on paper than in a live account.

Ownership and Super Admin

HubSpot’s permissions guide says Super Admins set what every user can view, create, edit or delete in an account. That role belongs with the business, in an account in its own name. An agency or consultant doing the onboarding works with the permissions the business grants, and those can be reduced once the work is done.

Seats

HubSpot assigns every user on a Starter, Professional or Enterprise subscription a seat type, from View-Only to paid seats, and changing seats needs Super Admin or billing permissions. Seats are a cost decision as well as an access one. List who needs to view, who needs to edit and who needs the paid features, and agree the seat mix before inviting anyone.

Lifecycle stages

Lifecycle stages decide how a contact moves from subscriber to customer, and every report about leads depends on them. HubSpot provides eight default stages; the decision is what each means for this business.

HubSpot’s default lifecycle stages, and what to decide for each
Stage HubSpot’s definition What to decide
Subscriber Opted in to hear more, such as a blog or newsletter sign-up Which forms set it, and which subscription types they use
Lead Converted beyond a subscription sign-up Which actions count as converting
Marketing Qualified Lead Qualified by marketing as ready for sales The written criteria, so marketing and sales agree
Sales Qualified Lead Qualified by sales as a potential customer; uses Lead Status sub-stages The Lead Status values your sales team will actually use
Opportunity Associated with a deal Whether deals are created automatically or by a person
Customer At least one closed deal Nothing, if deals are closed properly
Evangelist A customer who has advocated for you Whether you will use it at all
Other Does not fit any other stage Who uses it, so it does not become a dumping ground
Stage definitions from HubSpot’s lifecycle stages guide, read on 15 November 2026.

HubSpot’s lifecycle guide notes that default automatic updates only move the stage forward, for example from Subscriber to Opportunity. Moving a record backwards needs a manual change or a workflow designed for it. Write the criteria for each stage down, especially Marketing Qualified Lead, and get marketing and sales to agree them before anything is built.

Pipelines

Deal pipelines should mirror the real sales process, not an ideal one. HubSpot’s pipeline guide says a Starter, Professional or Enterprise subscription is needed to create a custom pipeline, and that lead pipelines need Professional or Enterprise. Agree the stages, what has to be true to move between them and which fields are required at each step.

Weeks 2 to 3: clean the data

Clean data before importing it. HubSpot will deduplicate some records automatically, but only on the fields it uses to match, and only if those fields are filled in.

HubSpot’s deduplication guide says it automatically deduplicates contacts by email address and companies by company domain name, and that record IDs can be used to deduplicate other objects. A contact with no email address cannot be matched that way, so it either gets an email, gets merged by hand or gets left out.

How long the data cleanup will take

Contacts without an email address cannot use HubSpot’s automatic email deduplication, and suspected duplicates need a decision. Enter your own figures; the defaults are an example, not a benchmark.

Records needing a human look1,680
Hours of review28.0Records needing review / records an hour
Records that can be imported as they are10,320
HubSpot deduplicates contacts by email address and companies by domain name, per its deduplication guide. The shares and review rate are placeholders for your own counts.

With the example figures, which are placeholders rather than HubSpot data, 12,000 records with 8% missing an email and 6% suspected duplicates leaves 1,680 records for a person to look at. At 60 an hour, that is 28 hours of review before the import, and 10,320 records that can go in as they are. Your own figures will differ; the point is to know the size of the job before setting the go-live date.

Migrate everything or start clean

Migrate all the old data, or start clean?
Is the old data used in reports or by the sales team every week?
Yes
Do most records have an email address, owner and source?
Yes
Migrate it, after deduplication, and keep a full export of the old system as an archive.
No
Migrate the active part only. Bring across open deals, customers and recent contacts; archive the rest as an export.
No
Is there a legal or contractual reason to keep the history in the CRM?
Yes
Migrate it, clearly labelled, with an import property such as the source system and date, so it can be filtered out of everyday views.
No
Start clean. Import customers and open deals, archive the old system’s export, and let new data build up properly from day one.
A guide, not a rule. Whatever you decide, keep a complete export of the old system before switching it off.

Weeks 3 to 4: import in the right order

Import companies first, then contacts, then deals, so each import can associate records with ones already in HubSpot. Check a sample after each import before running the next.

HubSpot’s import guide describes three import modes: create and update, create new only, and update existing only. To update existing records, the file must contain a unique identifier. It also notes that existing emails, meetings, notes and tasks cannot be updated by import, so activity history should be imported once and checked carefully.

  • Companies. With the domain filled in, so HubSpot’s automatic company deduplication works.
  • Contacts. With email addresses, company domain or name for association, owner, lifecycle stage and original source.
  • Deals. With pipeline, stage, amount, close date and the contact or company they belong to.
  • An import property on everything. A field recording the source system and the import date, so imported records can always be filtered, checked or removed.

Weeks 4 to 6: build properties, pipelines and automation

Build only what the agreed decisions need. Every property and workflow is something someone has to understand and maintain.

Properties

Create properties for information people will actually fill in and report on. A property nobody completes is noise in every record and every export. Group custom properties so they are easy to find, and document what each one is for.

Forms and subscription types

Set up email subscription types before any marketing email is sent, so each contact’s consent is recorded against the kind of email they agreed to. Connect each form to the right subscription types and lifecycle stage. Sending rules from the mailbox providers apply here too: Google’s sender guidelines require SPF and DKIM, DMARC for bulk senders and one-click unsubscribe for senders of more than 5,000 messages a day.

Workflows

Start with the few workflows that remove the most manual work: routing new leads to an owner, setting lifecycle stages from form submissions, creating follow-up tasks, and sending the first follow-up email. Give each workflow an owner and a one-line written purpose, and test it with real records before switching it on.

Reports

Build the dashboards each team will open: leads by source and stage for marketing, pipeline and forecast for sales. Where HubSpot reports meet web analytics, use the same source and campaign conventions as GA4; the GA4 audit guide covers how to check that tracking.

Connecting the other tools

Most businesses connect HubSpot to other tools during onboarding: the website, the email inbox and calendar, the ad accounts, a billing or ecommerce system. Each connection moves data in or out, so each needs the same care as an import.

  • List every connection first. What it is, which direction data flows, which objects and properties it touches, and who owns it.
  • Decide which system wins. When two tools hold the same field, such as a company name or deal amount, agree which one is the source of truth, so a sync does not overwrite good data with bad.
  • Connect one at a time. Switch on one integration, check a sample of records, then move to the next. Several at once make faults hard to trace.
  • Record it in the handover. Every connection, its owner and what it changes, so the next person does not have to rediscover it.

Website tracking deserves its own check. If HubSpot’s tracking code and Google Analytics both run on the site, their source and campaign data should use the same naming conventions, or the two will disagree about where leads came from.

Weeks 6 to 7: train the people who will use it

Train each team on the parts it uses, not on HubSpot in general. A sales team needs records, deals, tasks and sequences; marketing needs forms, lists, emails and reports.

  • Short sessions by role. An hour per team, on their own records and pipelines, works better than a day-long general course.
  • Written notes. One page per team: where things are, what to fill in, and who to ask.
  • Agreed habits. What must be recorded after a call, when a deal moves stage, who changes lifecycle stages by hand.
  • One person to ask. An internal owner for questions, so problems are caught early.

HubSpot’s own Academy has free courses that suit people who want to go further, but they do not replace training on the account the team will actually use.

Week 8: review what is used

Eight weeks in, check what the teams actually use. Onboarding is finished when the account matches how people work, not when every feature is switched on.

  • Adoption. Who logs in, who updates deals, which reports are opened.
  • Data quality. New duplicates, records without owners, stages that never change.
  • Workflows. Which ones ran, which errored, which nobody would miss.
  • Next quarter. The changes worth making now that real use has shown what matters.

Unused properties and workflows should be removed at this point, while people still remember why they were created.

Keeping HubSpot clean after go-live

Onboarding sets the account up clean; keeping it clean takes a few habits and a short monthly check.

  • One way in for new contacts. Forms, imports and integrations should all set the same core fields: owner, source and lifecycle stage.
  • A monthly data check. New duplicates, records without owners, deals stuck in one stage for months.
  • A rule for new properties. Anyone can ask for one; one person decides, so the account does not fill with half-used fields.
  • A rule for new workflows. Each one has an owner and a purpose written in its description, and is reviewed when that owner leaves.
  • A quarterly review. The same questions as week 8: what is used, what is not, what should change.

None of this needs a consultant. It needs an owner inside the business with the time to do it, which is worth agreeing at the start of onboarding rather than at the end.

The onboarding handover document

Every onboarding should end with a short written document the business keeps. It is what lets someone new, or a new agency, understand the account without reverse-engineering it.

  1. Ownership and access. Who is Super Admin, which seats exist and why, and who to ask for access.
  2. Definitions. Each lifecycle stage, each pipeline stage and what has to be true to move between them.
  3. Data. Where the old data came from, what was left out, and where the archive export is kept.
  4. Properties. Custom properties, what each is for and who fills it in.
  5. Automation. Each workflow, its owner and its purpose.
  6. Connections. Each integration, the direction of data and which system wins on shared fields.

Keep it short enough that people read it. A few pages that are accurate are worth more than a long manual that is out of date by the next quarter.

What onboarding costs

The cost of onboarding is mostly people’s time: the decisions, the cleanup and the training. HubSpot subscriptions and seats are a separate line, and depend on the hubs and tiers chosen.

Elefante RevOps says businesses with a single hub and straightforward requirements typically spend $750 to $3,500 on onboarding, and that large implementations with multiple hubs and extensive migration can exceed $15,000. Those figures are one agency’s view, not a survey, but they match the shape of the work: the cost rises with the number of hubs, the amount of data and the custom integrations.

Whoever does the work, budget the internal time too. The decisions in weeks 1 and 2 need people from marketing, sales and leadership, and no outside partner can make them for the business.

For agencies onboarding clients

Agencies onboarding a client into HubSpot carry the same responsibilities as an in-house team, plus one more: making sure the client owns what is built.

  • The client’s account. HubSpot in the client’s name and on their payment method, with the client as Super Admin.
  • Written decisions. Lifecycle criteria, pipeline stages and property definitions handed over as a document, not left in someone’s head.
  • Reduced access afterwards. The agency’s users reduced to what ongoing work needs once onboarding ends.
  • A clear scope. Hubs, imports, workflows and training sessions listed, so both sides know when onboarding is done.

How agencies resell this kind of work under their own brand, and the rules that come with it, is covered in what white-label marketing is.

Common onboarding mistakes

Most HubSpot onboarding problems come from doing the steps out of order.

  • Building before deciding. Workflows built before lifecycle criteria are agreed have to be rebuilt.
  • Importing before cleaning. Duplicates fixed by hand after import take far longer than before.
  • A supplier as Super Admin. The business cannot fully control its own CRM.
  • Too many properties. Fields nobody fills in make every record harder to read.
  • Email before subscription types. Consent recorded wrongly from the first send is hard to correct.
  • No review. Without a week-8 review, unused workflows and properties stay forever.
  • Training once and never again. New starters learn from whoever sits next to them, and the habits agreed at launch fade. Add the handover document to every new starter’s first week.

The HubSpot onboarding checklist

The checklist follows the plan. Work through it before go-live; the first two groups matter most.

The HubSpot onboarding checklist
Ownership and access
Data
Structure
Email and automation
Adoption
Ticks are saved in your browser.

If you would rather have the onboarding done for you, my HubSpot implementation service follows this plan, and agencies can buy it under their own brand through white-label CRM and marketing automation.

The short version

Onboard HubSpot in the order decide, clean, import, build, train, review: keep Super Admin with the business, write down lifecycle and pipeline criteria before building, clean emails and domains before import because HubSpot deduplicates on them, set up subscription types before any email goes out, and review what is used after eight weeks.

Operator note

The onboarding that goes wrong is almost always the one that started in the settings. Two weeks of decisions on paper saves a month of rebuilding later.

The one decision I always push for is the written definition of a Marketing Qualified Lead. Without it, every report about leads starts an argument.

Frequently asked

What is HubSpot onboarding?
Setting up a HubSpot account so the business can use it every day: ownership and access, data migration, lifecycle stages, pipelines, automation and training, ending when teams use it without help.
How long does HubSpot onboarding take?
About eight weeks for one or two hubs: two weeks of decisions, two of data cleanup and import, two of building, one of training and a review. Larger accounts with more data or integrations take longer.
Who should be Super Admin in HubSpot?
The business itself. Super Admins set what every other user can view, create, edit or delete, so the role should stay with the account owner rather than an agency or consultant.
How does HubSpot handle duplicate records?
HubSpot automatically deduplicates contacts by email address and companies by domain name. Records without those values are not matched automatically, so clean them before importing.
What order should I import data into HubSpot?
Companies, then contacts, then deals, so each import can be associated with records already in HubSpot. Add an import property recording the source and date to everything.
Do lifecycle stages move backwards automatically?
No. HubSpot says its default automatic updates only move the lifecycle stage forward; moving a record back needs a manual change or a workflow built for it.
How much does HubSpot onboarding cost?
It depends mostly on time: decisions, cleanup and training. Elefante RevOps puts single-hub onboarding at $750 to $3,500 and large multi-hub implementations above $15,000; HubSpot subscriptions and seats are separate.
Related reading
GA4 audit: a checklist for agencies, in the order that saves data What is white-label marketing? How agencies use it, and the rules that apply Webflow vs WordPress for client sites: cost, ownership and how to leave
Working on this yourself?

I have 3 client slots open for Q4 2026. If this raised a question about your own situation, or you want help with it, send it over.

Say hello