Migrate from Checkbox to Zoho CRM

Each Checkbox submission record maps as a Zoho Lead. Submission metadata (respondent name, email, phone, job title, company) maps to the corresponding Zoho Lead standard fields. Status and source information from the Checkbox form becomes a custom picklist field on the Lead.

Checkbox intake request records map to Zoho Deals. The form's request name, category, priority, and deadline fields translate to Deal fields or custom fields. The request owner (assigned user in Checkbox) resolves by email to a Zoho CRM user and populates Deal Owner.

Checkbox multi-select fields store values as comma-separated text. FlitStack decodes the values and populates a Zoho multi-select picklist field. The picklist value list is built from the unique values found in the Checkbox export — if a value does not yet exist in Zoho, it is created during migration setup.

Checkbox single-choice fields map to Zoho picklists with a value-by-value translation. Each distinct choice option in the Checkbox form definition creates a corresponding picklist value in Zoho. If the source form changes after the export, new values are flagged as unmapped and require manual review before import.

Numeric choice fields in Checkbox such as rating scales and budget ranges transfer directly to Zoho Number fields. Numeric validation rules from Checkbox are not automatically enforced in Zoho — post-migration validation is recommended to catch any out-of-range values that may have been entered in Checkbox.

Checkbox calculated fields using arithmetic or date expressions are translated to Zoho Formula fields where the syntax is compatible. Complex Checkbox expressions using custom functions may fall back to a Number or Currency field with the calculated value pre-populated as a static field — your Zoho admin can convert to a live formula after migration.

Checkbox date and datetime fields map to Zoho Date or DateTime fields, preserving the original date value. Because Zoho's native Created Date reflects migration time rather than the original submission, FlitStack stores the original submission date in a custom field such as Original_Submission_Date__c to maintain reporting continuity.

Checkbox text and textarea fields map to Zoho's multi-line text field type, which supports up to 32 KB per record. Long text fields from Checkbox are preserved in full. Special characters (pipe |, angle brackets) that Zoho's import rejects are stripped or escaped during the transformation step.

Files attached to Checkbox submissions are downloaded, then re-uploaded to Zoho Files and linked to the parent record (Lead or Deal). Zoho's 25 MB per-file limit applies — files exceeding this are flagged and skipped with a manifest so they can be uploaded manually or stored in Zoho Docs.

Checkbox does not have a native user directory equivalent to Zoho's Users module. Owner assignment in Checkbox submissions is resolved by email match against Zoho users. Unmatched owners are assigned to a fallback Zoho user and flagged in the migration report for manual re-assignment.

The originating Checkbox form or survey name is preserved as a custom text field on every migrated record, enabling segmentation by intake source in Zoho reports. This field is also used to map multiple Checkbox forms to multiple Zoho layouts or tags.

Checkbox workflow definitions (conditional routing, approval steps, Slack notifications, Ironclad integrations) do not transfer to Zoho. FlitStack exports the workflow definition as a documented reference document with step-by-step logic, which your Zoho admin uses to rebuild equivalent Zoho Blueprint sequences. This is a manual rebuild step included in the migration engagement scope.

Checkbox custom forms with fields not matching standard CRM objects migrate as Zoho CRM Custom Modules. The import file naming convention (form name + _C.csv) triggers Zoho's auto-module-creation during migration. Related lists link custom modules to Leads or Deals via lookup fields created during schema setup.

The original Checkbox submission GUID is stored as a text field in Zoho for traceability, delta-run de-duplication, and cross-referencing back to the Checkbox system during the cutover window. This field is indexed and used as the unique identifier for incremental record matching.