Migrate your GoCanvas data

Forms are the schema container defining all field types, conditions, calculations, and Reference Data bindings. We export the full form definition as JSON including screen layouts and field metadata, then recreate it at the destination. Custom fields are preserved as first-class properties.

Submissions are the core record in GoCanvas — each represents one completed form instance with all field values, timestamps, and submitter attribution. We export every submission with its associated PDF link and integration response payloads. The destination receives each submission as an independent record.

GoCanvas Users have login credentials, group memberships, and form-access controls. We map User records to destination contacts but note that GoCanvas User schema is minimal (no address or company fields). If the destination requires rich contact profiles, we merge submission submitter data to enrich each User record during migration.

Devices can be licensed as user-equivalents under Team Licenses, enabling a tablet to submit forms without a named-user login. We capture device-to-submission associations and map them to destination users or locations. Device metadata (device type, OS) is preserved as a custom field on the destination record.

Groups control which users can access which forms. We export the group hierarchy and rebuild it at the destination using destination-native team or role constructs. Group-to-form assignment is preserved as a mapping table.

Dispatches assign work to field users, including location data and navigation links. API v3 supports creating and retrieving Dispatches as objects. We export all open and historical Dispatches and map them to destination work orders or task records, preserving location coordinates and address fields.

Workflows define multi-step handoff chains where one user approves or edits a submission before it is finalized. We export the full workflow definition including handoff sequence, notification settings, and the handoff history for each submission. Workflow rules require manual rebuilding at most destinations since destination platforms do not share GoCanvas's handoff concept natively.

Reference Data attaches spreadsheet-backed dropdown lists, barcode lookups, and dependent field logic to forms. We export Reference Data CSVs alongside the form schema. If the destination supports lookup tables or custom picklists, we map Reference Data values to equivalent destination constructs; otherwise we flatten them to static picklist values at migration time.

GoCanvas Departments segment users, forms, and submissions within an account. We export the department tree and assign destination records to the corresponding department. Accounts without departments export cleanly under a single root.

PDFs (Standard, Designer, and Custom PDF) are output artifacts generated from submission data. We do not migrate PDF templates themselves. We preserve the submission data so PDFs can be regenerated from the destination platform. Any Custom PDF logic tied to specific form versions is documented as a custom post-migration step.

GoCanvas integrations push submission data to downstream systems (e.g., ERP connectors, Zapier, SharePoint). Integration configurations are exportable as connection metadata. We document active integrations so they can be reconfigured against the new data source after migration. Integration credentials must be re-entered on the destination platform.