folk to HubSpot
Lightweight relationship CRM with people, companies and deals held in groups, plus a REST API and Zapier/Make integrations.
folk data can move into HubSpot, landing mainly in Sales Hub. 3 of 8 mapped objects move directly (People (contacts), Companies and Notes); 4 items need manual work and 3 do not move. Plan roughly 1-2 weeks for a small move and 6-10 weeks for a large one.
Migration checklist for folk
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
up to 5k contacts
CSV-led, few groups.
Mid migration
5k-50k contacts
API for associations, deals and some activities.
Large migration
50k+ contacts
Full API extraction, many groups, heavy 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 folk: what you need to get in, what lands in HubSpot, and what will not.
REST (JSON) at https://api.folk.app/v1
An API key created in workspace Settings > API.
600 requests per minute per user, shared across that user's API keys. A burst policy of 20 requests per 2 seconds also appears in the docs. A 429 response carries a Retry-After header.
Choose your route
How will you move the data?
No native connector was found.
- You need: An API key created in workspace Settings > API.
- Permission: To confirm
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.
- Group-level 'Export view as CSV' produces a zip with contacts and notes CSVs.
- The export covers only the displayed columns and applied filters.
- There is no whole-workspace export, so export group by group.
- Use the REST API for fuller extraction of people, companies and deals.
- Third-party paid exporter services exist, but they are not vendor-supported.
Limits: 600 requests per minute per user, shared across that user's API keys. A burst policy of 20 requests per 2 seconds also appears in the docs. A 429 response carries a Retry-After header.
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-10 weeks, usually phased.
Talk to a partnerWhere each object lands
In folk
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| People (contacts) | Contacts | yes | Export by group via CSV or API, then dedupe across groups on email. |
| Companies | Companies | yes | Available via API. The CSV export excludes the 'people in the company' view, so association export needs the API. |
| Deals | Deals | partial | The API lists deals per group and returns linked companies, people and custom field values such as status, value, close date and assignee. Pipeline and stage mapping to HubSpot is rebuilt manually. |
| Notes | Notes | yes | Included in the group CSV export as a separate file. |
| Interactions (emails, meetings, calls) | Emails | partial | Excluded from the CSV export. A secondary source says the Interactions API endpoint was still private beta as of June 2025. Verify the current state. |
| Reminders | Tasks | manual | Excluded from the CSV export. The API route was not verified. |
| Users/owners | Contacts | manual | Assignee values are referenced by user id or email. Map them to HubSpot owners manually. |
| Groups | Custom objects | manual | Groups act like lists or segments. Map them to HubSpot lists or properties. |
What to expect
They are explicitly excluded from the export.
They are excluded from the CSV export.
A secondary source says it is not stored natively.
Automations do not export. Secondary sources name rebuilding them as the main switching cost.
The export and API return data, not configuration. This is an analyst assumption.
Export is per group and contacts can sit in several groups.
The CSV excludes the contact custom field, so display all fields in the view first or use the API.
Pull interactions through the API if available to your plan, or archive them separately.
Extract associations via the API using the people, companies and deals ids.
Confirm API availability on your folk plan before scoping. One secondary source says API access is Premium.
Honour Retry-After and use exponential backoff.
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, REST API, auth and rate limits are backed by folk docs. The object-to-HubSpot mapping, interactions coverage, permissions and certifications rest on analyst judgement or secondary sources. No native HubSpot connector was confirmed.
Sources
Related migrations
Frequently asked questions
How do I migrate folk to HubSpot?
1. Inventory all groups, custom fields and views in folk. 2. Confirm your plan includes API access and generate an API key under Settings > API. 3. Decide how each folk group maps to HubSpot lists, properties or deal pipelines. 4. List the Zapier/Make automations that touch folk.
What data can move from folk to HubSpot?
These objects move directly: People (contacts), Companies and Notes. Check the mapping table for partial and manual items.
What does not move from folk to HubSpot?
Interactions and reminders via the CSV export, Strongest connection and group smart fields and Full email thread content synced from Gmail/Outlook. Plan to rebuild or retire these.
How long does a folk to HubSpot migration take?
Small (up to 5k contacts): 1-2 weeks. Mid (5k-50k contacts): 3-6 weeks. Large (50k+ contacts): 6-10 weeks. These are planning estimates, not a quote.
What access do I need to export from folk?
An API key created in workspace Settings > API.
What compliance issues apply when moving folk data?
Check: Contacts scraped via LinkedIn or social tools may carry GDPR lawful-basis concerns. and Notes may contain sensitive data.. Agree consent, retention and access rules before exporting.
Moving folk 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