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 .
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.
| Workstream | Hours | Basis |
|---|---|---|
| Discovery and scoping | 12–24 | Base + 2 hubs |
| Account setup and data model | 11–22 | Base + 25 users |
| Hub configuration | 22–52 | Marketing Hub, Sales Hub × Professional factor |
| Workflows and automation | 20–50 | Moderate: about 6–20 workflows, some branching |
| Reporting and dashboards | 12–24 | Team |
| Data migration | 16–36 | 1 source system, 20,000 records |
| Integrations | 8–20 | 2 marketplace/native, 0 custom |
| Testing and launch | 13–41 | 15–20% of build hours |
| Training and documentation | 12–24 | Sessions by role, plus short guides + 2 hubs |
| Project management | 13–44 | 10–15% of all other hours |
| Total | 139–337 | 8–20 weeks |
Phase plan
| Phase | Hours | Weeks | Sign-off before moving on |
|---|---|---|---|
| 1. Discovery | 12–24 | 1–1.5 | Agreed scope and ranked goals |
| 2. Data model and account setup | 11–22 | 0.5–1.5 | A written schema: internal names, types, option values |
| 3. Build | 54–126 | 3.5–8.5 | Reviewed plan first, then reviewed assets |
| 4. Migration and integrations | 24–56 | 1.5–4 | Record counts and samples match the source |
| 5. Test, train, hand over | 25–65 | 1.5–4.5 | Acceptance 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.
| Workstream | Driver | Low | High | Unit |
|---|---|---|---|---|
| Discovery and scoping | Per project: goals, current process, systems, decision owners | 8 | 16 | hours |
| Discovery and scoping | Each hub in scope | 2 | 4 | hours per hub |
| Account setup and data model | Domains, tracking code, email connection, core properties, lifecycle and pipeline stages | 8 | 16 | hours |
| Account setup and data model | Each user: invites, teams, permission sets | 0.1 | 0.25 | hours per user |
| Hub configuration | Marketing Hub: forms, lists, email templates, lead scoring, lifecycle rules | 12 | 28 | hours |
| Hub configuration | Sales Hub: deal pipelines, templates, sequences, meetings, quotes | 10 | 24 | hours |
| Hub configuration | Service Hub: ticket pipelines, inbox and channels, knowledge base | 10 | 24 | hours |
| Hub configuration | Content Hub: domains, CMS settings, templates, blog setup (not a website build) | 8 | 24 | hours |
| Hub configuration | Data Hub: data sync settings, data quality, custom code actions | 6 | 16 | hours |
| Hub configuration | Commerce Hub: products, quotes, payments, invoices | 6 | 16 | hours |
| Hub configuration | Starter: fewer tools to configure | 0.6 | 0.8 | × hub hours |
| Hub configuration | Professional: the baseline | 1 | 1 | × hub hours |
| Hub configuration | Enterprise: teams, permissions, more tools to configure | 1.3 | 1.6 | × hub hours |
| Custom objects and associations | Each custom object: schema, properties, associations, pipeline if any | 6 | 14 | hours per object |
| Workflows and automation | Light (up to about 5 simple workflows), built and tested | 6 | 15 | hours |
| Workflows and automation | Moderate (about 6–20 workflows), built and tested | 20 | 50 | hours |
| Workflows and automation | Heavy (20+ workflows, routing, cross-object logic), built and tested | 50 | 120 | hours |
| Data migration | Each source system: field mapping, cleanup decisions, test import, reconciliation | 10 | 20 | hours per source |
| Data migration | Volume: up to 10,000 records | 2 | 6 | hours |
| Data migration | Volume: 10,001–100,000 records | 6 | 16 | hours |
| Data migration | Volume: 100,001–1,000,000 records | 16 | 40 | hours |
| Data migration | Volume: over 1,000,000 records | 40 | 80 | hours |
| Integrations | Each marketplace or native integration: install, field mapping, test sync | 4 | 10 | hours per integration |
| Integrations | Each custom API integration: spec, build, error handling, testing | 24 | 60 | hours per integration |
| Reporting and dashboards | Standard | 4 | 10 | hours |
| Reporting and dashboards | Team | 12 | 24 | hours |
| Reporting and dashboards | Advanced | 24 | 48 | hours |
| Training and documentation | Admin handoff | 4 | 8 | hours |
| Training and documentation | Sessions by role, plus short guides | 8 | 16 | hours |
| Training and documentation | Extended program | 20 | 40 | hours |
| Training and documentation | Role or extended training: each hub in scope | 2 | 4 | hours per hub |
| Additional portals | Each extra portal: share of setup, hub configuration, custom objects, workflows and reporting repeated | 0.35 | 0.7 | × those hours |
| Testing and launch | Testing with real records, staged switch-on of workflows | 0.15 | 0.2 | × build hours |
| Project management | Meetings, status, change control | 0.1 | 0.15 | × all other hours |
| Calendar | Waiting on decisions and reviews from your side | 1 | 3 | weeks added |
| Calendar | Any custom integration: waiting on the other system's owner and access | 1 | 2 | weeks 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 program | What HubSpot states |
|---|---|
| Sales Hub sample onboarding plan | Customers typically finish within 2 months, some faster |
| Marketing Hub sample onboarding plan | Within 3 months, some faster |
| Service Hub Professional sample plan | Within 2 months, some faster |
| A Solutions Partner replacing HubSpot’s onboarding | Begins 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
- Which of these workstreams does your quote include, and which are excluded?
- How many workflows, reports and review rounds are in the price?
- How many hours a week will you spend on us, and who does the work?
- When does each phase need a sign-off from us?
- 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
- Sales Hub sample onboarding plan (HubSpot)
- Marketing Hub sample onboarding plan (HubSpot)
- Service Hub Professional sample onboarding plan (HubSpot)
- Sales Hub Onboarding: what it covers and when to use a Solutions Partner (HubSpot)
- HubSpot onboarding services: plans built around your tech stack and its integrations (HubSpot)
- Customer Platform Onboarding: integration guidance by tier (HubSpot)
- Create workflows: subscription requirements (HubSpot Knowledge Base)
- HubSpot Partner Program sales rules: onboarding requirements (HubSpot)
- Create custom objects: subscription requirements (HubSpot Knowledge Base)
- Marketing Hub Enterprise pricing: required onboarding (HubSpot)
- What Jetty can build (Jetstack AI documentation)
HubSpot changes often. Spotted something out of date? Tell us at team@jetstack.ai.