StackLift
Integration · CRM & ERP

HubSpot integration: cost, timeline and how it works.

A HubSpot integration connects HubSpot's CRM, marketing, and service tools to your product, website, billing, or ERP so contacts, deals, and activity stay in sync. It usually means a private app token or OAuth app, API calls for records, webhook subscriptions for changes, and a mapping of your custom properties. Effort depends on custom properties, sync direction, and volume.

From the estimate

What a HubSpot integration adds to a project

StackLift's free estimate prices every integration by the engineering it takes. These are its numbers for a typical setup; your data, volumes and edge cases move them.

Typical effort

28 hours

About 4 working days of engineering

Catalog group

CRM

Contacts, deals, companies, forms, and marketing event sync.

The complete guide

HubSpot integration: the complete guide

Updated November 18, 2026 · Published by , Founder, StackLift AI. Written with AI assistance; how we make content.

Short answer

A HubSpot integration connects HubSpot's CRM, marketing, and service tools to your product, website, billing, or ERP so contacts, deals, and activity stay in sync. It usually means a private app token or OAuth app, API calls for records, webhook subscriptions for changes, and a mapping of your custom properties. Effort depends on custom properties, sync direction, and volume.

What does a HubSpot integration do?

HubSpot holds contacts, companies, deals, tickets, and marketing activity. An integration keeps that data aligned with the other places your business runs, so marketing, sales, and support see the same customer.

  • Create or update HubSpot contacts when someone signs up or buys in your product.
  • Sync deals and lifecycle stages with your billing or order system.
  • Send product usage events to HubSpot so sales can follow up at the right moment.
  • Create support tickets from your app and keep their status in sync.
  • Pull HubSpot lists and segments into your own admin or email tooling.
  • Write form and campaign source data into your reporting.

How does a HubSpot integration work?

HubSpot offers a REST API with objects for contacts, companies, deals, tickets, and custom objects, plus search and batch endpoints. You authenticate in one of two ways. A private app gives a token for a single HubSpot account and fits an integration built for your own business. An OAuth app is needed when the integration will be used by many accounts.

For changes, HubSpot can send webhook notifications to a URL you host, and workflows can call your endpoint too. Your receiver should verify the request signature, answer quickly, and process the work in a queue. Check HubSpot's current developer documentation for which subscription types each app type supports, because this has changed over time.

HubSpot lets you create developer test accounts, so you can build and test without touching your live portal. Rate limits depend on app type and subscription tier, so confirm the current figures in HubSpot's documentation. For API basics, see the API glossary entry.

What data moves, and in which direction?

HubSpot is often the source for marketing data and the destination for product data. Mark an owner for each property.

Typical HubSpot data flows
DataDirectionHow often
Contacts from sign-ups and formsInto HubSpotReal time
Company and deal recordsBoth ways, one system as ownerReal time or every few minutes
Lifecycle stage and lead statusOut of HubSpotOn change
Product usage and purchase eventsInto HubSpotReal time or hourly
Support ticketsBoth waysOn change
Lists and segmentsOut of HubSpotDaily

What drives the effort of a HubSpot integration?

A single form-to-contact flow is small. The work grows with these factors.

  • Custom properties and custom objects, each needing a mapping and type check.
  • Association rules between contacts, companies, and deals.
  • Duplicate contacts and how you match on email or an external ID.
  • Existing HubSpot workflows that react to changes your integration makes.
  • Data volume and the first backfill.
  • Two-way sync, with conflict rules and loop prevention.
  • Retries, queues, and alerting for failed calls.
  • Consent and unsubscribe status, which must never be overwritten by mistake.

The typical effort shown above is a baseline. A portal with many workflows and custom properties costs more to integrate safely than a clean one.

Common HubSpot integration pitfalls and how to avoid them

HubSpot integrations tend to fail in the details around tokens, limits, and automation.

  • Regenerated or revoked tokens: when a private app token is regenerated, every service using the old one stops until it is updated.
  • OAuth reauthorization: adding new scopes can require users to approve the app again, so request what you need up front.
  • Rate limit errors: use batch endpoints and back off when you receive a throttling response.
  • Workflow collisions: an integration update can trigger a HubSpot workflow that emails someone. Test with a copy first.
  • Overwriting marketing consent: treat opt-out fields as read-only unless the change is deliberate.
  • Missed webhooks: add a reconciliation job that compares recent records, so a dropped event heals itself.

Should you build a custom HubSpot integration or use a connector?

HubSpot has a large set of ready connectors, and Zapier and Make both connect to it. Start there when the flow is simple.

Ready connector or custom integration
QuestionReady connector or iPaaSCustom integration
Best forForm-to-contact, alerts, simple syncsCustom objects, volume, business rules
Duplicate and conflict handlingBasicDesigned for your data
Error handling and retriesBasicQueues, alerts, replay
Ongoing cost shapePer task or subscription tierOne-time build plus upkeep
Ownership of logicIn the vendor's toolIn your code

If your flow touches billing or an ERP, a custom integration is usually safer. See the iPaaS glossary entry for the trade-offs.

How do you test and launch a HubSpot integration?

Test against a safe copy of the system first, and move to live data only when the checks below pass.

  1. Build in a HubSpot developer test account or a sandbox.
  2. List every property, its type, and which system owns it.
  3. Run the backfill on a copy and compare record counts.
  4. Switch off or review workflows that could send email on test data.
  5. Test an expired token, a rate limit response, and a duplicate contact.
  6. Verify webhook signatures and the queue behind them.
  7. Enable logging and alerts, then release to a small segment.
  8. Keep a rollback step ready.

How does StackLift scope a HubSpot integration?

A HubSpot integration is scoped feature by feature in the free estimate, then reviewed by a senior architect before it becomes a commitment. Discovery covers which objects sync, which system owns each property, and which workflows already run in your portal. Scope and budget are agreed before engineering begins. See the CRM and ERP cost guide.

Agents work on feature branches and never push to the default branch or touch production secrets. CI/CD, observability and rollback are in the plan from sprint one, so a bad release of the integration can be reversed. Start a free estimate and add HubSpot as a feature to see the cost, timeline and team.

Questions people ask

How long does a HubSpot integration take?

A one-way contact sync can be quick. Custom objects, two-way sync, and a backfill add time. The effort above is a baseline, and a free estimate gives a timeline for your scope.

Should I use a private app or an OAuth app?

Use a private app for an integration built for your own HubSpot account. Use an OAuth app when many customers will connect their own accounts.

Can HubSpot send data to my app in real time?

Yes, through webhook subscriptions or workflow actions that call your endpoint. Your endpoint should verify signatures and queue the work.

Can I integrate HubSpot with my ERP or accounting tool?

Yes. Deals, companies, and invoices are the usual objects. See the QuickBooks and NetSuite pages for the accounting side.

Can AI be added to HubSpot data?

Yes. A language model can summarize contact history or draft follow-ups from HubSpot records. See LLM integration.

What happens if the integration fails?

A well-built one queues failed calls, retries them, and alerts someone. A reconciliation job then catches anything that slipped through.

Sources

Official HubSpot documentation

The vendor's own reference for the APIs, limits and authentication this guide describes. Check it for the current version before you build.