Salesforce Nonprofit Cloud to HubSpot
Salesforce's nonprofit CRM built on the core platform, with Person Accounts and fundraising objects such as Gift Transactions, Gift Commitments and Gift Designations.
Salesforce Nonprofit Cloud data can move into HubSpot, landing mainly in Sales Hub. 2 of 10 mapped objects move directly (Account (Organization) and Case); 5 items need manual work and 3 do not move. Plan roughly 3-6 weeks for a small move and 12-24 weeks for a large one.
Migration checklist for Salesforce Nonprofit 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 constituents, <100k gifts
Reference-only gifts, CSV import.
Mid migration
25k-250k constituents, 100k-1M gifts
Custom objects, household logic, parallel run.
Large migration
>250k constituents, >1M gifts
Integration with finance system, API-based loads.
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 Nonprofit Cloud: what you need to get in, what lands in HubSpot, and what will not.
Salesforce REST/SOAP/Bulk APIs with SOQL; Nonprofit Cloud fundraising objects are exposed as sObjects (API v59.0+)
Salesforce user with API Enabled. Fundraising objects also need the Fundraising Access license and Fundraising User permission.
For the HubSpot integration: API Enabled, View Setup and Configuration, and Modify All on synced objects. For export: Read on the records.
Choose your route
How will you move the data?
HubSpot offers an integration for importing records from Salesforce Nonprofit Cloud.
- You need: Salesforce user with API Enabled. Fundraising objects also need the Fundraising Access license and Fundraising User permission.
- Permission: For the HubSpot integration: API Enabled, View Setup and Configuration, and Modify All on synced objects. For export: Read on the records.
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
- Built-in Data Export (CSV per object; Data Loader cannot export attachments, so use the weekly export)
- Reports export
- sf CLI data query
- HubSpot-Salesforce integration sync
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: 12-24 weeks, usually phased.
Talk to a partnerWhere each object lands
In Salesforce Nonprofit Cloud
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Account (Person Account, individual) | Contacts | partial | Person Accounts combine account and contact fields, so split them into Contacts. Keep the Salesforce ID in a custom property. |
| Account (Organization) | Companies | yes | Import Companies before Contacts and Deals to keep associations. |
| Account (Household) | Companies | manual | HubSpot has no household object. Use a Company with a household type property or a Custom object. Analyst judgment. |
| Gift Transaction / Opportunity | Deals | partial | Load as Deals or a Custom object for reference only. The DonorId lookup points to an Account. Gift accounting stays in the source or finance system. |
| Gift Commitment (recurring) | Custom objects | manual | There is no native HubSpot equivalent for recurring gift commitments. |
| Gift Designation / Fund | Custom objects | manual | Keep fund references as properties or a custom object. |
| Membership (custom or package objects) | Custom objects | manual | Membership structures are customer-specific, so check the org's schema. |
| Campaign / Campaign Member | Custom objects | manual | Campaign member history does not map to contact timelines automatically. |
| Task / Event / Notes | Tasks, Meetings, Notes | partial | Historical activity import is limited. |
| Case | Tickets | yes | Recreate ticket pipelines first. |
What to expect
Automation does not migrate and must be rebuilt as HubSpot workflows.
HubSpot has no native equivalent. Per the scope note, retain these in Salesforce or a finance system.
Data Loader cannot export attachments, so use the weekly export.
Gift Soft Credit and household relationships have no direct HubSpot object.
Gift, fund and membership data needs a custom schema.
Salesforce automation and pipeline logic do not carry over.
Owner IDs differ between the two systems.
HubSpot copies are references and must tie back to the finance system.
Keep a system of record for gift accounting and load only reference or summary data.
Define dedupe rules, keep the Salesforce ID in a custom property, and import in order.
Export Campaign Member data and recreate it as a custom object or properties.
Confirm the export user has the Fundraising Access license and Fundraising User permission.
Store the Salesforce 18-character ID in a unique HubSpot property.
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, API objects) and the HubSpot Salesforce integration are backed by docs. Nonprofit-specific mappings (households, memberships, grants), rate limits, residency and certifications rest on category-level analyst knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate Salesforce Nonprofit Cloud to HubSpot?
1. Inventory the org: new Nonprofit Cloud (Person Accounts, Gift objects) or legacy NPSP, and any custom membership objects. 2. Confirm the export user has API Enabled and the Fundraising Access license and Fundraising User permission. 3. Decide which gift, fund and grant data stays in Salesforce or finance, and which moves as reference. 4. Create HubSpot custom properties and objects, including a unique Salesforce ID property.
What data can move from Salesforce Nonprofit Cloud to HubSpot?
These objects move directly: Account (Organization) and Case. Check the mapping table for partial and manual items.
What does not move from Salesforce Nonprofit Cloud to HubSpot?
Flows, Process Builder and automation, Gift accounting ledgers, restricted fund balances, tax receipting and grant administration and Attachments through Data Loader. Plan to rebuild or retire these.
How long does a Salesforce Nonprofit Cloud to HubSpot migration take?
Small (<25k constituents, <100k gifts): 3-6 weeks. Mid (25k-250k constituents, 100k-1M gifts): 6-12 weeks. Large (>250k constituents, >1M gifts): 12-24 weeks. These are planning estimates, not a quote.
What access do I need to export from Salesforce Nonprofit Cloud?
Salesforce user with API Enabled. Fundraising objects also need the Fundraising Access license and Fundraising User permission. For the HubSpot integration: API Enabled, View Setup and Configuration, and Modify All on synced objects. For export: Read on the records.
Is there a native HubSpot connector for Salesforce Nonprofit Cloud?
Yes. Confirm the supported objects in discovery.
What compliance issues apply when moving Salesforce Nonprofit Cloud data?
Check: Financial (donation and payment data), Possible minors' data, Possible health-related data for some charities and Tax receipting records. Agree consent, retention and access rules before exporting.
Moving Salesforce Nonprofit 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