Dex to HubSpot
Personal CRM that consolidates contacts from LinkedIn, email, calendar and messaging, with a timeline of notes, reminders and custom fields per contact.
Dex data can move into HubSpot, landing mainly in Sales Hub. 1 of 6 mapped objects move directly (Contacts); 3 items need manual work and 2 do not move. Plan roughly 1-2 weeks for a small move and 4-8 weeks for a large one.
Migration checklist for Dex
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
<5k contacts
CSV import only.
Mid migration
5k-25k contacts plus notes
Notes association and company creation.
Large migration
25k+ contacts, team or enterprise use
API scripts, reminders 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 Dex: what you need to get in, what lands in HubSpot, and what will not.
REST API (OpenAPI spec) plus MCP server
Dex API key, or OAuth login, for the account being exported.
Account owner. API and MCP access require a Dex Professional subscription.
Choose your route
How will you move the data?
No native connector was found.
- You need: Dex API key, or OAuth login, for the account being exported.
- Permission: Account owner. API and MCP access require a Dex Professional subscription.
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.
- CSV export of all contacts
- CSV export of all timeline notes/events
- CSV export of LinkedIn Sync network updates
- REST API reads of contacts, notes, reminders, tags, groups and custom fields
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: 4-8 weeks, usually phased.
Talk to a partnerWhere each object lands
In Dex
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts | Contacts | yes | CSV includes name, title, email, phone, birthday, social URLs, groups and custom fields. Keep the Dex Id as a reference. |
| Company (text field on contact) | Companies | partial | Company is exported as a field on the contact, not as a separate record. Companies must be created and associated in HubSpot by matching on name or domain. |
| Timeline notes/events | Notes | partial | Events CSV carries note text, event type, dates and ContactIds, so each can be associated to a contact by Dex Id. The Events CSV has no email or meeting bodies. |
| Reminders | Tasks | partial | Reminders are readable via the API, not in the CSV export. |
| Groups/tags | Contacts | partial | Groups are exported as a contact column. Map them to a multi-select property or a list. |
| Deals/pipelines | Deals | no | No deal or pipeline objects were found in the Dex docs, and a third-party review says Dex has no sales stages. Deals must be built new in HubSpot. |
What to expect
The export covers notes/events only, so these would need re-syncing in HubSpot.
No owner or team permission data appears in the CSV export fields.
Dex does not model these objects.
Keep-in-touch frequency is exported as a field only, not as automation.
These are Dex source connections and do not transfer.
Deduplicate in Dex before export, then import to HubSpot keyed on email.
Import the Dex Id as a custom property.
Use CSV export when the plan is lower.
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 and API are backed by Dex's own docs and site. Dex is a personal CRM with no deals, pipelines or companies objects. HubSpot import mapping is category-level knowledge, and no HubSpot connector was found.
Sources
Related migrations
Frequently asked questions
How do I migrate Dex to HubSpot?
1. Export contacts, events and network updates CSVs from the Dex Export page. 2. Confirm the plan tier if API extraction (Professional) is wanted. 3. Inventory custom fields and groups, and decide on matching HubSpot properties. 4. Decide whether any Dex users or teams need HubSpot owners (Enterprise team features).
What data can move from Dex to HubSpot?
These objects move directly: Contacts. Check the mapping table for partial and manual items.
What does not move from Dex to HubSpot?
Synced email, calendar and message history as native HubSpot Emails/Meetings and Automation, owners and permissions. Plan to rebuild or retire these.
How long does a Dex to HubSpot migration take?
Small (<5k contacts): 1-2 weeks. Mid (5k-25k contacts plus notes): 2-4 weeks. Large (25k+ contacts, team or enterprise use): 4-8 weeks. These are planning estimates, not a quote.
What access do I need to export from Dex?
Dex API key, or OAuth login, for the account being exported. Account owner. API and MCP access require a Dex Professional subscription.
What compliance issues apply when moving Dex data?
Check: Personal relationship notes may contain sensitive data and Birthdays and personal contacts are imported without a clear lawful basis. Agree consent, retention and access rules before exporting.
Moving Dex 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