Migrate from folk to Zoho CRM

folk Contacts of person subtype map directly to Zoho CRM Contacts. Standard fields (First Name, Last Name, Email, Phone, LinkedIn URL) map to Zoho's First_Name, Last_Name, Email, Phone, and LinkedIn fields. Custom fields present in the source Group's schema migrate to corresponding Zoho custom fields on the Contact module, which must be pre-created during schema design. Address data maps to Zoho's Mailing Street, Mailing City, Mailing State, and Mailing Country fields. Tags migrate as Zoho Tags on the Contact record.

folk Contacts of company subtype map to Zoho CRM Accounts rather than Contacts. The company name maps to Account_Name. Any custom fields specific to company-type contacts (industry, employee count, revenue) migrate to corresponding Zoho Account custom fields. Person-type contacts at the same company link via the Account Name lookup on the Contact record. We cannot infer folk relationships that were not manually established; only explicit relationship links present in the export migrate.

folk Groups are container entities with no direct Zoho equivalent. We map each Group using one of two strategies chosen during scoping: either as a Zoho Tag applied to all records originally in that Group (preserving group membership as a label without creating a separate module), or as a custom Zoho picklist field (e.g., Segment) whose values match Group names. The chosen strategy depends on whether the customer relies on Groups for workflow routing or purely for contact organization.

folk Pipeline views with custom stages map to Zoho CRM Potentials. Each pipeline in folk becomes a separate Zoho Sales Pipeline within the Potential module. Stage names from folk transfer to Zoho Stage picklist values, which we configure in the Potential module before migration. Stage probability percentages map to Zoho's probability field per stage. Potential records inherit the Account lookup from the company-type contact mapping.

folk Notes attached to contacts migrate to Zoho CRM Notes. The note body, creation timestamp, and author attribution map to Zoho Note content, Created_Time, and Owner fields. Notes attach to the parent record (Contact or Account) via Zoho's Related_To lookup. Plain text content migrates directly; rich formatting is preserved where the CSV export supports it.

folk Reminders map to Zoho CRM Tasks. The reminder text becomes the Task Subject, the due date maps to Due_Date, and the assignee (owner) maps by email resolution to a Zoho User. We resolve the owner by matching the folk owner email against Zoho User email addresses; unresolved owners go to a reconciliation queue for admin provisioning before the migration phase.

folk contact tags migrate as Zoho CRM Tags. Tags are stored as a multi-value string array per contact and map directly to Zoho's tag model. The full tag set per contact transfers as tag strings, which Zoho renders as clickable tag pills on the contact or account record. Tag-based segmentation used for group membership may be superseded by the Group mapping strategy selected in scoping.

folk's activity timeline records (calls, logged emails, meetings) partially appear in the CSV export. We map these to Zoho CRM Tasks (for calls and generic activities) and Events (for meetings with start and end time). Activity timestamps preserve the original folk timestamp to maintain timeline ordering. Activity attribution (who performed the activity) resolves by owner email to Zoho User. Activity history coverage is partial because folk's CSV export does not include the full engagement log; we flag any timeline gaps in the reconciliation report.

Contact attachments exported from folk as file references or URLs migrate as Zoho CRM attachments on the corresponding Contact or Account record. We download source files and re-upload to Zoho. File size limits apply per Zoho's attachment constraints (typically 10 MB per file). Attachments that reference external URLs in folk without a downloadable file are logged as attachment references for manual follow-up post-migration.

Folk custom fields are defined per-group, creating a fragmented schema. During discovery we enumerate every Group's field definitions and consolidate them into a unified per-module custom field map in Zoho CRM. Fields that exist in one Group but not others become optional custom fields in Zoho (no value for contacts that originated in Groups where the field was not defined). This consolidation step is required before any record import because Zoho enforces field consistency per module. Conflict-resolution logic applies when a contact spans multiple Groups with conflicting field values for the same field name.