Migrate from folk to HubSpot

folk person contacts map 1:1 to HubSpot contacts. 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.

folk company-type contacts map to HubSpot companies via the Companies API. 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.

HubSpot has no native group equivalent. 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.

folk deals inside groups map to HubSpot deals using the Deals API. 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.

folk pipeline stage names map to HubSpot dealstage values via value_mapping. 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.

folk notes and reminders attached to contacts or deals migrate as HubSpot engagements with type 'note' via the Engagements API. 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.

folk email tracking logs (sent emails, opens, clicks) migrate as HubSpot engagements with type 'email' using the Engagements API. Original send timestamp and recipient contact preserved. HubSpot requires the tracking code installed on your email domain to resume new tracking post-migration. Historical email tracking data from folk appears as past engagement records in HubSpot.

folk relationship records (e.g., 'reports to', 'colleague') have no direct HubSpot equivalent object. We migrate these as a custom multi-select text property (Related_Contacts__c) listing the related contact email addresses. The HubSpot Associations API is used when relationships are explicitly defined between contact records to maintain the relationship graph.

folk owner assignment (user email) resolves against HubSpot users by email match using the Owners API. If a folk owner has no matching HubSpot user, the record lands unassigned — we flag these before migration so your team can invite the user or reassign before go-live. Owner resolution runs as a pre-flight check before the main migration load.

folk custom fields scoped to a group create HubSpot custom contact or deal properties portal-wide via the Properties API. Duplicate field names across groups (e.g., 'Status' in both Leads and Clients) are disambiguated with a group prefix in the HubSpot property name (Leads.Status__c, Clients.Status__c). Pick-list values are mapped value-by-value during property creation.

folk files attached to contacts or deals are downloaded and re-uploaded to HubSpot Files using the Files API. File names, sizes, and attached-to-record associations are preserved. Files are re-associated to the migrated HubSpot contact or deal record after upload. HubSpot file size limit is 250MB per file — any folk attachments exceeding this threshold are flagged for manual handling.

folk sequences and automation logic do not transfer — they are operational constructs, not data. We export a machine-readable JSON summary of your folk sequence definitions (step order, delay rules, contact filtering logic) as a rebuild reference for your HubSpot admin. The JSON export includes enrollment triggers, step sequencing, and delay configurations needed to rebuild in HubSpot Workflows.