Base CRM to HubSpot
Base CRM was rebranded Zendesk Sell, a sales CRM for leads, contacts, deals and pipelines. Zendesk has announced its retirement.
Base CRM data can move into HubSpot, landing mainly in Sales Hub. 5 of 9 mapped objects move directly (Contacts (people), Leads, Deals and Notes); 3 items need manual work and 2 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Base CRM
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 records
CSV import only
Mid migration
10k-100k records
Adds API extraction of activities
Large migration
100k+ records
Heavy activity history and documents
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 Base CRM: what you need to get in, what lands in HubSpot, and what will not.
REST (Core, Sync, Firehose and Search APIs) at api.getbase.com
OAuth access token (or API key for scripts) for a Sell user.
Admins can run the account export. Admins can also grant export permission to all users for smart list exports.
Choose your route
How will you move the data?
No native connector was found.
- You need: OAuth access token (or API key for scripts) for a Sell user.
- Permission: Admins can run the account export. Admins can also grant export permission to all users for smart list exports.
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.
- Account Export CSV (Settings > Data > Export) covering leads, contacts, deals, notes, tasks
- Smart list export, which also returns the Parent Company fields
- Sales CRM API for data the CSV omits (calls, emails, documents, etc.)
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-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Base CRM
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts (people) | Contacts | yes | In the CSV export. Company ID may be dropped where it differs from the contact's value. |
| Contacts (organizations) | Companies | partial | The full export omits Parent Company and Parent Company ID. Use a smart list export to get them. |
| Leads | Contacts | yes | Leads are exported. Map them to Contacts with a lead status or lifecycle stage. |
| Deals | Deals | yes | Deals are in the export. Pipelines and stages are available through the API. |
| Notes | Notes | yes | In the CSV export and the API. |
| Tasks | Tasks | yes | In the CSV export and the API. |
| Calls | Calls | partial | Call logs are not in the CSV. They are available through the API, and call recordings can be downloaded with scripts. |
| Emails, appointments, documents | Emails / Meetings / Files | manual | Not in the CSV. They need the API and custom scripting. |
| Users/owners, pipelines | Owners / Deal pipelines | manual | Rebuild owners and pipelines in HubSpot, then map by name or email. |
What to expect
Zendesk states the export does not cover them.
No export route was found. Rebuild them in HubSpot.
The CSV excludes them.
These are not portable.
The full export omits it.
Export early and archive the files.
Complete the API extraction before cancelling.
Download and verify the files immediately.
Reconcile companies and contacts using smart list exports.
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 and API are backed by Zendesk docs and secondary guides. HubSpot-side mapping, rate limits and governance certifications were not verified, so those rest on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate Base CRM to HubSpot?
1. Audit the objects, custom fields, pipelines and users in Sell. 2. Confirm you have an admin account, and enable export for all users if needed. 3. Obtain OAuth credentials for api.getbase.com. 4. Check whether your Sell plan includes API access (one third-party guide says Growth or higher).
What data can move from Base CRM to HubSpot?
These objects move directly: Contacts (people), Leads, Deals, Notes and Tasks. Check the mapping table for partial and manual items.
What does not move from Base CRM to HubSpot?
Activity history, appointments, emails, call logs and documents via CSV and Automations, permissions and reports. Plan to rebuild or retire these.
How long does a Base CRM to HubSpot migration take?
Small (<10k records): 2-4 weeks. Mid (10k-100k records): 4-8 weeks. Large (100k+ records): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Base CRM?
OAuth access token (or API key for scripts) for a Sell user. Admins can run the account export. Admins can also grant export permission to all users for smart list exports.
What compliance issues apply when moving Base CRM data?
Check: Call recordings may need consent evidence. Agree consent, retention and access rules before exporting.
Moving Base CRM 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