Nimble to HubSpot
Relationship-focused CRM for small businesses and teams. It covers contacts, companies, deals, activities, email marketing and sequences.
Nimble data can move into HubSpot, landing mainly in Sales Hub. 2 of 7 mapped objects move directly (People and Company contacts and Deals); 4 items need manual work and 2 do not move. Plan roughly 1-3 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Nimble
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 contacts, <1k deals
CSV-led import.
Mid migration
10k-100k contacts, 1k-10k deals
API pull for notes and associations.
Large migration
>100k contacts, >10k deals
Heavy rate-limit handling and automation rebuild.
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 Nimble: what you need to get in, what lands in HubSpot, and what will not.
REST (v1), OpenAPI contract published
API token generated in Settings > API Token. OAuth apps reportedly need registration via api-support@nimble.com.
Admins grant users API access and bulk export rights in Settings > Users. Third parties report that only admins can generate API keys.
Per-account limits enforced, with HTTP 429 returned. Exact thresholds are not published.
Choose your route
How will you move the data?
No native connector was found.
- You need: API token generated in Settings > API Token. OAuth apps reportedly need registration via api-support@nimble.com.
- Permission: Admins grant users API access and bulk export rights in Settings > Users. Third parties report that only admins can generate API keys.
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.
- Contacts CSV export, emailed to the user (select all via tag, filter or segment)
- Activities export to CSV (tasks, logged calls, events, custom activity types)
- Deals export to CSV
- vCard export
- REST API: contacts, deals, pipelines, fields, notes, tasks
Limits: Per-account limits enforced, with HTTP 429 returned. Exact thresholds are not published.
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-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Nimble
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| People and Company contacts | Contacts, Companies | yes | Records have record_type person or company. Company records list their child persons, which is the basis for associations. |
| Deals | Deals | yes | The CSV export only includes fields editable on the deal's Edit page. Pipelines and stages need to be recreated and mapped in HubSpot. |
| Activities (tasks, logged calls, events) | Tasks, Calls, Meetings | partial | Activities can be exported to CSV. Check that each activity carries its contact and deal association. |
| Notes | Notes | partial | The CSV export excludes notes. The API has contact note endpoints, so notes need a scripted pull. |
| Users/owners | Owners (users) | manual | Team members can be read via the API. Owners must be recreated in HubSpot and matched by email. |
| Email correspondence | Emails | no | The help centre says email correspondence can't be exported. |
| Tags and custom fields | Contact properties, Company properties | partial | Custom fields and field groups are available via the API. Tags have no direct HubSpot equivalent, so map them to properties or lists. |
What to expect
Nimble states it cannot export email correspondence.
No export route found. Rebuild these in HubSpot.
No export path was found for automation definitions.
Nimble permissions are group-based and are set per user.
Reports are not exportable.
CSV exports exclude notes. Association coverage must be audited.
Pull notes through the API and archive emails separately if they are needed.
Use paging, exponential backoff and off-hours runs.
Audit association coverage by comparing record counts and a sample.
Have an admin grant the export and API rights to the migration user.
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 (CSV, API) are backed by Nimble's help centre and API docs. Several API details come from third-party sources. These are the API auth and host details, the undocumented rate limits, and the pipeline and activity coverage. No HubSpot-side docs on Nimble were reviewed, and there is no native HubSpot connector evidence.
Sources
Related migrations
Frequently asked questions
How do I migrate Nimble to HubSpot?
1. Have an admin grant bulk export and API access in Settings > Users. 2. Generate an API token in Settings > API Token for the migration user. 3. Inventory custom fields, tags, deal pipelines and custom activity types. 4. Count people, companies, deals, activities and notes for later reconciliation.
What data can move from Nimble to HubSpot?
These objects move directly: People and Company contacts and Deals. Check the mapping table for partial and manual items.
What does not move from Nimble to HubSpot?
Email correspondence history and Automations, sequences, permissions and reports. Plan to rebuild or retire these.
How long does a Nimble to HubSpot migration take?
Small (<10k contacts, <1k deals): 1-3 weeks. Mid (10k-100k contacts, 1k-10k deals): 3-8 weeks. Large (>100k contacts, >10k deals): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Nimble?
API token generated in Settings > API Token. OAuth apps reportedly need registration via api-support@nimble.com. Admins grant users API access and bulk export rights in Settings > Users. Third parties report that only admins can generate API keys.
What compliance issues apply when moving Nimble data?
Check: Possible health or financial data in free-text notes depending on the customer. Agree consent, retention and access rules before exporting.
Moving Nimble 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