Migrate from GoCanvas to Zoho CRM

Each GoCanvas form becomes a Zoho CRM custom module. Form fields map to custom fields in that module. The module API name follows Zoho convention (uppercase, underscores). We create the module before migration so field mapping can reference the target field IDs. Custom fields are created with matching data types — text, number, date, pick-list, lookup — based on the source field definition in GoCanvas.

Individual submissions import as individual records in the corresponding Zoho CRM custom module. Each submission row becomes one record with fields populated from the form field values captured at submission time. The submission timestamp maps to a custom datetime field in Zoho CRM. Submitter information maps to the Zoho CRM user lookup by email match.

GoCanvas users map to Zoho CRM users via email address matching. Users who do not have a matching Zoho CRM account are flagged before migration — your team either creates the Zoho user first or assigns those submissions to a default owner. Group memberships in GoCanvas have no direct Zoho equivalent; they are preserved as a custom multi-select pick-list field on the user record.

GoCanvas Reference Data is a CSV or Google Sheet used as a lookup table within a form. Small Reference Data tables (under 100 rows) are converted to Zoho CRM pick-list fields on the target module, preserving the exact allowed values. Large Reference Data tables are migrated as separate Zoho CRM custom modules with a lookup relationship from the submission module.

GoCanvas Workflow chains submissions through a multi-step handoff sequence with approval gates before final submission. This has no native Zoho CRM equivalent. Zoho Blueprint provides stage-based process automation but does not replicate GoCanvas's handoff queue model. FlitStack exports the GoCanvas Workflow definition as a written process document so your Zoho admin can rebuild it in Blueprint or Deluge script.

Files and photos attached to GoCanvas submissions are downloaded and re-uploaded to the corresponding Zoho CRM record. Zoho CRM stores attachments on the record's Attachments related list or in Zoho Docs linked via custom URL fields. Inline images in notes are extracted, saved as image files, and reattached.

GoCanvas captures metadata on every submission: submission ID, device type, GPS coordinates, and form version. None of these have Zoho CRM standard field equivalents. We create custom fields — Submission_ID__c, Device_Type__c, GPS_Latitude__c, GPS_Longitude__c, Form_Version__c — to preserve this metadata for audit and analytics purposes.

GoCanvas Groups control form access and submission routing. Zoho CRM uses a Team model for data sharing and record assignment. Group memberships are mapped to Zoho Teams by name where a 1:1 mapping exists, or consolidated into a custom multi-select field if the group structure does not map cleanly to Zoho's team sharing model.

GoCanvas supports calculated fields that compute values (sums, averages, conditional logic) within a form. Zoho CRM formula fields support a subset of these calculations. Complex GoCanvas calculations that Zoho formula fields cannot replicate are migrated as read-only custom number or currency fields populated at migration time — we preserve the computed value from GoCanvas, and your admin decides whether to convert to a live formula.

Free-text notes added to a submission in GoCanvas migrate to Zoho CRM Notes on the corresponding record. If the note was added during a Workflow handoff (indicating a specific activity), we migrate it as a Zoho CRM Task with the handoff timestamp and the handoff user's name as the task owner.

GoCanvas Dispatch sends a form to a field worker for completion at a scheduled time. Zoho CRM Tasks and Events serve a similar scheduling function. Dispatch records migrate as Zoho Tasks with custom fields for dispatch destination, scheduled date, and dispatch status. Completed Dispatch records link to the resulting Submission record.

GoCanvas Subforms allow a repeating set of fields within a single submission (e.g., a checklist of items). Zoho CRM supports Subform fields on standard modules, or you can create a related custom module with a one-to-many relationship from the parent submission module. We recommend the related module approach for more than 10 subform fields or when the subform data needs independent reporting.