Skip to content
Book a build

Free tool

HubSpot implementation estimator: hours and weeks for your scope

Pick the hubs, tier, data, integrations and automation in scope. You get low–high hours for each workstream, a calendar estimate in weeks, a phase plan and the assumptions behind it, ready to copy or download.

Free, no sign-up. Data checked .

Hubs in scope
Tier (the highest edition you're buying)
More than 1 for multi-brand or multi-region setups.
Contacts, companies, deals, tickets combined. 0 if none.
Other CRMs, spreadsheets, tools you migrate from.
HubSpot makes custom objects available on Enterprise subscriptions.
HubSpot lists workflows for Professional or Enterprise subscriptions only, not Starter. Pick Starter with workflows and the estimate warns you.
Hours the team spends on your project each week. Ask your partner.
Any currency. Left blank, no cost is shown.

Runs in your browser. Nothing you enter leaves this page.

Your estimate

139–337 hours

About 8–20 weeks on the calendar at 20 delivery hours a week, including time waiting on decisions. HubSpot's partner rules ask a partner replacing its onboarding to begin within 10 business days of the subscription start, unless you set another timeline.

HubSpot's own reference: Sales Hub: customers typically complete onboarding within 2 months, some faster (sample onboarding plan); Marketing Hub: customers typically complete onboarding within 3 months, some faster (sample onboarding plan). Those plans cover up to three goals and don't break out hours for migration or integrations. HubSpot designs each onboarding plan around your current tech stack and how it integrates with HubSpot. Its onboarding pages list guidance on setting up standard (App Marketplace or native) integrations; they don't list building custom API integrations, except Customer Platform Onboarding's Premier tier, which lists custom integrations. The guidance is remote; your team or a partner does the hands-on work.

Hours by workstream (low–high), from our planning assumptions
WorkstreamHoursBasis
Discovery and scoping12–24Base + 2 hubs
Account setup and data model11–22Base + 25 users
Hub configuration22–52Marketing Hub, Sales Hub × Professional factor
Workflows and automation20–50Moderate: about 6–20 workflows, some branching
Reporting and dashboards12–24Team
Data migration16–361 source system, 20,000 records
Integrations8–202 marketplace/native, 0 custom
Testing and launch13–4115–20% of build hours
Training and documentation12–24Sessions by role, plus short guides + 2 hubs
Project management13–4410–15% of all other hours
Total139–3378–20 weeks

Phase plan

Phases overlap in practice; weeks are each phase's share of the timeline. Project management runs across all of them.
PhaseHoursWeeksSign-off before moving on
1. Discovery12–241–1.5Agreed scope and ranked goals
2. Data model and account setup11–220.5–1.5A written schema: internal names, types, option values
3. Build54–1263.5–8.5Reviewed plan first, then reviewed assets
4. Migration and integrations24–561.5–4Record counts and samples match the source
5. Test, train, hand over25–651.5–4.5Acceptance by the people who will run it

To budget, multiply the hours by your partner's hourly rate, or type it into the optional rate field.

Migration hours assume the data model is agreed first, one test import and one final import. Heavy cleanup or full activity history adds time.

Marketing Hub and Sales Hub Professional and Enterprise come with HubSpot's required one-time onboarding unless a Solutions Partner waives it by delivering the onboarding itself.

Hours come from the planning assumptions below, not from HubSpot. If Projects builds the properties, pipelines and workflows from your brief, the configuration hours can drop; we don't publish a number for that. Want this scoped by someone who'll deliver it? Get a partner recommendation ↓

Planning assumptions behind every number (ours, not HubSpot's)

HubSpot publishes no hours per workstream. These figures are Jetstack AI planning assumptions for a partner or experienced admin doing the work. Compare them with your partner's quote line by line; the downloads include this table.

WorkstreamDriverLowHighUnit
Discovery and scopingPer project: goals, current process, systems, decision owners816hours
Discovery and scopingEach hub in scope24hours per hub
Account setup and data modelDomains, tracking code, email connection, core properties, lifecycle and pipeline stages816hours
Account setup and data modelEach user: invites, teams, permission sets0.10.25hours per user
Hub configurationMarketing Hub: forms, lists, email templates, lead scoring, lifecycle rules1228hours
Hub configurationSales Hub: deal pipelines, templates, sequences, meetings, quotes1024hours
Hub configurationService Hub: ticket pipelines, inbox and channels, knowledge base1024hours
Hub configurationContent Hub: domains, CMS settings, templates, blog setup (not a website build)824hours
Hub configurationData Hub: data sync settings, data quality, custom code actions616hours
Hub configurationCommerce Hub: products, quotes, payments, invoices616hours
Hub configurationStarter: fewer tools to configure0.60.8× hub hours
Hub configurationProfessional: the baseline11× hub hours
Hub configurationEnterprise: teams, permissions, more tools to configure1.31.6× hub hours
Custom objects and associationsEach custom object: schema, properties, associations, pipeline if any614hours per object
Workflows and automationLight (up to about 5 simple workflows), built and tested615hours
Workflows and automationModerate (about 6–20 workflows), built and tested2050hours
Workflows and automationHeavy (20+ workflows, routing, cross-object logic), built and tested50120hours
Data migrationEach source system: field mapping, cleanup decisions, test import, reconciliation1020hours per source
Data migrationVolume: up to 10,000 records26hours
Data migrationVolume: 10,001–100,000 records616hours
Data migrationVolume: 100,001–1,000,000 records1640hours
Data migrationVolume: over 1,000,000 records4080hours
IntegrationsEach marketplace or native integration: install, field mapping, test sync410hours per integration
IntegrationsEach custom API integration: spec, build, error handling, testing2460hours per integration
Reporting and dashboardsStandard410hours
Reporting and dashboardsTeam1224hours
Reporting and dashboardsAdvanced2448hours
Training and documentationAdmin handoff48hours
Training and documentationSessions by role, plus short guides816hours
Training and documentationExtended program2040hours
Training and documentationRole or extended training: each hub in scope24hours per hub
Additional portalsEach extra portal: share of setup, hub configuration, custom objects, workflows and reporting repeated0.350.7× those hours
Testing and launchTesting with real records, staged switch-on of workflows0.150.2× build hours
Project managementMeetings, status, change control0.10.15× all other hours
CalendarWaiting on decisions and reviews from your side13weeks added
CalendarAny custom integration: waiting on the other system's owner and access12weeks added

What HubSpot says about implementation time

HubSpot publishes durations for its own onboarding programs, and only those. They’re the one official reference in this estimate:

HubSpot programWhat HubSpot states
Sales Hub sample onboarding planCustomers typically finish within 2 months, some faster
Marketing Hub sample onboarding planWithin 3 months, some faster
Service Hub Professional sample planWithin 2 months, some faster
A Solutions Partner replacing HubSpot’s onboardingBegins within 10 business days of the subscription start

Each plan covers up to three goals and is guidance, not a build: HubSpot sends customers who need hands-on execution to a Solutions Partner. The guidance can cover integrations: HubSpot plans each onboarding around your tech stack, and Sales Hub Onboarding lists turning on standard App Marketplace and native integrations. The hands-on migration, integration and custom object work still comes on top, and HubSpot doesn’t time it. Content Hub, Data Hub and Commerce Hub have no published timeline that we could find. More in how long a HubSpot implementation takes.

What drives the timeline

  • Migration. Each source system needs field mapping, a test import and reconciliation. Agree the data model first or you import twice.
  • Integrations. Marketplace apps are hours; custom API work is weeks, mostly waiting on the other system’s owner.
  • Custom objects. Schema decisions everything else references. HubSpot makes them available on Enterprise only.
  • Workflows. Each one needs testing with real records before it’s switched on.
  • Several portals, brands or teams. Routing, permissions and reporting have to be agreed for each group.
  • Open decisions. Lifecycle definitions and pipeline stages often cost more calendar time than building them. The estimate adds one to three weeks for this.

How to read the estimate

The hour figures are planning assumptions, not HubSpot data, listed in one table under the tool and in both downloads. Low assumes clear decisions and clean data; high assumes rework. Weeks are total hours divided by the delivery hours a partner spends on you each week, plus decision time, so a partner working 10 hours a week roughly doubles the build time of one working 20.

There are no prices because partner rates vary and HubSpot doesn’t publish them. Multiply the hours by your partner’s rate, and budget separately for HubSpot’s required onboarding on Professional and Enterprise editions of Marketing Hub and Sales Hub (what the onboarding fee covers, can a partner replace it).

What to ask a partner

  1. Which of these workstreams does your quote include, and which are excluded?
  2. How many workflows, reports and review rounds are in the price?
  3. How many hours a week will you spend on us, and who does the work?
  4. When does each phase need a sign-off from us?
  5. What do we receive at handoff?

Use the downloaded estimate as the brief you send every partner, so the quotes are comparable. See how partners price implementations, what implementation services include, the phases, the checklist, what an implementation costs, onboarding services or in-house and how to choose a partner.

Where Jetstack AI fits

Projects builds properties, pipelines, lists, forms, emails and workflows from an agreed brief after your approval, then reads each one back from HubSpot. That can shorten the configuration lines; we don’t publish a figure. Migration, integrations and user setup stay with you or your partner. Inheriting a portal? Run a Portal Audit before scoping. Running several portals? With Portal reuse you can deploy the same setup to multiple destination portals, reviewing each portal’s mappings.

Want a hand with this project?

Get a partner recommendation.

We work with experienced HubSpot partners. Tell us about the portal and the work, and we'll recommend one that fits your scope, timeline and budget.

HubSpot implementation estimator

Questions about this tool.

Why does the estimator show hours instead of prices?

Partner rates vary widely and HubSpot doesn't set or publish them. Hours for a defined scope are the comparable part. Type your partner's hourly rate into the optional field, or multiply the hour range by it yourself.

Where do the hour ranges come from?

They are our planning assumptions, not HubSpot data: HubSpot doesn't publish hours per workstream. Every figure sits in one table on this page and in the downloads, so you can check it against a partner's quote. The only durations HubSpot states are in its sample onboarding plans: within 2 months for Sales Hub and Service Hub Professional, within 3 months for Marketing Hub, for up to three goals.

Is this the same as HubSpot's onboarding?

No. HubSpot's onboarding is remote guidance on up to three goals, and your team does the work. That guidance can include integrations: HubSpot plans each onboarding around your tech stack and how it integrates with HubSpot, and Sales Hub Onboarding lists turning on standard App Marketplace and native integrations. This estimate counts the hands-on hours for migration, integrations and testing, which HubSpot's sample plans don't break out.

Sources

HubSpot changes often. Spotted something out of date? Tell us at team@jetstack.ai.

Planning & implementation

Turn the brief into approved HubSpot assets.

Projects plans the build against the client portal, generates the assets and deploys them only after you approve.

Explore Projects