Notion CRM templates to HubSpot
CRM built from Notion databases and templates. Contacts, companies, deals and activities are user-defined databases linked by Relations and Rollups.
Notion CRM templates data can move into HubSpot, landing mainly in Sales Hub. 2 of 8 mapped objects move directly (Contacts database and Companies/Accounts database); 5 items need manual work and 2 do not move. Plan roughly 1-2 weeks for a small move and 6-12 weeks for a large one.
Migration checklist for Notion CRM templates
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 6 doneAfter
0 of 6 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
under 5k records, 2-3 databases
CSV and import wizard.
Mid migration
5k-50k records, 5-10 databases with relations
API extraction and association load.
Large migration
50k+ records, many relations, files and notes
Throttled extraction and heavy 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 Notion CRM templates: what you need to get in, what lands in HubSpot, and what will not.
REST JSON API (Notion API) with no bulk export endpoint; database query is paginated by cursor
Integration token, with each CRM database shared with the integration. Alternatively, a workspace member who can export.
Workspace owner or admin to create integrations and run a workspace export. Exact rules by plan are not confirmed.
<cite index="10-1">Average of 3 requests per second per integration</cite>. Overages return HTTP 429, so handle Retry-After and backoff. Payloads are limited to 1,000 blocks and 500KB per request.
Choose your route
How will you move the data?
No native connector was found.
- You need: Integration token, with each CRM database shared with the integration. Alternatively, a workspace member who can export.
- Permission: Workspace owner or admin to create integrations and run a workspace export. Exact rules by plan are not confirmed.
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.
- Database export to CSV (Markdown & CSV) from the UI
- Workspace export as ZIP (Markdown/CSV, HTML)
- API extraction to JSON
- Third-party extraction tools such as Apify actors
Limits: <cite index="10-1">Average of 3 requests per second per integration</cite>. Overages return HTTP 429, so handle Retry-After and backoff. Payloads are limited to 1,000 blocks and 500KB per request.
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: 6-12 weeks, usually phased.
Talk to a partnerWhere each object lands
In Notion CRM templates
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts database | Contacts | yes | A flat database exports to CSV and can use the HubSpot import wizard. Notion page IDs need to be kept as a reference property. |
| Companies/Accounts database | Companies | yes | Import companies first, then rebuild the links as associations. |
| Deals/Pipeline database | Deals | partial | Stage and status properties must be mapped to a HubSpot pipeline. Board views must be rebuilt. |
| Relations and Rollups | Associations / calculated properties | partial | The CSV flattens relations. The API is needed to preserve them. Rollups become calculated properties. |
| Page body content (notes, meeting notes) | Notes | partial | Content exports as Markdown files. Loading it as Notes takes custom API work. |
| Activity/Tasks databases | Tasks | manual | Activities are custom databases, so mapping to Tasks, Calls or Meetings is analyst judgement. |
| Files & media properties | Files | partial | Files must be downloaded and re-uploaded because Notion file URLs expire. |
| Person property (owner) | Contact/Deal owner | manual | Match Notion users to HubSpot users by email. |
What to expect
They have no HubSpot equivalent and must be rebuilt as workflows, views and dashboards.
CSV export carries no history. I found no source showing the API exposes row-level change history.
Notion automations, buttons and third-party Zaps do not migrate.
Notion page and database sharing differs from CRM object permissions.
Notion views and rollups are not portable.
The CSV drops relations and page content, so check them against the API output.
Notion properties are schema-free and often inconsistent.
Use API-led extraction for anything relational and reconcile record and association counts.
Queue requests, back off on 429, and cache the schema.
Download files at extraction time and upload them to HubSpot Files.
Dedupe on email and domain before import.
Check the HubSpot tier before designing the target model.
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 the rate limit rest on third-party migration guides (ClonePartner and others). I did not open Notion's or HubSpot's own docs, so access and object mapping are not vendor-verified. Object mapping is analyst judgement because a template CRM has no fixed schema.
Sources
Related migrations
Frequently asked questions
How do I migrate Notion CRM templates to HubSpot?
1. Inventory every database in the CRM template and its Relations and Rollups. 2. Create a Notion internal integration and share each CRM database with it. 3. Map each database to a HubSpot object and list the properties to create. 4. Add a Notion page ID property to use as an external key.
What data can move from Notion CRM templates to HubSpot?
These objects move directly: Contacts database and Companies/Accounts database. Check the mapping table for partial and manual items.
What does not move from Notion CRM templates to HubSpot?
Notion automations, buttons and database views (Board, Calendar, Timeline) and Edit history and activity audit trail. Plan to rebuild or retire these.
How long does a Notion CRM templates to HubSpot migration take?
Small (under 5k records, 2-3 databases): 1-2 weeks. Mid (5k-50k records, 5-10 databases with relations): 3-6 weeks. Large (50k+ records, many relations, files and notes): 6-12 weeks. These are planning estimates, not a quote.
What access do I need to export from Notion CRM templates?
Integration token, with each CRM database shared with the integration. Alternatively, a workspace member who can export. Workspace owner or admin to create integrations and run a workspace export. Exact rules by plan are not confirmed.
Is there a native HubSpot connector for Notion CRM templates?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving Notion CRM templates data?
Check: Free-text notes may contain health, financial or minors' data depending on the business. Agree consent, retention and access rules before exporting.
Moving Notion CRM templates 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