25 Best HubSpot Integrations in 2026: Native Apps, Custom Builds and How to Choose

For most teams, the list of best HubSpot integrations is short: a CRM or ERP sync, an enrichment tool, your support desk, your store or billing system, and a messaging layer. The hard part is figuring out which of these can be done with a marketplace app and which need a custom build. This guide answers that question.

As a HubSpot Custom Integration Accredited, HubSpot Diamond Solutions Partner, we have been building HubSpot integrations since 2013. We’ve connected 300+ platforms to HubSpot and process over 20 billion records a year for our clients. So the notes below are from scoping, building and fixing these connections and watching where they break.

We’ll give you the 25 HubSpot integrations we’d recommend in 2026, sorted by team. And you’ll get the five ways to connect HubSpot to other systems, a decision framework for picking one, real cost tiers, and the failure modes that quietly break syncs.

Something before the list. This year has seen many changes to HubSpot’s developer platform. In March 2026, HubSpot migrated its REST APIs to date-based versions such as /2026-03/ and in April, its remote MCP server entered general availability. Any guide you’re reading that’s still talking about API keys or v1 endpoints is hopelessly out of date.

What is a HubSpot integration?

A HubSpot integration is a connection that transfers data between HubSpot and another system, either in real time or on a schedule. Most HubSpot integrations do three things: Sync records like contacts, companies, deals and tickets Trigger actions across tools Show outside data inside the HubSpot CRM

Some install in minutes from the HubSpot App Marketplace. Other companies need HubSpot integration services such as API authentication, field mapping, error handling and monitoring. It is contingent upon the amount of data you have, how many systems need to agree on the same record and how much it costs you when the sync is wrong.

How many HubSpot integrations are there?

HubSpot’s App Marketplace currently lists well over 1,700 apps, and third-party counts have it above 2,000 recently. Any system that has an API can also be connected using a custom build, so the practical limit is your engineering budget, not the marketplace.

HubSpot itself is big enough to pull vendors in. The company reported 306,446 customers as of June 30, 2026. The most-installed apps are the ones you’d expect:

• Gmail: about 533,000 installs
• Google Calendar: about 309,000 installs
• Outlook: about 248,000 installs
• HubSpot connector for Claude: about 212,000 installs
• Zapier: about 170,000 installs, connecting HubSpot to 8,000+ apps

Install counts tell you what’s hot. They don’t tell you what’s in your stack. Consider the native Salesforce app, for example. It has around 19,000 installs, but is one of the most customized connections we see in mid-market accounts. Browse every platform we’ve connected with our catalog of 300+ HubSpot integrations.

for HubSpot

Turn HubSpot Into A Real-Time SMS Engine with
Message IQ

Two-Way Conversations



Shared Team Inbox



Automation Triggers



Advanced Reporting



Compliance Tools



Two-Way Conversations



Shared Team Inbox



Automation Triggers



Advanced Reporting



Compliance Tools

• 98%
  SMS read within 3 min
• 78%
  Buy from first responder
• 21×
  More likely to qualify

Proven results

98% open rate
·
3–5 min avg response
·
$45–$50 ROI / $1

Explore Message IQ

*MessageIQ is an IntegrateIQ product – built natively for HubSpot by the same team.

The 5 ways to connect HubSpot

Five ways to connect HubSpot to another system Most companies end up using three or four at once, and that’s fine. The problems begin when a team tries to make one method do a job intended for the other.

1. Native apps from the App Marketplace

Native integrations are pre-built apps listed in the HubSpot App Marketplace. HubSpot builds some of them, and technology partners build the rest. Setup usually takes minutes through an OAuth install flow.

Best for: standard tools with standard data, such as Gmail, Slack, Zoom, Google Ads and Stripe.

Limits: you get the fields, sync direction and logic the app developer chose. If the app doesn’t sync a custom property or a custom object, you can’t add that yourself.

2. Data Hub data sync

Data Hub (formerly Operations Hub) includes a two-way data sync engine that works with 100+ apps in HubSpot’s data sync collection. The free tier syncs default fields. Paid tiers add custom field mappings, historical sync and filtering, and Data Hub Enterprise adds two-way sync with Snowflake, BigQuery and AWS S3.

Best for: teams that need more control than a native app gives, without writing code. Common pairings include Mailchimp, Pipedrive and Microsoft Dynamics.

Limits: it only works with apps in the data sync collection, and it maps fields one to one. It won’t run multi-step business logic or reshape data on the way through.

3. Middleware and iPaaS

Middleware platforms such as Zapier, Make and Workato sit between HubSpot and another app. A trigger in one system fires an action in the other.

Best for: low-volume automations, quick tests, and tools that have no native app.

Limits: per-task pricing climbs with volume, most recipes run on polling schedules rather than true real time, and error handling is shallow. Once you need calculations, conditional mapping or several systems agreeing on one record, recipes get fragile. We cover that trade-off in detail in Zapier vs. custom integration.

4. Custom API integrations

A custom integration calls HubSpot’s REST API from your own infrastructure, authenticated through a private app or OAuth. It can sync any object, including custom objects, apply your business rules, and move millions of records with proper queuing and retries.

Best for: mid-market and enterprise teams with ERPs, custom objects, proprietary systems, real-time needs, or 10,000+ records changing each day.

Limits: higher upfront cost, and someone has to own it as APIs change. HubSpot now ships new API versions twice a year, in March and September, so a custom build needs a maintenance plan from day one.

5. AI agents and MCP connections

The latest way to connect HubSpot is with AI tools. On April 13, 2026, HubSpot launched its remote MCP (Model Context Protocol) server. MCP-compatible AI clients, like Claude, can access and manipulate CRM data via a HubSpot-hosted link at mcp.hubspot.com, secured with OAuth 2.1 and PKCE. It honors the existing HubSpot permissions for each user.

Best for: conversational access to CRM data, such as meeting prep, quick pipeline questions and research.

Limits: It’s designed for ad hoc questions and small updates, not bulk data movement. It is driven by the CRM search API and does not support access to activity records for accounts with sensitive data enabled. Your nightly ERP sync should still run on the REST API.

How the five methods compare

How to choose the right HubSpot integration

Choose the lightest method that solves the problem for the next 12 to 24 months. Heavier options cost more and take longer, so don’t build custom when a native app does the job. But don’t stack middleware recipes on a revenue-critical sync either.

We walk every client through the same five questions:

1. Is there a native app that syncs the fields you need? If yes, install it and move on.
2. Do you need custom field mapping or historical backfill for a supported app? Use Data Hub data sync.
3. Is it a low-volume automation between tools with no native app? Use Zapier, Make or Workato.
4. Do you have custom objects, multi-step business logic, or 10,000+ records changing a day? Plan a custom API integration.
5. Is the other system on-premise, behind a firewall, or a legacy ERP without a modern API? Custom is the only realistic option, because middleware can’t reach systems it can’t call.

If two of these questions point to custom, stop trying to stretch middleware into the role. A brittle Zapier setup that breaks every quarter usually costs more over two years than a build done right once.

Here’s how the framework plays out in practice:

• A SaaS company connecting HubSpot, Stripe and Slack. Both have solid native apps. Total setup is under an hour, and the only cost is the subscriptions.
• A B2B manufacturer connecting HubSpot to Epicor with customer-specific pricing. No native app covers it, and the pricing logic is too complex for middleware. This is a custom build of about eight weeks.
• A marketing team syncing HubSpot and Mailchimp with custom fields. The native app covers basics. Custom field needs move it into Data Hub data sync.
• A staffing firm running Bullhorn and Greenhouse. Greenhouse has a workable native app. Bullhorn usually needs a custom connection for placements and job orders.

If you have a dozen apps running already, do an audit before adding any more. List out every connected app, what it writes to HubSpot, what properties it owns, and who gets the alert when it fails. Teams that do this often find that two or three apps are writing to the same fields, or that an old middleware recipe is still running against a process that changed a year ago. First clean that up, and each new integration is easier to test.

The 25 best HubSpot integrations in 2026

We grouped these HubSpot integrations by team. For each one, you’ll see what it does, who it’s for, and whether the native app is usually enough or a custom build is common. Where we’ve built deeper versions, we link to our integration page.

Sales and prospecting

1. Salesforce

The HubSpot Salesforce integration is the connection mid-market teams ask us about most. HubSpot’s native app runs an automatic two-way sync of contacts, companies, deals and activities, and it works well on clean Salesforce instances. It struggles when either side has custom objects, complex opportunity stages or non-standard lifecycle rules.

• Usual approach: native app first, custom logic for enterprise data models
• Best for: companies running HubSpot for marketing and Salesforce for sales, or moving between the two

2. LinkedIn Sales Navigator

The HubSpot LinkedIn integration brings Sales Navigator profiles, InMail activity and relationship signals into HubSpot records. Reps can research and engage prospects without leaving the CRM.

• Usual approach: native
• Best for: outbound B2B and account-based sales teams

3. ZoomInfo

The HubSpot ZoomInfo integration enriches contacts and companies with verified phone numbers, firmographics and intent data, and it can push new prospects into HubSpot lists.

• Usual approach: native
• Best for: mid-market and enterprise sales teams prospecting at volume

4. Apollo

The HubSpot Apollo integration combines enrichment with sequences, so teams get data and outreach in one tool. Sequence activity and engagement sync back to HubSpot.

• Usual approach: native
• Best for: teams that want enrichment and engagement without two separate contracts

5. Outreach

The HubSpot Outreach integration syncs prospects, sequences, calls and email activity in both directions. Managers report from one source while SDRs keep working in Outreach.

• Usual approach: native
• Best for: sales orgs with dedicated SDR teams

6. Clay

The HubSpot Clay integration pulls data from many providers, runs AI research on each account, and writes the results back to HubSpot properties. It’s become a common layer in 2026 outbound stacks.

• Usual approach: native, sometimes with light API work to control which properties it can overwrite
• Best for: RevOps teams building enrichment and research workflows

Marketing and advertising

7. Google Ads

The HubSpot Google Ads integration ties ad clicks to contacts and deals, sends conversion events back to Google for bidding, and builds audiences from HubSpot lists.

• Usual approach: native
• Best for: any team spending on Google Ads

8. LinkedIn Ads

The LinkedIn Ads app syncs Lead Gen Form submissions into HubSpot, connects ad spend to pipeline, and builds matched audiences from your CRM.

• Usual approach: native
• Best for: B2B advertisers

9. Mailchimp

The HubSpot Mailchimp integration syncs audiences, engagement and unsubscribe status. It suits teams that keep Mailchimp for newsletters while HubSpot stays the system of record.

• Usual approach: native, or Data Hub data sync when you need custom field mapping
• Best for: companies running two email programs or moving off Mailchimp

10. Typeform

The HubSpot Typeform integration maps form answers, including hidden fields, into HubSpot contact properties.

• Usual approach: native
• Best for: marketing teams running quizzes, surveys and lead gen forms

Customer service and support

11. Zendesk

The HubSpot Zendesk integration links tickets to contacts and companies, so sales can see open issues before a renewal call. Many mid-market teams extend it past the native app to sync ticket fields, SLAs or custom objects.

• Usual approach: native, custom common
• Best for: companies running support in Zendesk and everything else in HubSpot

12. Intercom

The HubSpot Intercom integration sends chat conversations and lead data into HubSpot timelines. It’s a strong fit for SaaS companies with product-led growth motions.

• Usual approach: native
• Best for: SaaS, product-led and customer success teams

13. Aircall

The HubSpot Aircall integration adds click-to-call, automatic call logging and recordings to HubSpot records. CloudTalk, JustCall and Dialpad are solid alternatives, especially if you want AI call summaries built into the dialer.

• Usual approach: native
• Best for: inside sales and support teams with steady call volume

E-commerce and payments

14. Shopify

The HubSpot Shopify integration syncs customers, orders, products and abandoned carts. The native app works well for standard stores. Custom builds come in for B2B pricing, custom checkouts or several stores feeding one portal.

• Usual approach: native, custom for B2B and multi-store setups
• Best for: DTC brands and smaller B2B stores

15. Magento (Adobe Commerce)

The HubSpot Magento integration handles customers, orders, inventory, tiered B2B pricing and quote requests. In our experience, the native options rarely cover B2B Magento stores.

• Usual approach: custom
• Best for: B2B and enterprise e-commerce

16. BigCommerce

The HubSpot BigCommerce integration syncs customer, order and product data. Standard stores do fine with the native app; B2B Edition stores usually need custom work.

• Usual approach: native, custom for B2B
• Best for: mid-sized e-commerce brands

17. Stripe

The HubSpot Stripe integration brings payments, subscriptions and billing details into HubSpot, which makes renewal workflows and revenue reporting possible.

• Usual approach: native
• Best for: SaaS and subscription businesses

Finance and ERP

18. QuickBooks

The HubSpot QuickBooks integration connects deals to invoices, customers and payments, so sales can see what’s been paid without asking finance.

• Usual approach: native, custom for complex billing or multi-entity books
• Best for: SMB and lower mid-market teams

19. NetSuite

The HubSpot NetSuite integration is almost always a custom build. NetSuite’s custom records, subsidiaries and saved searches don’t line up with HubSpot’s standard objects. Done well, it gives sales, finance and marketing one view of the customer, from quote through invoice.

• Usual approach: custom, about eight weeks
• Best for: mid-market and enterprise companies running NetSuite as their ERP

20. Microsoft Dynamics 365

The HubSpot Dynamics 365 integration is a common dual-stack build. Data Hub data sync covers basic account and contact flows. Sales orders, quotes and complex pipeline mapping need custom work.

• Usual approach: Data Hub data sync or custom
• Best for: mid-market and enterprise teams on the Microsoft stack

21. SAP

The HubSpot SAP integration links HubSpot with SAP ECC or S/4HANA for customer master data, order status and billing. There’s no meaningful native path for most SAP environments.

• Usual approach: custom
• Best for: enterprise companies with SAP as the system of record

Data and BI

22. Snowflake

The HubSpot Snowflake integration moves CRM data into your warehouse for BI and modeling, and can push modeled data, like health scores, back into HubSpot. Data Hub Enterprise includes two-way Snowflake sync; custom pipelines handle heavier transforms.

• Usual approach: Data Hub Enterprise or custom
• Best for: data teams that report across HubSpot, ERP and product usage

Communication and collaboration

23. Slack

The HubSpot Slack integration sends deal changes, ticket alerts and notifications to channels, and lets teams manage records and ask Breeze questions from Slack.

• Usual approach: native
• Best for: any team that lives in Slack

24. Microsoft Teams

The HubSpot Microsoft Teams integration does the same job for Microsoft 365 companies, with meeting scheduling and record lookups inside Teams.

• Usual approach: native
• Best for: companies standardized on Microsoft 365

25. Message IQ (two-way SMS for HubSpot)

Message IQ is our own product. We built it because SMS was the integration our clients kept asking for. It runs two-way texting inside HubSpot records and the shared inbox, triggers texts from workflows on contacts, deals, tickets and companies, and reports delivery events natively in HubSpot. Carrier compliance checks are built in.

• Usual approach: native, built for HubSpot
• Best for: teams that need appointment reminders, sales follow-ups or service updates by text
• Pricing: from $49/month, month-to-month, with every feature on every plan

When to use a custom integration vs. a native connector

Use a custom integration when the native connector can’t represent your data correctly or can’t keep up with it. Across 300+ platforms, these are the triggers we see most:

• Custom objects. HubSpot Enterprise supports HubSpot custom objects such as subscriptions, projects or equipment. Most native apps don’t know they exist.
• Two-way sync with conflict rules. When both systems can edit the same field, you need explicit rules for which side wins. Native apps usually pick one direction.
• Near real-time requirements. Inventory, pricing and order status often can’t wait for a 15-minute polling cycle.
• High volume. Once 10,000+ records change each day, per-task middleware pricing and rate limits start to bite.
• On-premise or legacy systems. ERPs on private networks and homegrown order systems need secure, custom access patterns.
• Several HubSpot portals. Multi-brand companies and post-merger groups often run more than one portal, and most native apps connect to one.
• Real data transformation. Splitting fields, lookup tables, calculated values and conditional mapping are beyond field-to-field sync.

If your stack hits two or more of these, plan for custom from the start. Retrofitting a custom build after a year of middleware patches costs more than doing it once.

Common HubSpot integration failures and how to prevent them

Most integration failures are quiet. A sync stops, the error sits unread in a log for weeks, and then the pipeline report is wrong. These are the patterns we fix most often when teams ask us about fixing broken HubSpot integrations:

1. Token refresh failures. OAuth access tokens are short-lived and HubSpot returns their lifetime in the expires_in field. Integrations that don’t refresh on schedule stop syncing without an apparent error. Create refresh logic, retries and alerts from day one.
2. Rate limit throttling. Privately distributed apps get 100 requests in 10 seconds on Free and Starter, 190 on Professional and Enterprise. Daily limits are 250,000 to 1,000,000 requests per account. Marketplace OAuth apps receive 110 requests per 10 seconds per account. Integrations that pass testing often receive 429 errors under production load. Use batch endpoints, cache and queues. Fixes. Our guide to HubSpot API rate limiting.
3. Webhook gaps. Some changes, such as certain bulk imports, don’t fire the webhooks you’d expect. Pair webhooks with scheduled polling and a daily reconciliation job.
4. Last-write-wins conflicts. Without field ownership rules, two systems overwrite each other. Decide which system owns each field, then enforce it.
5. Field mapping mismatches. Date formats, character limits and dropdown values that don’t match cause records to fail one at a time. Test with real edge cases: nulls, special characters and time zones.
6. Outdated API versions. HubSpot retired API keys in 2022, and it now releases date-based API versions every March and September. Each integration needs an owner who tracks the changelog and upgrades on schedule.
7. Heavy work inside workflow code actions. Custom code actions have strict execution limits. Move long jobs to external infrastructure.
8. No monitoring. Every integration should have error alerts, a dashboard and a runbook. We ship all three with every build.
9. Ungoverned AI agents. Breeze agents and MCP-connected tools can now write to deals and contacts. Scope their permissions, log their changes and review them on a schedule. Our Breeze agent data readiness checklist is a good place to start.

What HubSpot integrations cost

HubSpot integration costs fall into four tiers, and the cheapest one is often the right one:

Plan for maintenance on custom builds at about 10% to 20% of the build cost per year. That covers HubSpot’s API version updates, changes on the other system, and new fields as your process evolves.

We price custom work on an outcome-based, fixed basis. After discovery, you get one number for the scoped result, not an hourly meter. You can get a working range in about a minute with our integration cost estimate, and our breakdown of the hidden costs of HubSpot integrations shows where budgets usually slip.

How we build a custom HubSpot integration in 8 weeks

Our typical custom build goes from kickoff to go-live in eight weeks. Here’s how those weeks break down:

1. Weeks 1 and 2: Discovery and architecture. We map every system, object and business rule in scope, and interview sales, marketing, operations and finance. You sign off on a written architecture document before we write code.
2. Weeks 3 to 5: Build and field mapping. Engineers set up authentication, build the sync logic, add type validation and error handling, and backfill historical data.
3. Weeks 6 and 7: Testing and user acceptance. We run the integration against real data in staging and test deletes, conflicting updates, network failures and rate limit responses. Your team signs off on how it behaves.
4. Week 8: Go-live and handoff. We cut over to production, turn on monitoring and hand over the runbook. Post-launch support is included, not sold separately.

This process is a big reason we keep a 98.5% client retention rate, and our integrations sync about 7 million fields a day across client accounts. Read the full rundown of our HubSpot integration process.

HubSpot integration stacks by industry

The right stack depends on what you sell and how you sell it. These are the patterns we build most:

• Manufacturing. HubSpot plus an ERP such as Epicor, SAP or NetSuite, often with inventory and CPQ. Reps need pricing and stock inside deals, and finance needs invoices flowing back. See our Epicor case study and our work in manufacturing.
• B2B e-commerce. HubSpot plus Magento or BigCommerce, Stripe, a help desk and an ERP. Negotiated pricing, account-level catalogs and order approvals push most of these builds into custom.
• Field service. HubSpot plus RealGreen or FieldRoutes, QuickBooks and scheduling. Marketing runs in HubSpot, routes and service records live in the field service system, and billing closes the loop. More on this in lawn care and pest control.
• Staffing and recruiting. HubSpot plus Avionté or Bullhorn, with candidates as contacts and job orders as deals. Our Avionté case study walks through one build.
• Financial services and healthcare. These need audit logging and strict separation of regulated data, which most native apps don’t provide. Custom builds with compliance controls are the norm.

If you’re consolidating systems before you connect them, our CRM migration services handle the move and the integrations in one plan.

FAQ

How many integrations does HubSpot have?

HubSpot’s App Marketplace has more than 1,700 apps, and recent third-party counts put it over the 2,000 mark. Any system with an API can also connect via a custom integration. Most installed apps: Gmail, Google calendar, Outlook, HubSpot connector for Claude and Zapier.

Are HubSpot integrations free?

Most native marketplace apps are free to download, but you still pay for the integrated tool. The Data Hub data sync for default fields and custom mappings is free on paid tiers. Middleware is priced on volume of tasks, and custom integrations are a one-time build and ongoing maintenance.

What is the difference between a native and a custom HubSpot integration?

A native integration is an app from the HubSpot App Marketplace that is pre-built, installs in minutes, and syncs the fields its developer has chosen. A custom integration based on the HubSpot REST API for your specific data model. Custom is needed when you have custom objects, complex business rules, high volume or systems the marketplace doesn’t support.

Does HubSpot integrate with Salesforce?

Yes. HubSpot’s native Salesforce app runs an automatic two-way sync of contacts, companies, deals and activities. Enterprise teams often add custom logic for custom objects, complex opportunity stages and lifecycle rules. If you’re deciding between the platforms, see our HubSpot vs Salesforce comparison.

What is the best HubSpot integration for e-commerce?

Depends on your platform Shopify’s native app is good for regular stores. Tiered pricing, quotes and multi-store setups often require custom builds for Magento and B2B BigCommerce stores.

How long does it take to build a custom HubSpot integration?

Most mid-market custom integrations take 6-12 weeks, and our typical delivery is 8 weeks from kickoff to go-live. This is discovery, build, testing and training. For large builds with multiple systems and custom objects, it can take 12 to 16 weeks.

Do I need Data Hub (Operations Hub) for HubSpot integrations?

No. Native marketplace apps work on all HubSpot tiers and custom integrations don’t require Data Hub either. Data Hub adds data sync with custom field mapping, programmable automation, and, on Enterprise, two way data warehouse sync.

Can Claude or ChatGPT connect to HubSpot?

Yes. In general availability since April 2026, HubSpot’s remote MCP server allows MCP-compatible AI tools to read and write CRM data within each user’s existing permissions. There is also a dedicated HubSpot connector for Claude with over 200,000 installs.

Can HubSpot integrate with a legacy ERP?

Yes, through a custom API integration. Legacy and on-premise ERPs such as Epicor, SAP ECC, Sage and Dynamics GP can connect if they expose an API or can be reached through a secure gateway. For NetSuite specifically, see our HubSpot NetSuite integration service.

Free ROI Calculator

See your 12-month revenue impact with HubSpot CRM

Enter your current numbers — visitors, leads, deal size — and get a personalized projection based on real HubSpot customer benchmarks.

Calculate My ROI

Get your HubSpot integrations scoped by a Diamond Partner

Most HubSpot integration issues stem from the wrong tool for the job: middleware pushed past its limits, or a native app that can’t see your real data. Either way you’re paying for it in broken syncs, manual clean up, and reports your leadership team stops trusting.

If you’re not doing a standard marketplace install, talk to an engineer first. We’ll scope your integration in 30 minutes, tell you honestly if you need custom and if you do, deliver it in about 8 weeks at a fixed price. We have integrated 300+ platforms, process over 20 billion records per year and have a 98.5% client retention.

{
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
        {
            "@type": "Question",
            "name": "How many integrations does HubSpot have?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "HubSpot offers over 1,500 apps in the App Marketplace and more than 2,000 companies in its App Partner Program
building new connectors. Any system with an API can also be integrated through a custom integration, making the
practical limit effectively unlimited."
            }
        },
        {
            "@type": "Question",
            "name": "Are HubSpot integrations free?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "Most native marketplace integrations are free to install, although subscriptions for connected tools are
separate. Operations Hub Data Sync is included with Operations Hub Professional and above. Middleware platforms such as
Zapier and Workato charge based on usage, while custom integrations are typically one-time engineering investments."
            }
        },
        {
            "@type": "Question",
            "name": "What is the difference between a native and a custom HubSpot integration?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "A native integration is a pre-built connector available through the HubSpot App Marketplace and can be
installed quickly. A custom integration is built using HubSpot APIs and external infrastructure to support custom
objects, complex business logic, or systems not covered by marketplace apps."
            }
        },
        {
            "@type": "Question",
            "name": "Does HubSpot integrate with Salesforce?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "Yes. The native HubSpot-Salesforce integration supports bi-directional synchronization of contacts, companies,
opportunities, and activities. Enterprise implementations often require additional customization for custom objects,
lifecycle stages, and advanced deal-stage mapping."
            }
        },
        {
            "@type": "Question",
            "name": "What is the best HubSpot integration for e-commerce?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "The best integration depends on the e-commerce platform being used. Shopify offers a strong native integration
with HubSpot, while Magento and BigCommerce often require custom integrations for advanced B2B requirements such as
custom pricing, quote workflows, and multi-store environments."
            }
        },
        {
            "@type": "Question",
            "name": "How long does it take to build a custom HubSpot integration?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "A typical mid-market custom HubSpot integration takes between 6 and 12 weeks. Standard projects are often
delivered in 8 weeks, including discovery, development, testing, and training. More complex enterprise integrations may
take 12 to 16 weeks."
            }
        },
        {
            "@type": "Question",
            "name": "Can HubSpot integrate with my legacy ERP?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "Yes. HubSpot can integrate with legacy and on-premise ERP systems through custom API integrations or secure
middleware layers. This includes platforms such as Epicor, SAP ECC, Sage, Dynamics GP, and NetSuite."
            }
        },
        {
            "@type": "Question",
            "name": "Do I need Operations Hub for HubSpot integrations?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "No. Native marketplace integrations are available across HubSpot tiers. Operations Hub provides additional
capabilities such as advanced bi-directional data sync, custom-coded workflow actions, and programmable automation, but
it is not required for most integrations."
            }
        }
    ]
}

Tim Ritchie

CEO of Integrate IQ

An admitted HubSpot fanboy, Tim has been in the HubSpot ecosystem as a consumer of the platform from the beginning. Tim believes that Message IQ’s success begins and end with the success of our customers and partners.