Migrate from GoCanvas to Nutshell

Every GoCanvas submission containing a submitter email, name, or phone becomes a Nutshell Person record. The primary Person is identified by the submitter's user account when available, or by the most complete contact block found within the submission fields. Multiple submissions from the same email address are linked to a single Person record rather than creating duplicates.

Submission fields named or formatted as company identifiers (company name, domain, address) extract to a Nutshell Company record. When a submission references a company name without a domain, the Company is created with that name and left without a website — the website field is populated only when a domain is present in the submission data.

GoCanvas user accounts identifying the submitter are resolved against Nutshell users by email match. Where a GoCanvas submitter email matches a Nutshell user, the Nutshell Person record is assigned that user as owner. Unmatched submitters are flagged for manual owner assignment before the migration commits.

GoCanvas has no single-contact object — every field lives inside a submission. The originating form name is preserved as a custom text field on the Nutshell Person record so teams can trace which GoCanvas form generated each contact. Multiple forms may map to the same Person if that contact submitted through several forms.

The original GoCanvas submission timestamp is preserved as a custom datetime field on the Nutshell Person record. This maintains reporting continuity for teams tracking when a contact first entered the system via a GoCanvas form, and allows historical analysis of submission timing across the CRM.

GoCanvas captures GPS latitude and longitude at submission time. These coordinates are stored as a custom text field in Nutshell in 'lat, lng' format. If the submission also contains a parsed street address, the address is mapped to the Person's standard address fields and the coordinates are retained as supplementary reference.

GoCanvas Reference Data files uploaded to power dropdown and cascading fields are exported as value lists and loaded into Nutshell as custom pick-list field options. Each Reference Data file becomes one Nutshell custom pick-list field; the field name is derived from the Reference Data file name. Cascading (dependent) Reference Data relationships are not natively supported in Nutshell and are surfaced as a flat pick-list with a note for the admin.

Photos, signatures, and PDF exports attached to a GoCanvas submission are downloaded and re-uploaded to the corresponding Nutshell Person record as file attachments. Each file link in Nutshell points to the original file URL stored during migration. File size limits follow Nutshell's attachment constraints.

GoCanvas submissions containing repeating table rows (multiple sub-rows within a single submission) cannot map to a single Nutshell record. We flatten each table row into a structured text block and attach it as a Nutshell Note on the primary Person record. The Note includes the table column headers and all row values so the full dataset is preserved.

Long-text fields captured in GoCanvas submissions — inspection notes, comments, description fields — migrate as Nutshell Notes attached to the corresponding Person record. The original field label from the GoCanvas form is prepended to the Note body for traceability and retrieval.

Barcode scan values, digital signatures, and captured photos from GoCanvas submissions are stored as files and attached to the Nutshell Person record. Barcode values are additionally captured in a custom text field for searchability. Signatures are stored as PNG image attachments.

GoCanvas groups control which users can access which forms — this is an access-control concept with no direct Nutshell equivalent. Form-level access rules cannot be migrated; teams rebuild access control using Nutshell's roles and team features post-migration. The migration documentation captures group names and membership so administrators can assign the same users to equivalent Nutshell roles, ensuring consistent permissions across the new CRM environment.

GoCanvas Workflow defines sequential handoffs of a submission between users before final submission. Nutshell has no equivalent multi-step handoff construct. The workflow definition is exported as JSON for reference; Nutshell Sales Email sequences can replicate some trigger logic but manual rebuild is required.

Submissions submitted without an identifiable contact email — for example, anonymous inspection submissions — have no basis for a Nutshell Person record. These submissions are converted to Notes on the relevant Company record where a company is identifiable, or exported as standalone notes if no link exists.