Migrate from Checkbox to Freshsales

Checkbox contact records and intake submissions map directly to Freshsales Leads. Email address is the unique identifier for deduplication. First name, last name, phone, and custom field values transfer as-is. Submissions with no company association land as standalone Lead records.

Checkbox contacts flagged as converted or associated with a company map to Freshsales Contacts. Contact requires an AccountId — if no company exists in Freshsales, a placeholder Account is created first, or the contact is held pending account resolution during the migration run.

Checkbox records containing company information map to Freshsales Accounts. Account.Name, website, industry, employee count, and annual revenue transfer directly. If Checkbox stores hierarchical company data, the parent relationship maps to Freshsales Parent Account via the ParentId field. During the import, FlitStack validates each Account against duplicate rules to prevent accidental duplication of existing records.

Checkbox submissions tagged with a deal flag or containing deal-amount fields map to Freshsales Opportunities. The submission title becomes Opportunity.Name, deal amount maps to Amount, expected close date maps to CloseDate, and deal stage maps to StageName via value mapping per pipeline.

If Checkbox stores multiple deal pipelines or stage values, each pipeline maps to a Freshsales Deal Pipeline with stage values mapped value-by-value. Stage probability and forecast category re-applied from Freshsales pipeline defaults. Multiple Checkbox pipelines require multiple Freshsales pipeline configuration.

Checkbox custom fields (text, number, checkbox/boolean, date, dropdown, multi-select, formula) require Freshsales custom fields to be created before migration. Field type is preserved: Checkbox boolean becomes Freshsales checkbox, Checkbox dropdown becomes Freshsales picklist, and so on. Enterprise plan required for advanced custom field types and field-level permissions.

Checkbox file attachments (documents, images, PDFs uploaded with submissions) are downloaded and re-uploaded to Freshsales as file attachments on the corresponding Lead, Contact, or Account record. File size limits per Freshsales plan apply — files exceeding 25MB require chunking or alternative storage linking.

Checkbox assignee and team-member fields resolve by email match against Freshsales users. Unmatched owners are flagged before migration — teams either create Freshsales users first or assign records to a fallback owner. OwnerId on Opportunities and Contacts is set during the migration run.

Checkbox workflow states and submission statuses represent process logic with no direct Freshsales equivalent. These values migrate as custom field data for reference, but the underlying workflow automation must be rebuilt in Freshsales Workflows post-migration. FlitStack exports the workflow definition as a rebuild reference.

Checkbox conditional survey logic, branching rules, and conditional field display rules are platform-native and cannot transfer to Freshsales. The survey structure exports as a reference document, but Freshsales forms do not support equivalent branching logic natively — this requires custom form-building or a third-party form tool.

Checkbox AI-powered legal workflow configurations (clauses, obligation tracking, contract-review automation) have no Freshsales equivalent. These automations must be rebuilt using Freshsales Workflows and, for legal-specific use cases, a dedicated legal-automation tool. FlitStack provides a workflow audit export as a rebuild specification.