Migrate from GoCanvas to Twenty CRM

Each GoCanvas submission maps to a Twenty Task record. The Task's subject becomes the form name, and the Task body stores a structured key-value dump of all submission field values. The submission date becomes Task dueDate or a custom datetime field for reporting continuity.

Each distinct GoCanvas form type becomes a named custom object in Twenty (e.g., Inspection, Work Order, Safety Check). The custom object fields replicate the form's field structure — text fields, number fields, and select fields map to their Twenty type equivalents. Forms with shared field schemas can be consolidated into a single custom object with a form-type discriminator field.

GoCanvas user accounts map to Twenty workspace members. Matching happens by email address. Unmatched GoCanvas users are flagged before migration — your team either invites them to Twenty or assigns their submission records to a fallback member. The GoCanvas device-license distinction does not translate to Twenty and is not preserved.

GoCanvas groups (used to publish forms to specific teams) translate to a custom select field on the target Twenty object — either a form-type custom object or a Task type field. Teams that used groups for access control should plan Twenty permission sets separately during workspace setup.

GoCanvas Reference Data spreadsheets map to Twenty select fields if the list is flat, or to a relation object (a small custom object acting as a lookup table) if the list has dependent columns. The Reference Data must be pre-loaded into Twenty before submission imports run because Twenty CSV import requires target fields to exist first.

The GoCanvas user who submitted a record maps to the Task assignee field in Twenty via email resolution. This preserves the chain of accountability for each field submission and allows Twenty's activity tracking to attribute work to the correct member.

GoCanvas submissions containing address fields (Address Line 1/2, City, State, Zip) map to Twenty address fields on the associated Company or a custom address block on the Task. GoCanvas auto-generates navigation buttons for address fields — this behavior does not replicate in Twenty and must be rebuilt as a custom workflow or integration if required.

GoCanvas photo and signature attachments on submissions migrate as file attachments on the corresponding Twenty Task or custom object record. Twenty's file storage handles the re-upload; inline images embedded in submission PDFs are downloaded and attached individually. File size limits on the target Twenty deployment apply.

GoCanvas's internal submission ID is stored as a custom text field (Source_Submission_ID__c) on each Twenty record for traceability, delta-run deduplication, and audit purposes. This field enables FlitStack AI to identify already-migrated records on subsequent runs, maintain a permanent link back to the source GoCanvas submission, and support rollback procedures if post-migration reconciliation reveals mapping errors. The field is marked as unique where the Twenty deployment supports unique constraints on custom fields.

GoCanvas Workflows, dispatch rules, and handoff chains have no direct equivalent in Twenty CRM. Twenty's workflow builder handles internal automations but lacks GoCanvas's multi-step field-team dispatch model. We export your GoCanvas workflow definitions as a structured JSON + markdown reference document your admin can use to rebuild the logic in Twenty or a separate automation tool.

GoCanvas automations (email notifications, conditional routing, escalation triggers) cannot migrate to Twenty. These must be rebuilt as Twenty Workflows or handled by an external automation layer (n8n, Make, or similar). Our export package includes each automation's trigger condition, action, and target so the rebuild is traceable.

GoCanvas tracks form version history for each submission. Twenty has no native form-version audit. We preserve the source form version ID as a custom field on each migrated record so historical context is not lost, but version-state progression is not modeled in Twenty.