Migrate from Checkbox to Nutshell

Checkbox survey responses containing name, email, phone, and job title extract as contact fields and map to Nutshell Person records. Each unique respondent email creates one Person — duplicate submissions by the same email update the existing Person record rather than creating a new one.

When Checkbox forms include a company name field, that value maps to a Nutshell Company record. The Person record links to the Company via Nutshell's party-company association. If the Company doesn't exist in Nutshell, it is created during the migration run.

Each Checkbox survey field that has no direct Nutshell equivalent becomes a custom field on the Person object. Text fields, number fields, date fields, and multiple-choice fields all map to corresponding Nutshell custom field types. Multi-select Checkbox fields with comma-separated values store as text fields in Nutshell.

Checkbox records the submission datetime for each response. This timestamp migrates as a read-only custom datetime field (Checkbox_Submitted_At__c) on the Nutshell Person record for historical reference. The Person CreatedDate in Nutshell reflects the migration date. The datetime is stored in UTC to maintain consistency across time zones. Teams can use this field to sort responses chronologically or to calculate response latency relative to other events in Nutshell.

The name of the Checkbox form associated with each response migrates as a text field (Checkbox_Form_Name__c) on the Person record. This lets Nutshell users filter and report by original intake source without accessing Checkbox. If a respondent submitted multiple forms, each form name appears as a comma-separated list in the field, giving a complete view of their engagement history. This segmentation aids in lead scoring and targeted follow-up.

Each Checkbox response has a unique internal ID. We store this as Source_Checkbox_ID__c on the Person record for traceability and delta-run de-duplication — any updated Checkbox response with the same ID updates the existing Nutshell Person. During the delta window, new submissions bearing an existing ID trigger an update rather than a duplicate creation, keeping the dataset current. The ID also appears in migration logs, enabling lookup if issues arise.

File attachments submitted with Checkbox responses (documents, signed forms, images) are downloaded and attached to the corresponding Nutshell Person record as Notes. The original filename is preserved so teams can identify what was submitted. If a file exceeds Nutshell's 25MB limit, we store it externally and add a custom URL field pointing to the file location. This preserves the attachment context while respecting Nutshell's storage constraints.

Checkbox workflow definitions, intake routing rules, and automation logic are platform-native constructs with no Nutshell equivalent. These must be rebuilt using Nutshell's sales automation features or an external workflow tool. We export the workflow configuration as a JSON reference document for your admin.

If Checkbox intake requests track a deal or project alongside contact data, those request records can merge into Nutshell Deals. The Deal name maps from the intake request title, the amount maps from a numeric field if present, and custom fields capture intake-specific status data not available in standard Nutshell Deal fields.

Checkbox assigns responses to internal users. We resolve Checkbox user emails against Nutshell users and assign the Person record to the matched owner. Unmatched Checkbox users are flagged before migration — your team decides whether to create Nutshell users for them or reassign their records.