Where to begin
Where to begin a HubSpot migration
Start with access: which systems expose an API, which need a private app or credentials, what can move and where the risk sits.
Method
What to settle first
- Who owns an admin login on the source system?
- Is there an API, a private app or only a file export?
- Which objects land in HubSpot, which are manual, which stay behind?
- Which risks need a decision before any data moves?
By platform
Find your system
Open a category, or filter by platform name.
Horizontal CRM4
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Salesforce Sales Cloud | OAuth 2.0 flows (Bulk API 2.0) | Yes |
| Microsoft Dynamics 365 Sales | To confirm | Yes |
| Zoho CRM | OAuth 2.0 (authorization code grant, 1-hour access tokens, refresh tokens) | Yes |
| Pipedrive | Personal API token (query parameter or header), OAuth 2.0 authorization code flow | To confirm |
Real estate CRM3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Follow Up Boss | HTTP Basic Auth with API key as username and blank password | To confirm |
| Wise Agent | OAuth 2.0 | To confirm |
| Top Producer | To confirm | To confirm |
Lending, wealth & insurance CRM3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Salesforce Financial Services Cloud | OAuth (via the HubSpot Salesforce integration) | Yes |
| Microsoft Cloud for Financial Services | Microsoft Entra ID (OAuth 2.0) | Yes |
| Redtail CRM | OAuth credentials (per integration vendor description; not confirmed in vendor docs) | No |
Admissions & enrollment3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Salesforce Education Cloud | Salesforce login with security token or MFA (Data Loader), Connected app / OAuth (assumed from the platform; not confirmed in the sources) | Yes |
| Ellucian CRM Recruit | Ellucian-provisioned service or API account in the ADADMIN domain (per partner guide) | No |
| Ellucian CRM Advise | To confirm | To confirm |
Patient acquisition & engagement3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Salesforce Health Cloud | Salesforce username and password, plus security token where MFA is required (Data Loader) | To confirm |
| Microsoft Cloud for Healthcare | To confirm | To confirm |
| Veeva CRM | To confirm | To confirm |
Recruitment CRM & ATS3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Bullhorn | OAuth 2.0 authorization code flow, BhRestToken session key, exchanged from the access token via /rest-services/login | Yes |
| Vincere | To confirm | To confirm |
| Recruit CRM | API token (Bearer) | No |
Professional services & legal CRM3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Clio Grow | OAuth 2.0 Authorization Code (Clio Platform developer app with client_id/client_secret) | To confirm |
| Lawmatics | OAuth 2.0 | To confirm |
| Law Ruler | Secret API key (Setup > 3rd Party Integrations > API Key) | To confirm |
Industry sales & booking systems3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| VinSolutions | API key plus per-dealer authorization, OAuth 2.0 (partner-reported) | To confirm |
| DealerSocket | To confirm | To confirm |
| Elead CRM | Fortellis client_id and client_secret, Per-dealer Subscription-Id, Request-Id correlation header | To confirm |
Nonprofit & membership CRM3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Salesforce Nonprofit Cloud | Salesforce username and password plus security token (Data Loader), OAuth via the HubSpot-Salesforce integration | Yes |
| Blackbaud Raiser’s Edge NXT | OAuth 2.0, API subscription key | No |
| Blackbaud CRM | To confirm | To confirm |
Marketing automation & email3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Adobe Marketo Engage | OAuth 2.0 (Bearer token in Authorization header) | To confirm |
| Oracle Eloqua | HTTP Basic Authentication, OAuth 2.0 (2-legged and 3-legged) | To confirm |
| Salesforce Marketing Cloud Account Engagement | Salesforce OAuth 2.0 (Connected App) bearer token, Pardot-Business-Unit-Id header | Yes |
ABM, advertising & social3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| 6sense | HubSpot OAuth (6sense side, 'Sign in with HubSpot'), Legacy HubSpot API key / private app access key (being migrated to OAuth) | Yes |
| Demandbase | JWT, API token (Account Connector) | Yes |
| Terminus | To confirm | Yes |
Forms, events & conversion3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Typeform | Personal access token (Bearer), OAuth 2.0 | Yes |
| Jotform | API key (APIKEY header or apiKey query param) | Yes |
| Formstack | Personal Access Token (V2025 API), OAuth 2.0 (earlier v2 API, per third-party profiles) | Yes |
Customer support & help desk3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Zendesk Support | API token, OAuth | No |
| Freshdesk | API key sent as the Basic Auth username, with X as the password | Yes |
| Intercom | Access token (own workspace), OAuth 2.0 (public apps) | To confirm |
ITSM, contact centre & field support3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| ServiceNow ITSM | Basic auth, OAuth bearer token | To confirm |
| Jira Service Management | Basic auth with email and API token, OAuth 2.0 (3LO), Connect/Forge app auth | To confirm |
| Freshservice | API key via HTTP Basic Auth (key as username, any string as password) | To confirm |
Customer success, feedback & knowledge3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Gainsight | API access key (accesskey header), OAuth 2.0 bearer token (Connectors 2.0) | Yes |
| ChurnZero | To confirm | Yes |
| Totango | API token (personal access token from the user profile) | Yes |
CPQ, proposals & sales documents3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Salesforce CPQ | OAuth bearer token (Salesforce connected app) | No |
| Salesforce Revenue Cloud | To confirm | Yes |
| Oracle CPQ | HTTP Basic (per legacy docs) | To confirm |
Billing, subscriptions, payments & accounting3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Stripe Billing | Restricted API key (rk_), Secret API key (sk_), Organisation API key (sk_org_), HTTP Basic Auth with the key as username | Yes |
| Stripe Payments | API keys over HTTP Basic Auth (restricted rk_, secret sk_), Organisation API keys (sk_org_), Workload Identity Federation (short-lived tokens) | Yes |
| Chargebee | HTTP Basic auth with API key as username and empty password | Yes |
Revenue intelligence & sales engagement3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Clari | API key (Revenue API), X-Api-Key plus X-Api-Password headers (Copilot API) | To confirm |
| Gong | Basic auth (Access Key + Secret), OAuth | Yes |
| Revenue.io | To confirm | To confirm |
Integration & workflow automation3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Zapier | OAuth 2.0 (Workflow API), Account login for UI export | No |
| Make | API token (Authorization: Token header), OAuth 2.0 | Yes |
| n8n | API key sent in X-N8N-API-KEY header, Enterprise plans: scoped API keys | Yes |
Customer data, enrichment & data quality3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Twilio Segment | Public API bearer token, Source write key (Tracking API), HubSpot Private App token or OAuth for the HubSpot destination | Yes |
| mParticle | OAuth2 client credentials bearer token via the SSO token endpoint, API key/secret for outputs | To confirm |
| RudderStack | To confirm | Yes |
Warehouses, databases & analytics3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Snowflake | OAuth (Snowflake OAuth / External OAuth), Key-pair (JWT), Programmatic access token, Username/password via drivers (SSO/MFA options) | Yes |
| Databricks | Personal access token, OAuth access token, Microsoft Entra ID token (Azure), Service principal tokens (recommended for automation) | No |
| Google BigQuery | Google service account generated by HubSpot and granted roles in your GCP project | Yes |
Agent builders & conversational AI3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Salesforce Agentforce | External client apps issuing tokens for the Agent API, OAuth (assumed from Salesforce platform standard) | No |
| Microsoft Copilot Studio | Microsoft Entra ID (Power Platform environment access) | To confirm |
| Google Vertex AI Agent Builder | Google Cloud IAM (project-level permissions) | No |
CMS & website builders3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| WordPress | Application Passwords (HTTP Basic, core since 5.6), Cookie + nonce (same-origin only), JWT (plugin), OAuth (plugin) | Yes |
| WordPress.com | To confirm | Yes |
| Drupal | HTTP Basic (per tutorial), Cookie/session, Other auth modules such as OAuth (not verified here) | No |
Headless CMS, content operations & SEO3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Contentful | CMA management token (the CLI takes it via –management-token) | No |
| Sanity | API token (bearer) | To confirm |
| Strapi | API token (Bearer), Users & Permissions JWT, Transfer token (CLI strapi transfer only) | No |
Ecommerce, learning & customer portals3
| Platform | API and auth | HubSpot connector |
|---|---|---|
| Shopify | App access token sent in the X-Shopify-Access-Token header (OAuth for apps) | Yes |
| Shopify Plus | Per-shop Admin API access token (X-Shopify-Access-Token), App install via OAuth or token exchange | Yes |
| Adobe Commerce | OAuth 1.0a integration (consumer key/secret, access token/secret), Admin bearer token (4h default), Customer token (1h default), Adobe IMS OAuth 2 server-to-server (Commerce as a Cloud Service) | Yes |
Quick answers
Frequently asked questions
Where do I start a HubSpot migration?
Start with how data leaves the source system: API, private app, credentials or file export, then decide what moves, what is manual and what stays.
Talk to a partner
Want a partner to run this move?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner