Migrate from GoCanvas to Salesforce Sales Cloud

Each GoCanvas form becomes a Salesforce Custom Object with the API name Form_API_Name__c. The object label matches the form name in GoCanvas. Custom object plural label is auto-generated from the form name. Deployment via Salesforce Metadata API requires a package.xml entry per object.

Individual submissions map one-to-one to records in the corresponding Salesforce Custom Object, preserving the full field data payload from GoCanvas. Each submission's unique GoCanvas ID is stored in a Source_System_ID__c custom field to enable delta-run de-duplication and traceability during subsequent migration passes. Submission status values from GoCanvas — Draft, Submitted, and Archived — map directly to a custom pick-list field on the Salesforce record.

GoCanvas user accounts are matched by email address to existing Salesforce User records during the pre-migration user-resolution phase. Any GoCanvas user that does not have a corresponding Salesforce User is flagged in a detailed user-resolution report for manual review or automated fallback assignment. Submissions originating from unresolvable users are assigned to a designated fallback Salesforce User or a dedicated 'GoCanvas Migration' service account to ensure data integrity and audit compliance.

Photos, signatures, and uploaded files attached to GoCanvas submissions are downloaded from GoCanvas cloud storage and re-uploaded to Salesforce as Salesforce Files using the ContentDocument and ContentVersion objects. Each file is linked to the parent submission record via a ContentDocumentLink with AllUsers visibility to ensure accessibility across the organization. PDF exports of completed submissions are stored as Salesforce Attachments for reference, separate from the native Files architecture.

Each GoCanvas form field becomes a Salesforce Custom Field on the custom object. Field type mapping: Short/Long Text → Text(255) or TextArea; Number → Number; Date/Time → DateTime; Dropdown → Picklist; Checkbox → Checkbox; Barcode/Scan → Text. Calculated fields become Formula fields.

GoCanvas Reference Data, which provides spreadsheet-backed lookup tables for form fields, migrates to Salesforce as either Custom Objects or Custom Metadata Type records. Static reference data that rarely changes — such as equipment types, inspection categories, or facility codes — is stored as Custom Metadata Type records for queryability by Flow without record access. User-editable reference data migrates as Custom Object records, and pick-list value sets are built from the migrated rows.

GoCanvas Groups map to Salesforce Public Groups to preserve sharing-rule parity for form access and submission visibility. Groups with territory assignment or dispatch-oriented semantics — such as regional teams or role-based dispatch pools — are mapped to Salesforce Queues to enable work routing and load balancing. A mapping table is generated during discovery, listing each GoCanvas group name, member count, and the recommended Salesforce group type.

GoCanvas Workflow handoffs have no Salesforce native equivalent. FlitStack exports the complete handoff history (submitter, handoff target, timestamp, status) as a JSON field on the submission record and as a separate custom object for admin review. The admin rebuilds routing logic in Flow using this as a reference.

GoCanvas Automations, which include form-submit triggers, email notifications, and conditional field routing logic, are exported as a JSON specification for each automation defined in the account. FlitStack documents the trigger conditions, action types, recipient rules, and any conditional branches for every automation. Your Salesforce admin or FlitStack uses these specifications to design and configure equivalent Record-Triggered Flows or Scheduled Flows in Salesforce, ensuring that automation logic is preserved post-migration.

Salesforce's native CreatedDate field reflects the timestamp when records are inserted during migration, not the original GoCanvas submission date. To maintain reporting continuity and audit trails, FlitStack preserves the original GoCanvas submission timestamp in a custom DateTime field named Original_Submission_Date__c on each record. Similarly, the original GoCanvas Last Modified date is stored in Original_Last_Modified__c. All Salesforce reports and list views that rely on historical submission timing reference these custom fields.

GoCanvas tracks form version changes that affected submissions. This version history is preserved as a custom text field (Form_Version_Snapshot__c) on each record, storing the GoCanvas form version ID at time of submission. Salesforce does not natively track form schema versioning.

GoCanvas submission status values — Draft, Submitted, and Archived — map directly to a custom pick-list field on the Salesforce submission record. Archived submissions are migrated with their Archived status preserved to maintain historical records in Salesforce. Draft submissions are migrated as-is only if explicitly requested in the project scope; by default, FlitStack migrates only Submitted records to ensure that Salesforce contains active, production-relevant data upon go-live.