Migrate from GoCanvas to Freshsales

Each GoCanvas submission becomes one Freshsales Deal. The form type and submission date populate the Deal name and Close Date. The JSON field-value pairs from the submission are preserved as custom field values on the Deal or as a rich-text note. Owner resolves from the GoCanvas submitter's email to a Freshsales user.

GoCanvas user accounts (name, email, phone) migrate as Freshsales Contacts. The submitter's email becomes the Contact Email field. If the GoCanvas submitter's email matches an existing Freshsales Contact, records are linked. If the submitter has no email, a placeholder Contact is created with the device identifier in the Last Name field.

Many GoCanvas forms include a company or client name field. When present, FlitStack AI looks up or creates a matching Freshsales Account and links the Deal to it. Accounts without a domain match are flagged for review — your team decides whether to merge or keep separate Account records.

GoCanvas form schemas define the fields in each submission. FlitStack AI creates matching Freshsales custom fields for each form field that has no standard CRM equivalent. Text fields become text custom fields, numeric fields become number custom fields, pick-list-style fields become Freshsales pick-list custom fields with value-by-value mapping.

Each field-value pair from the GoCanvas submission JSON is mapped to the corresponding Freshsales custom field by label match. Fields that appear in only one form and have no other home become Deal-level custom fields. Fields that recur across multiple forms (e.g., Site Address) are surfaced as Contact or Account custom fields for cross-submission reporting.

Photos, signatures, and documents attached to a GoCanvas submission are downloaded and re-uploaded as Freshsales Files linked to the corresponding Deal record. File size limits of Freshsales apply (25MB per file). Inline images in GoCanvas notes are extracted and stored as separate file attachments. URLs to the original GoCanvas-hosted files are preserved in a custom field for audit purposes.

The GoCanvas submission timestamp becomes the Freshsales Deal Created Date. When the original submission date is required for reporting continuity — particularly for compliance-heavy industries — it is also preserved as a custom datetime field (Original_Submission_Date__c) on the Deal record.

GoCanvas user groups (used for form access control and submission routing) map to Freshsales Teams. Members are matched by email to Freshsales user accounts. Groups with no matching Freshsales users are flagged — your admin can invite the user to Freshsales before the migration or reassign records to a fallback owner.

GoCanvas Dispatch records — which assign a form to a specific worker for completion at a specific time — migrate as Freshsales Tasks linked to the corresponding Deal. Dispatch status (pending, in-progress, completed) maps to the Task status field. Uncompleted Dispatches at migration time are flagged for your team to handle post-migration.

GoCanvas Reference Data (CSV or Google Sheets powering form field autofill) maps to Freshsales pick-list custom fields. Each unique value in the Reference Data column becomes a pick-list option. When Reference Data changes frequently, FlitStack documents the current state as a pick-list setup plan so your admin can update it post-migration.

GoCanvas Workflows route submissions between field workers for approval or additional input before final submission. Freshsales has no equivalent workflow-routing construct at the Deal level — automations in Freshsales are trigger-action rules that run on record events, not multi-step human handoffs. FlitStack exports the full GoCanvas workflow definitions (step sequence, responsible user, handoff conditions) as a structured reference document your Freshsales admin uses to rebuild equivalent automation logic in Freshsales.