Migrate from Checkbox to Twenty CRM

Each Checkbox form submission from a named respondent maps to a Twenty People record. The respondent's first name, last name, and email from the form response become the corresponding Twenty fields. If Checkbox captures company information in the form, it maps to the People.companyId relation requiring a Company record to exist first.

When a Checkbox form collects only an email address without full name, FlitStack creates a minimal People record with the email field populated and firstName/lastName left blank for manual completion. The original submission timestamp is preserved in a custom datetime field.

Any company name or organization field captured in a Checkbox form submission maps to a Twenty Companies record. The company domain is parsed from the respondent email address and populated in Companies.domain for automatic linking. Duplicate company names are deduplicated during migration.

Checkbox custom fields on forms — text, number, date, or select types — require pre-creation as custom fields in Twenty Settings → Data Model before import. FlitStack delivers a field-creation guide specifying the field name, type, and pick-list values from the Checkbox form definition.

Each Checkbox workflow run generates a log entry with timestamps, triggered steps, and outcomes. FlitStack maps these as Notes attached to the relevant People or Company record, with the workflow name as the Note title and the run outcome as the body text. Original run timestamps are preserved in the Note body.

Files uploaded via Checkbox form responses are downloaded by FlitStack and re-uploaded to Twenty as Notes with file attachments. The Note body captures the original file name and upload timestamp from Checkbox. Files exceeding Twenty's attachment size limits are flagged for manual handling.

If Checkbox forms capture deal value, deal stage, or expected close dates in custom fields, FlitStack maps these to a Twenty Opportunities record linked to the People or Company from the same submission. The Opportunity name defaults to the form name + respondent email. Pipeline stages require post-migration configuration in Twenty.

Checkbox workspace users (admins, form editors) are matched to Twenty Workspace Members by email address. FlitStack flags any Checkbox user without a matching Twenty Workspace Member before migration — these records either get assigned to a fallback owner or require a Twenty user invite before migration runs.

If Checkbox forms represent a distinct entity type in your process (e.g., Intake Requests, Support Tickets), FlitStack can map these to a Twenty Custom Object rather than People. The custom object definition (name, plural label, fields) is delivered as a schema plan for pre-creation in Twenty Settings → Data Model.

Checkbox captures submission metadata: response ID, submission timestamp, last-edit timestamp, IP address, language. The response ID maps to a Source_Response_ID__c custom field on People for traceability. Original timestamps map to Original_Submission_Date__c. IP and language map to custom text fields if retention is required.