SalesNOW to HubSpot
Cloud and mobile CRM with contacts, companies, leads, deals, custom fields and activities.
SalesNOW data can move into HubSpot, landing mainly in Sales Hub. 2 of 7 mapped objects move directly (Contacts and Companies/Accounts); 3 items need manual work and 2 do not move. Plan roughly 2-3 weeks for a small move and 8-14 weeks for a large one.
Migration checklist for SalesNOW
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
<10k
Spreadsheet-based move.
Mid migration
10k-100k
Includes association repair and some activity work.
Large migration
>100k
API extraction and a heavy rebuild are likely.
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 SalesNOW: what you need to get in, what lands in HubSpot, and what will not.
REST (JSON, optionally XML)
A user with Export access is required for UI exports. The scope of data exported depends on that user's data access level.
Choose your route
How will you move the data?
No native connector was found.
- You need: To confirm
- Permission: A user with Export access is required for UI exports. The scope of data exported depends on that user's data access level.
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.
- Export to Excel from the main tabs (Contacts, Companies and others) and from Advanced Search results
- Export selected records using checkboxes
- REST API (JSON/XML) mentioned on the consulting page; endpoint coverage is not confirmed
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: 8-14 weeks, usually phased.
Talk to a partnerWhere each object lands
In SalesNOW
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts | Contacts | yes | Exports to Excel from the Contacts tab, then imports to HubSpot as a CSV or XLSX file. |
| Companies/Accounts | Companies | yes | Exports from the Companies tab; association to contacts must be checked in the export. |
| Deals | Deals | partial | SalesNOW has Deals and customizable sales stages. Whether deals export from the UI with their stage and owner is unconfirmed. |
| Leads | Contacts | partial | Leads are a separate SalesNOW object. They would map to Contacts with a lifecycle stage or lead status; the mapping is analyst judgement. |
| Activities (calls, tasks, notes) | Notes | manual | Export coverage for activity history is not documented. Test whether it can be exported, or pull it through the API. |
| Users/owners | Contacts | manual | Owner names exported in the files must be matched to HubSpot users. |
| Custom fields | Custom objects | partial | Unlimited custom fields exist. They would be recreated as HubSpot properties before import. |
What to expect
They are not exportable as data and have to be rebuilt in HubSpot.
File export is not documented, so they probably need to be downloaded manually and uploaded to HubSpot Files.
Customizable sales stages need to be recreated.
Per scope note; no export path is documented.
Spreadsheet exports may omit relationship keys.
Add a shared key, such as an exported ID or company name, and test the join on a sample.
Ask SalesNOW support for a full data dump or API access.
Confirm API availability and authentication with the vendor in writing.
Run exports as a user with full-team scope.
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.
Vendor pages confirm the product, the UI export to Excel and a REST API. They do not document API auth, rate limits, the export field set or how activities and associations are exported. Object mapping rests on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate SalesNOW to HubSpot?
1. Ask SalesNOW to confirm Export access for an admin user and the API availability for your account. 2. List custom fields across contacts, accounts, leads and deals, then create the matching HubSpot properties. 3. Document the pipeline stages, owners and automations to rebuild. 4. Run a trial Excel export from each tab and check which columns carry IDs and relationships.
What data can move from SalesNOW to HubSpot?
These objects move directly: Contacts and Companies/Accounts. Check the mapping table for partial and manual items.
What does not move from SalesNOW to HubSpot?
Automation rules, permissions/data-access levels and reports and Documents (2GB storage). Plan to rebuild or retire these.
How long does a SalesNOW to HubSpot migration take?
Small (<10k): 2-3 weeks. Mid (10k-100k): 4-8 weeks. Large (>100k): 8-14 weeks. These are planning estimates, not a quote.
What access do I need to export from SalesNOW?
A user with Export access is required for UI exports. The scope of data exported depends on that user's data access level.
Moving SalesNOW 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