Migrate from Checkbox to Microsoft Dynamics 365 Sales

Each Checkbox survey maps to a dedicated custom table in Dataverse. The table name derives from the survey title (sanitized). We create the table schema first, then map response rows as table records. Response GUID becomes the primary key; source survey ID is stored as a text reference field.

When a Checkbox survey captures contact fields (name, email, phone), those values extract into separate Contact records in Dynamics 365 Sales. The custom response table stores a Contact lookup (fullname) rather than duplicating contact fields. Email match against Dynamics users resolves owner assignment.

Checkbox forms that ask for company information map to Account records in Dynamics. If the same company appears across multiple Checkbox survey submissions, deduplication by name and domain creates a single Account with multiple response linkages. Unmatched companies create Account records with the name provided in the form.

The Checkbox user who created a survey is resolved by email match to a Dynamics 365 Sales SystemUser record. This owner becomes the OwnerId on the custom response table record. Unmatched owners are assigned to a designated fallback Dynamics user flagged before migration.

Every Checkbox custom property on a survey becomes a column in the corresponding Dataverse custom table. Field type mapping: text to Single-Line Text, number to Whole Number or Decimal, date to Date and Time, multi-select to Choice or Multi-Select Option Set. Boolean checkboxes in Checkbox map to Two Options in Dataverse.

Checkbox preserves the original submission timestamp on each response record. In Dynamics 365 Sales, the CreatedOn field reflects the Dataverse record creation date rather than the original submission time. We capture the original Checkbox submission date as a custom datetime column so that all reporting displays the actual submission timeline accurately, independent of when the migration run occurred.

Checkbox integrations are connection-level configurations that point to external systems. They do not migrate. If Checkbox pushes completed intake to Salesforce via an integration, we can configure a Dynamics 365 Sales post-migration workflow in Power Automate to replicate that routing behavior.

Files attached to Checkbox survey responses are downloaded from Checkbox storage and re-uploaded to the associated Dynamics custom table record's designated SharePoint document location or as Dataverse Note attachments, depending on your Dynamics configuration. File size limits follow Dataverse constraints with a maximum of 32MB per file for notes.

Checkbox user roles and team assignments do not map directly to Dynamics 365 Sales security roles and team structures. After migration, the Dynamics administrator must assign appropriate Security Roles and Team memberships based on each user's job function. The exported Checkbox user list serves as a useful reference guide for making these role assignment decisions.

Checkbox maintains complete form version history as a standard feature. Dynamics custom tables lack native schema version tracking capabilities. Only the current field definitions from the final survey version migrate across; historical version data is not replicated. We recommend documenting the final Checkbox survey state prior to cutover as the authoritative reference record.