Migrate from GoCanvas to Mailchimp

GoCanvas users who submitted forms with identifying information (name, email) map directly to Mailchimp members. The email address is the primary key for deduplication. Members receive the subscribed status on import unless explicitly flagged as unsubscribed in GoCanvas. Original GoCanvas user ID preserved as a custom merge field for delta-run traceability.

Each GoCanvas submission becomes a single Mailchimp member — not a separate record. Form field names become merge field definitions in Mailchimp (e.g., INSPECTION_RESULT, VEHICLE_MILEAGE). Multiple submissions from the same email collapse to one member with the most-recent submission values or all values stored as comma-separated merge field entries, per your configuration choice.

GoCanvas form field definitions (text, number, date, dropdown, multi-select, photo, signature, barcode) each require a corresponding Mailchimp merge field. Mailchimp supports TEXT, NUMBER, DATE, PHONE, ADDRESS, and IMAGE merge field types. Photo and signature fields cannot store binary data — FlitStack exports these as downloadable URLs in a TEXT merge field or external storage reference.

GoCanvas Reference Data sheets that power dropdown fields map to Mailchimp groups (audience-wide categories) or static merge field value lists. Since Mailchimp Reference Data has no live-sync equivalent, FlitStack imports the current snapshot as a static group or pick-list. Ongoing updates require manual Mailchimp group maintenance or re-import.

The GoCanvas submission date maps to a DATE-type merge field (e.g., LAST_SUBMISSION_DATE) for use in Mailchimp segmentation. The earliest submission date can alternatively map to the Mailchimp member_since timestamp, which is read-only — FlitStack uses the most-recent submission date for timestamp merge fields.

The GoCanvas form name becomes a Mailchimp tag applied to each member from that form (e.g., tag: 'Equipment_Inspection_Form'). Tags enable segmentation across forms — all members tagged with a specific form name can receive targeted campaigns. Alternatively, form names map to Mailchimp groups for group-based audience segmentation.

GoCanvas GPS coordinates captured on submissions split into Mailchimp ADDRESS merge fields (street, city, state, zip) when address components are present. Raw coordinates without address components store as a TEXT merge field or tag with lat/long values. Address-based segmentation in Mailchimp requires the full ADDRESS merge field type.

GoCanvas electronic signatures and photo captures store as binary files with no Mailchimp equivalent. FlitStack exports these to cloud storage (S3-compatible or your specified endpoint) and stores the download URL in a TEXT merge field on the member record. Recipients access files via link rather than inline attachment — this is a known limitation with no native Mailchimp resolution.

GoCanvas Workflow routes submissions through handoff sequences with conditional approvals and escalation notifications. Mailchimp Customer Journeys handle email automation triggered by member actions, not submission routing or approval chains. FlitStack does not migrate workflow configurations — your team should document current workflow logic for manual rebuild in Mailchimp Customer Journeys or a separate workflow tool.

GoCanvas Dispatches assign form submissions to workers with scheduling, status tracking, and job handoff. Mailchimp has no job-dispatch or task-assignment model. Dispatch records with relevant contact information can be stored as custom merge fields or exported separately, but the routing and status-tracking logic cannot be replicated in Mailchimp.