Migrate from folk to Freshsales

Folk person-type Contacts migrate directly to Freshsales Contact. The folk subtype field is preserved in a custom field folk_subtype__c. All standard properties (name, email, phone, social handles) map to Freshsales standard fields. Custom fields per contact migrate via the per-Group field map. Each contact receives an AccountId lookup once the parent Account (from folk company-type contacts) is created.

Folk company-type Contacts map to Freshsales Account. The folk subtype field is preserved in folk_subtype__c on the Account. All company properties and custom fields migrate per the applicable Group field map. Person-type contacts that have a manual relationship link to this company-type contact receive an AccountId pointing to the newly created Account.

Folk Groups are migration targets as both Contact records (the group membership data) and Freshsales native Tags applied to those contacts. We extract every Group name, enumerate all Contacts in each Group during discovery, and apply the Group name as a Freshsales Tag on each Contact record during import. Contacts that appear in multiple Groups receive multiple Tags.

Folk custom fields are defined per-Group, not globally. We enumerate every Group's field schema during discovery, build a distinct field map per Group, then pre-create Freshsales custom fields before any record import. Fields with conflicting names or types across Groups require conflict-resolution logic and customer sign-off before migration begins.

Folk pipeline views per Group map to Freshsales Pipeline stages. Each pipeline stage from folk becomes a Freshsales Deal Stage value within the configured Pipeline. We preserve stage order and any custom stage labels. Closed-won and closed-lost reasons from folk become Freshsales custom deal fields.

Folk Notes attached to contacts migrate as Freshsales Notes linked to the corresponding Contact. Note body, author attribution, and timestamp migrate directly. Notes are imported after the parent Contact exists to satisfy the relationship reference.

Folk Reminders migrate to Freshsales Task with the reminder text as Task Subject and the due date as ActivityDate. Assignee mapping requires resolving the folk user identity to a Freshsales User by email. We flag any Reminders assigned to users without a matching Freshsales User for the customer's admin to resolve.

Folk Tags migrate as Freshsales native Tags applied to Contact records. Tags stored as multi-value fields on folk contacts migrate as individual Tag records linked to the Contact. Group names also become Tags as described in the Group mapping entry.

Activity data present in folk's CSV export (sent emails, logged meetings, call records) migrates to Freshsales Task records for calls and emails, and Event records for meetings. We map what is available in the CSV; activity timeline gaps are expected due to folk's limited activity export scope. Freshsales built-in phone call logs are not applicable to migration scope since they represent future Freshsales activity, not historical folk data.