Migrate from Checkbox to Pipedrive

Checkbox form submissions that capture contact information (name, email, phone) map directly to Pipedrive People records. The submission ID from Checkbox is stored as a custom field for traceability. If a submission captures multiple contacts, each becomes a separate Person record.

Checkbox form fields for first name, last name, and email map directly to Pipedrive's name and email fields on the Person object. Phone and mobile fields map to the corresponding phone fields on Person. These are direct field-to-field assignments with no transformation required, preserving the original contact data exactly as entered in Checkbox.

Checkbox submissions that include company or organization name map to Pipedrive Organization records. If the same company appears across multiple submissions, FlitStack deduplicates to a single Organization and links all associated Person records. This deduplication prevents duplicate company records from cluttering Pipedrive and maintains referential integrity across the CRM.

Each distinct Checkbox custom field defined on a form becomes a Pipedrive Custom Field on the matching entity (Person, Organization, or Deal). Pipedrive generates a 40-character hash key for each custom field — FlitStack records the mapping between Checkbox field label and Pipedrive field key for downstream reference.

Checkbox's boolean checkbox field type has no native Pipedrive equivalent. We map to a Pipedrive custom field — either a text field storing 'Yes'/'No' or a pick-list with Yes/No options depending on downstream reporting needs. Value mapping is documented in the migration plan before the run.

Checkbox date and datetime custom fields map to Pipedrive date or datetime custom fields of the same type. Original timestamps from submission records are preserved. Timezone handling is documented — FlitStack converts to UTC and notes the source timezone for Pipedrive admin review.

Checkbox multi-select fields (where a respondent can select multiple options) require value-by-value mapping to Pipedrive pick-list options. If Pipedrive pick-lists are not feasible, FlitStack collapses multi-select values into a semicolon-delimited text field and documents the original options for manual cleanup.

Checkbox stores file attachment URLs or binary blobs linked to form submissions. FlitStack re-uploads attachments to Pipedrive's Files feature, attaching each file to the corresponding Person or Organization record. Pipedrive's storage limits apply per plan tier — Essential includes 5GB/user; larger imports may require plan upgrade.

Checkbox records a submission timestamp per response. Pipedrive's CreatedDate reflects the migration run date, not the original submission date. FlitStack preserves the original Checkbox submission date as a custom datetime field (e.g., Original_Submission_Date__c) so historical reporting continuity is maintained and teams can sort or filter by the original submission timestamp in Pipedrive.

If Checkbox stores an owner or assignee per submission, FlitStack resolves by email match against Pipedrive Users. Unmatched owners are flagged as custom field values on the record — Pipedrive requires a valid UserId for owner assignment, so unresolved assignments are logged for admin review before final migration.

Checkbox workflows and automation rules — conditional routing, SLA timers, approval chains, escalation logic — have no equivalent construct in Pipedrive's object model. FlitStack exports a JSON representation of each workflow definition as a reference document. Pipedrive's Automation builder can recreate trigger-based rules, but complex branching logic requires manual design.

The form structure itself — field order, conditional visibility, validation rules, branching logic — is a Checkbox-specific artifact. Pipedrive has no form builder at the CRM level. If Pipedrive's Advanced plan or a marketplace form tool is in scope, those integrations can recreate form-based intake, but the original form schema does not migrate.