Migrate from GoCanvas to HubSpot

GoCanvas stores the submitter's name and email on every submission. FlitStack AI resolves the submitter email to a HubSpot contact by email lookup. If no matching contact exists, one is created. The original GoCanvas submitter ID is preserved as a custom property on the contact for traceability.

The submission as a whole has no direct HubSpot equivalent. Depending on your use case, it maps to a HubSpot Ticket (for support/service submissions) or a custom object (for inspection records, audit logs, or project deliverables). FlitStack AI creates the custom object schema in HubSpot before migration if you choose the custom-object path.

Each GoCanvas form field becomes a HubSpot custom property on the target object (Contact, Ticket, or custom object). Field types map to HubSpot property types: text fields to single-line text, numeric fields to number properties, date fields to date properties, dropdown fields to single-option picklists, and multi-select fields to HubSpot multi-checkbox properties.

Form name, form version, and submission ID are preserved as HubSpot properties: Form_Name__c (single-line text), Form_Version__c (single-line text), and Submission_ID__c (single-line text). These enable deduplication on re-migration and traceability back to GoCanvas. Each property is indexed for fast retrieval, and their values are used in HubSpot reporting to segment submissions by origin form and version.

Photo and document attachments from GoCanvas submissions are downloaded and re-uploaded to HubSpot Files, then linked to the target CRM record. File size limits depend on your HubSpot plan. Images embedded in submission PDFs are extracted and uploaded individually where the form structure allows.

GoCanvas captures GPS coordinates when the mobile device has location permission enabled. We map latitude and longitude to two custom number properties (Submission_Latitude__c, Submission_Longitude__c) on the target record. HubSpot does not have a native map field — these values are stored for use in HubSpot Analytics or external map integrations.

GoCanvas user records (name, email, group membership) are matched to HubSpot users by email. A HubSpot user must exist for every owner assignment. Unmatched GoCanvas users are flagged before migration — your team either creates HubSpot user accounts first or assigns records to a designated fallback HubSpot user.

GoCanvas user groups map to HubSpot Teams. Team membership determines which HubSpot users can view and edit records. We preserve group-to-user membership and re-create the team structure in HubSpot before assigning records. Group names are transferred verbatim, but you can rename teams in HubSpot after migration if needed. HubSpot Teams support hierarchical nesting, so any nested GoCanvas groups can be mirrored using HubSpot sub‑teams for fine‑grained access control.

GoCanvas Dispatches — pre-scheduled form assignments sent to field workers — map to HubSpot Tasks linked to the corresponding contact or deal. Dispatch status (pending, in-progress, completed) becomes the Task status in HubSpot. If a Dispatch includes a due date, the due date maps to the Task due date field, enabling field teams to track deadlines directly within HubSpot.

GoCanvas Reference Data provides dropdown options from an uploaded spreadsheet. These option values map to HubSpot picklist options on the corresponding property. If the Reference Data sheet exceeds HubSpot picklist limits, we split the options across multiple single-option or multi-checkbox properties.