Salesforce Health Cloud to HubSpot
Salesforce Health Cloud is a healthcare CRM built on the Salesforce platform. It models patients and members as person accounts and adds provider, care plan, and health insurance data models.
Salesforce Health Cloud data can move into HubSpot, landing mainly in Sales Hub. 1 of 8 mapped objects move directly (Account (Business record type) – provider organizations); 4 items need manual work and 2 do not move. Plan roughly 3-5 weeks for a small move and 10-20 weeks for a large one.
Migration checklist for Salesforce Health Cloud
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<25k contacts
Enquiry and referral data only.
Mid migration
25k-250k
Adds appointments, custom objects and sensitive properties.
Large migration
250k+
Multi-org, heavy custom schema and compliance review.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Salesforce Health Cloud: what you need to get in, what lands in HubSpot, and what will not.
Salesforce platform APIs (REST, Bulk API / Bulk API 2.0, SOQL)
Salesforce login with API access (API is included in Enterprise, Unlimited and Developer editions); a security token is needed where MFA is enforced.
Data Loader returns only data the user has read access to, so use a user with read access to all in-scope objects and fields.
Choose your route
How will you move the data?
No native connector was found.
- You need: Salesforce login with API access (API is included in Enterprise, Unlimited and Developer editions); a security token is needed where MFA is enforced.
- Permission: Data Loader returns only data the user has read access to, so use a user with read access to all in-scope objects and fields.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Data Loader export to CSV via SOQL; Data Loader does not support nested queries or child-object queries
- Data Export Wizard (scheduled, raw CSVs, limited standard objects)
- Bulk API 2.0 and Workbench
- dataloader.io and Skyvia
- SFDX CLI queries
- Reports (capped at 100,000 rows)
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 10-20 weeks, usually phased.
Talk to a partnerWhere each object lands
In Salesforce Health Cloud
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Person Account (Account, Person record type) – patients/members | Contacts | partial | Move only permitted enquiry and engagement fields; PHI needs HubSpot sensitive properties on an Enterprise plan. |
| Account (Business record type) – provider organizations | Companies | yes | Business-record-type accounts represent provider organizations. |
| Healthcare Provider (references person account via AccountId) | Custom objects | partial | There is no standard HubSpot equivalent; it needs a custom object or a Company/Contact mapping. |
| Lead / Opportunity | Deals | partial | Standard Salesforce objects that can be exported with SOQL; map referral source to a deal or contact property. |
| Appointments (scheduling objects) | Custom objects | manual | HubSpot's sensitive-data API lists an Appointments object, but I did not verify Health Cloud appointment object names or how they map. |
| Task / Event / EmailMessage / Note | Tasks | partial | These are exportable with Data Loader or SFDX; notes, emails and meetings need separate mapping. |
| Case | Tickets | partial | Case relationships are not preserved in raw exports and need manual joins. |
| ContentDocument (files) | Files | manual | Data Loader does not natively support files; Bulk API returns base64 only. |
What to expect
Out of scope per the analyst boundary: retain them in Salesforce or the EHR.
It exports raw CSVs with IDs only and no preserved relationships.
Person accounts combine account and contact in one record.
Data Loader cannot query child objects, and joins are manual.
HubSpot does not know which fields hold PHI.
They are automation and config and are not exported as data.
Sign the BAA, enable Sensitive Data, flag PHI properties, and strip PHI from notes before import.
Confirm the edition before scoping; keep PHI in Salesforce or the EHR otherwise.
Choose the data center before enabling HIPAA.
Keep Salesforce IDs as HubSpot properties and use them for association imports.
Use selective sync or exclude fields.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Export paths (Data Loader, SOQL, Bulk API) and Health Cloud's person-account model are supported by Salesforce docs, and HubSpot Sensitive Data docs are cited. The Salesforce API auth, rate limits, Health Cloud-specific object mapping and certifications were not checked against vendor docs and rest on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate Salesforce Health Cloud to HubSpot?
1. Inventory Health Cloud objects and tag each as migrate, retain, or archive. 2. Confirm HubSpot Enterprise, a signed BAA and Sensitive Data settings. 3. Create an integration user with read access and API enabled; get its security token. 4. Define the permitted field list (enquiry, referral source, appointments, preferences) and exclude clinical fields.
What data can move from Salesforce Health Cloud to HubSpot?
These objects move directly: Account (Business record type) – provider organizations. Check the mapping table for partial and manual items.
What does not move from Salesforce Health Cloud to HubSpot?
Clinical records, EHR-linked data, care plans, diagnosis/procedure codes and insurance coverage and Relational integrity from the native Data Export Service. Plan to rebuild or retire these.
How long does a Salesforce Health Cloud to HubSpot migration take?
Small (<25k contacts): 3-5 weeks. Mid (25k-250k): 6-10 weeks. Large (250k+): 10-20 weeks. These are planning estimates, not a quote.
What access do I need to export from Salesforce Health Cloud?
Salesforce login with API access (API is included in Enterprise, Unlimited and Developer editions); a security token is needed where MFA is enforced. Data Loader returns only data the user has read access to, so use a user with read access to all in-scope objects and fields.
What compliance issues apply when moving Salesforce Health Cloud data?
Check: HIPAA/PHI, Health/medical data, Possible minors' data and Insurance/financial data. Agree consent, retention and access rules before exporting.
Moving Salesforce Health Cloud into HubSpot?
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