Skip to content
Get a quote

folk to HubSpot migration

Moving from folk CRM to HubSpot Sales Hub gives your team access to HubSpot's native deal pipelines, lifecycle stage tracking, and Breeze AI tooling — but folk's group-centric data model doesn't map one-to-one onto HubSpot's lifecycle-stage-driven contact architecture. We extract every contact, company, deal, and custom field from folk, map group memberships and pipeline positions to HubSpot equivalents, and deliver a test migration with field-level diff before the full run commits your records.

Short answer

FlitStack AI migrates contacts, companies, custom property + static lists, deals and deal stages from folk to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 records.

By

Source folk
DestinationHubSpot
ContactCompanyCustom Property + Static ListDealDeal Stage
Mapped field by field · sample run · one-click rollback

What moves from folk to HubSpot?

folk organizes its CRM around groups — you place contacts into named categories (Leads, Clients, Prospects) and track relationships, notes, and deals per group.

Read the full summary

HubSpot uses lifecycle stage on the contact record itself to drive reporting, automation triggers, and list segmentation, with Deals as a separate object and multiple named pipelines available per portal. The migration maps folk contacts to HubSpot contacts, folk companies to HubSpot companies, and folk deals to HubSpot deals. Group memberships in folk require a decision: HubSpot has no native group equivalent, so we either populate a custom contact property (Group_Membership__c) or build HubSpot lists from group names and assign them as static lists. Pipeline positions in folk map to dealstage on HubSpot deals. Custom fields in folk migrate to HubSpot custom properties (camelCase naming). HubSpot's API ingestion path for contacts uses the Contacts API with property updates via the CRM Lists and Contact Properties API. We run a sample migration of 100–500 records first to surface any pick-list value gaps, lifecycle routing decisions, and custom property creation needs before the full dataset runs. FlitStack does not migrate folk's automation sequences or workflow logic — those are operational constructs that require manual rebuild inside HubSpot's workflow builder.

direct

Contact (person) → Contact

folk person contacts map 1:1 to HubSpot contacts.

How it maps

Email, name, phone, job title, and address fields migrate directly using the HubSpot Contacts API. folk's custom fields attached to a contact become HubSpot custom contact properties created portal-wide. All standard folk contact fields translate to their HubSpot equivalents, and the folk internal record ID is preserved in folk_source_id__c for delta-run de-duplication.

direct

Contact (company) → Company

folk company-type contacts map to HubSpot companies via the Companies API.

How it maps

Company name, domain, industry, employee count, and annual revenue map to HubSpot company properties. folk company records without an email domain are created as HubSpot companies with domain set to a placeholder value to maintain data integrity. The folk company record ID is preserved in folk_source_id__c on the HubSpot company record.

custom_field_required

Group membership → Custom Property + Static List

HubSpot has no native group equivalent.

How it maps

We migrate each folk group name as a custom contact property (Group_Name__c) and create HubSpot static lists named after each group. You choose whether to use the custom property for segmentation or the static list for targeted workflows. Both options are available in the migration deliverable for your team to evaluate.

direct

Deal (within group) → Deal

folk deals inside groups map to HubSpot deals using the Deals API.

How it maps

Deal name, amount, stage, close date, and owner migrate to HubSpot deal properties. The folk group the deal belongs to is preserved in a custom deal property (Source_Group__c) for audit trail and historical reference. folk deal record ID is stored in folk_source_id__c for delta-run tracking.

value_mapping

Pipeline stage (folk group view stage) → Deal Stage

folk pipeline stage names map to HubSpot dealstage values via value_mapping.

How it maps

If folk stages have custom names not matching HubSpot's default pipeline stages, we create a custom HubSpot pipeline with stages matching your folk stage names exactly before data loads. Stage probabilities and forecast categories are mapped to HubSpot deal properties during the pipeline creation process.

direct

Note / Reminder → Engagement (Note)

folk notes and reminders attached to contacts or deals migrate as HubSpot engagements with type 'note' via the Engagements API.

How it maps

Original author and creation timestamp preserved in the engagement record. Rich-text formatting in folk notes is preserved in the engagement body when migrating to HubSpot. Notes are associated to the migrated contact or deal using the associations API.

What moves12 objects
folkHubSpot
  • ContactContact1:1
  • ContactCompany1:1
  • Group membershipCustom Propertytransformed
  • DealDeal1:1
  • Pipeline stageDeal Stagetransformed
  • NoteEngagement1:1

+ 6 more in the mapping below

How folk and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionfolkHubSpot
Record organization modelfolk uses Groups — contacts belong to named categories (Leads, Clients, Partners) with per-group custom fields and pipeline viewsHubSpot uses Lifecycle Stage on the contact record plus separate Deals object; no native group construct — lists serve a similar segmentation purpose
Deal trackingfolk deals exist within group contexts; pipeline view shows deal name, amount, stage, and owner per groupHubSpot Deals are a top-level CRM object with a dedicated pipeline board, stage probability, and forecast category per pipeline
Custom field scopefolk custom fields are created per-group — the same field name can exist independently in different groupsHubSpot custom properties are portal-wide; a custom property created once is available on all applicable object types
Contact-company relationshipfolk treats people and companies as separate contact types within the same object model; a person record can reference a company contactHubSpot has distinct Contact and Company objects with an explicit association; contacts without a company get no-company flag
Email and activity loggingfolk logs email tracking and LinkedIn interactions at the contact level; activities tied to the contact record directlyHubSpot Engagements (calls, emails, meetings, notes) attach to CRM records; email tracking requires the tracking code installed on your email domain
Automation / sequencesfolk sequences use LinkedIn and email automation within the platform; exported as config reference onlyHubSpot has Sequences (Sales Hub paid), Workflows (all tiers), and Breeze AI agents — must be rebuilt from scratch post-migration
Pricing modelfolk charges per seat (Standard $24/user/mo, Premium $40/user/mo) with workspace-wide AI credit capsHubSpot charges per seat plus per-hub (Sales Hub Starter $20/seat, Professional $100/seat) and bills contacts at Marketing Hub tiers

folk to HubSpot field mapping

The 30 most-used fields of 39 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
folkHubSpot
  1. firstnameContact firstnameContact
  2. lastnameContact lastnameContact
  3. emailContact emailContact
  4. phoneContact phoneContact
  5. mobilephoneContact mobilephoneContact
folk fieldHubSpot fieldMappingNote
Contact.firstnameContact.firstnamedirect
Contact.lastnameContact.lastnamedirect
Contact.emailContact.emaildirect
Contact.phoneContact.phonedirect
Contact.mobilephoneContact.mobilephonedirect
Contact.jobtitleContact.jobtitledirect
Contact.addressContact.addressdirect
Contact.cityContact.citydirect
Contact.stateContact.statedirect
Contact.countryContact.countrydirect
Contact.linkedinprofileurlContact.linkedinbiodirectfolk's LinkedIn URL maps to HubSpot's linkedinbio contact property.
Contact.created_atContact.createdatedirect
Contact.updated_atContact.hs_lastmodifieddatedirect
Contact.folkidContact.folk_source_id__ccustom_field_requiredfolk internal record ID stored as a custom property for delta-run de-duplication and traceability.
Contact.group_nameContact.folk_group__ccustom_field_requiredfolk group membership migrates as a custom text property. Used to create HubSpot static lists per group.
Contact.owner_emailContact.hubspot_owner_idtransformedOwner resolved by email match against HubSpot users. Unmatched owners flagged before migration.
Company.nameCompany.namedirect
Company.domainCompany.domaindirect
Company.industryCompany.industryvalue_mappingfolk industry pick-list values mapped to HubSpot company industry pick-list. Unmatched values land as free-text.
Company.numberofemployeesCompany.numberofemployeesdirect
Company.annualrevenueCompany.annualrevenuedirect
Company.created_atCompany.createdatedirect
Company.folkidCompany.folk_source_id__ccustom_field_requiredfolk company record ID preserved on HubSpot for association traceability.
Deal.deal_nameDeal.dealnamedirect
Deal.amountDeal.amountdirect
Deal.stageDeal.dealstagevalue_mappingfolk deal stage names map to HubSpot dealstage values. A custom HubSpot pipeline is created first if folk stages don't match HubSpot defaults.
Deal.closedateDeal.closedatedirect
Deal.owner_emailDeal.hubspot_owner_idtransformedOwner resolved by email match against HubSpot users.
Deal.created_atDeal.createdatedirect
Deal.folkidDeal.folk_source_id__ccustom_field_requiredfolk deal record ID preserved on HubSpot for delta-run de-duplication.

What to watch for in a folk to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

folk groups have no native HubSpot equivalent — group-to-lifecycle routing requires a decision

folk organizes contacts by assigning them to groups — the group is the primary segmentation unit.

How we handle it

HubSpot's lifecycle stage lives on the contact record and drives list membership, workflow triggers, and reporting. Migrating folk groups directly to HubSpot lifecycle stages conflates two different concepts (group assignment vs. buying-stage progression). We surface this by migrating group membership as a custom property and a static list, then your team decides whether folk group names should map to HubSpot lifecycle stages, custom lifecycle properties, or static lists. Mapping every group to a HubSpot lifecycle stage risks having 'Client' and 'Lead' treated as buying stages when they are actually organizational categories. This is a business decision FlitStack cannot make for you — we flag it before the full migration runs.

high

folk per-group custom fields create duplicate HubSpot properties across groups

folk lets you create a custom field scoped to a specific group — 'Status' can exist independently in both the Leads group and the Clients group with different pick-list values.

How we handle it

HubSpot custom properties are portal-wide: there is one 'Status' property on contacts, shared across all workflows and lists. If folk has 'Status' with values 'Hot / Warm / Cold' in one group and 'Active / Churned / Trial' in another, those values conflict in a single HubSpot property. We disambiguate by prefixing: 'Leads.Status' and 'Clients.Status' become two separate HubSpot custom properties. This inflates property count and requires your admin to map the right property into relevant HubSpot workflows post-migration.

medium

folk sequences and automation logic are not data — they must be rebuilt

folk sequences (LinkedIn DM flows, email drip sequences, follow-up triggers) are workflow configurations, not CRM records.

How we handle it

They do not appear in a data export and cannot be extracted as migration payload. HubSpot has its own sequence tooling (Sales Hub Professional+) and Workflows (all tiers) that operate differently — folk's step-based sequences do not map to HubSpot's enrollment-trigger model. We export a structured JSON reference of your folk sequence definitions (step order, delay days, contact filter criteria) so your HubSpot admin has a rebuild blueprint. The automation rebuild effort is not included in FlitStack migration pricing.

medium

folk email and LinkedIn tracking history requires HubSpot tracking code re-installation

folk tracks email opens, clicks, and LinkedIn profile visits by instrumenting the email channel and LinkedIn browser integration within its own platform.

How we handle it

This engagement history migrates as past engagement records in HubSpot, but HubSpot's own email tracking (open/click logging) only resumes after you reinstall the HubSpot tracking code on your email domain and reconnect LinkedIn integrations. Engagement history before migration cutover shows as past data in HubSpot; new engagement tracking starts fresh post-migration.

medium

HubSpot marketing contact billing model means migrated contacts may affect HubSpot pricing

HubSpot bills Marketing Hub at contact tier thresholds (1,000, 2,000, 10,000+ contacts).

How we handle it

Every contact migrated into your HubSpot portal counts toward that total, regardless of whether it has marketing email activity. folk does not have a separate marketing contact billing flag — all contacts are treated equally. After migration, your HubSpot contact count is assessed for Marketing Hub tiering. If you have a large folk database with many cold or inactive contacts, you may trigger a tier upgrade. We include a pre-migration contact count and tier-impact estimate in the scoping phase.

How the migration runs

  1. Extract folk contacts, companies, deals, and groups via API

    FlitStack connects to folk via its export API to extract all contacts (person and company types), deals, notes, email tracking records, and group memberships.

    What this step covers

    We capture every custom field definition per group, including pick-list values and field types. The export runs against a live read-only connection — your team continues working in folk during extraction. The output is a structured JSON dataset organized by object type and group.

  2. Design group-to-lifecycle and property mapping plan

    Before any data is created in HubSpot, we build a mapping plan covering: (a) which folk groups map to HubSpot lifecycle stages vs. custom properties vs. static lists; (b) disambiguation of duplicate custom field names across groups; (c) folk deal stage names mapped to HubSpot pipeline stage values (creating a custom pipeline if needed); (d) owner email-to-HubSpot user resolution.

    What this step covers

    The mapping plan is delivered as a review document — your team approves it before the test migration runs.

  3. Run test migration with field-level diff on 100–500 sample records

    A representative slice of folk records — spanning contacts from multiple groups, companies, deals, notes, and custom field values — migrates to a HubSpot staging portal (or sandbox if available).

    What this step covers

    We generate a field-level diff comparing source folk values against the HubSpot destination fields, showing every mapped value, every custom property created, and every pick-list value translated. You verify the diff and approve the mapping plan or request adjustments before the full migration commits.

  4. Execute full migration and delta-pickup window

    The full folk dataset loads into HubSpot.

    What this step covers

    Contacts and companies migrate first (required for deal associations), then deals with their stage mappings and owner assignments, then notes and email tracking as engagements. A delta-pickup window of 24–48 hours runs after the main load to capture any records modified or created in folk during the cutover period. All operations are logged in the FlitStack audit trail. One-click rollback is available if reconciliation reveals data integrity issues.

  5. Deliver sequence rebuild reference and post-migration handoff

    We deliver a machine-readable JSON export of your folk sequence definitions (step order, delay rules, contact filter criteria) and a written summary of all folk groups mapped to HubSpot static lists or custom properties.

    What this step covers

    HubSpot workflows, sequences, and automation logic must be rebuilt manually — the reference document gives your HubSpot admin a starting blueprint. We offer a separate scope for workflow rebuild if your team prefers guided assistance.

folk HubSpot
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · HubSpotRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

48–72 hours for under 50,000 recordsTypical, smaller accounts
5–8 days for over 500,000 records or complex group-to-lifecycle routingLarge or heavily customised accounts

FlitStack pricing for folk to HubSpot migrations scales with three drivers: total record count across contacts, companies, and deals; number of folk groups that need mapping to HubSpot lifecycle stages or static lists; and custom property count and type complexity (pick-lists need value-by-value mapping in HubSpot). Folk's per-group custom fields inflate the property count since HubSpot portal-wide properties must be created for each unique field name encountered across all groups. Migrations with more than 15 groups, 50+ custom fields, or heavy deal history fall in the upper pricing range. The test migration phase is included in all tiers. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for folk to HubSpot →

Why teams move from folk to HubSpot

  • folk's group-based data model makes cross-team reporting difficult — there is no single view of all contacts regardless of group assignment. HubSpot's lifecycle stage on the contact record enables unified reporting across the entire contact database without switching context between groups.
  • Teams outgrow folk when they need HubSpot's native deal pipeline with stage probability, forecast category, and multi-pipeline support. folk's pipeline views are scoped per group, which limits visibility for managers who need a portfolio view across all groups simultaneously. This creates blind spots in forecasting and pipeline health assessment.
  • folk's enrichment credits and Magic Field AI caps (2,000–5,000/month workspace-wide) throttle active outbound teams. HubSpot's Breeze AI and Sales Hub Professional+ reporting give deeper pipeline intelligence without per-month workspace credit limits. As outreach volume scales, folk's AI credit constraints become a blocking issue for sales development teams running high-volume sequences.
  • folk's LinkedIn-first workflow works for solo and small teams, but HubSpot's 1,600+ integrations and native marketing-sales alignment across Hub, Sales, and Service hubs better supports mid-market companies that need cross-functional CRM coverage. Companies scaling beyond 10 users typically require integration with ERP, billing, and support tools that folk does not natively connect to.

Questions, answered

folk to HubSpot migration questions

How long does a folk to HubSpot migration take?

Most folk to HubSpot migrations complete within 48–72 hours of clock time for databases under 50,000 contacts, companies, and deals combined. Larger datasets with 500,000+ records or migrations with more than 15 folk groups requiring custom pipeline creation extend to 5–8 days. The longest planning step is designing the group-to-lifecycle mapping strategy — the data load itself runs on a compressed timeline using HubSpot's bulk API ingestion.

Will my folk sequences and automation logic migrate to HubSpot?

No. FlitStack migrates data and schema only — folk sequences, LinkedIn automation flows, and follow-up triggers are workflow configurations, not data records. They do not appear in a folk data export. We provide a structured JSON summary of your sequence step order, delay rules, and contact filter logic as a rebuild reference for your HubSpot admin. Rebuilding sequences in HubSpot's Workflows and Sequences tools requires manual setup and is not included in migration pricing.

What happens to my folk group memberships in HubSpot?

HubSpot has no native group equivalent — groups are a folk-specific organizational construct. We migrate each folk group as a custom contact property (Group_Membership__c) and create HubSpot static lists named after each group. Your team decides whether group names map to HubSpot lifecycle stages or remain as static lists. Folk group names used as deal categories are preserved in a custom deal property (Source_Group__c) for audit continuity.

Can I migrate folk custom fields to HubSpot custom properties?

Yes. folk custom fields per group become HubSpot custom contact or deal properties portal-wide. If the same field name exists in multiple folk groups with different pick-list values (e.g., 'Status' with different values in Leads vs. Clients), we disambiguate by creating separate HubSpot properties with a group-name prefix. Pick-list values map value-by-value. Number, date, and text field types translate directly to their HubSpot equivalents.

What happens to folk deal stages in HubSpot?

folk deal stage names map to HubSpot dealstage values. If your folk stages do not match HubSpot's default pipeline stage names, we create a custom HubSpot pipeline with stages matching your folk stage names before data loads. Stage probabilities and forecast categories are preserved as deal properties in HubSpot. The folk group the deal originated from is saved in a custom property for audit traceability.

Does the migration affect my folk account during cutover?

No. FlitStack uses scoped read-only API access on folk — your team keeps full read/write access to folk during the migration. A delta-pickup window of 24–48 hours captures any contacts, companies, or deals created or modified in folk after the main data export. Your team should freeze new folk automation sequences during the cutover window since those cannot be migrated — new manual follow-ups entered in folk during cutover are picked up in the delta run.

Will my folk email and LinkedIn tracking history show up in HubSpot?

Past email open/click and LinkedIn interaction logs from folk migrate as historical engagement records in HubSpot. However, HubSpot's own live email tracking (opens, clicks, reply detection) only resumes after you reinstall the HubSpot tracking code on your email domain and reconnect LinkedIn integrations post-migration. The engagement history before cutover shows as past data in HubSpot reports; new tracking starts fresh from the go-live date.

Get a quote

Moving from folk to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

Get a quote