Migrate from GoCanvas to Odoo CRM

GoCanvas submissions are the primary data record. Each submission containing identifiable contact fields (name, email, phone) maps to one Odoo crm.lead. The Form name becomes preserved in a custom char field (x_gocanvas_form_name) on the lead for reporting continuity. Submissions without contact data map to lead records with x_gocanvas_form_name only — your team decides whether to merge these into existing leads by submitter.

GoCanvas stores submitter name, email, and phone per submission — not as a standalone contact object. When the same submitter appears across multiple submissions, FlitStack de-duplicates into a single res.partner record and links all corresponding crm.lead records to that partner_id. If a submitter email maps to an existing Odoo partner, the lead links to the existing record. This prevents duplicate contacts in Odoo.

GoCanvas submission status values (Pending, Submitted, Approved, Rejected) map to Odoo crm.stage records via a value-by-value mapping: Pending → New, Submitted → Qualified, Approved → Won, Rejected → Lost. Your Odoo admin creates these stages in the pipeline before migration. Custom GoCanvas statuses get mapped to a configurable stage or preserved as a custom selection field on the lead.

GoCanvas Form definitions have a name and version. Since Odoo CRM has no Form concept, the form name is stored as a custom char field x_gocanvas_form_name on crm.lead. This allows Odoo reports and filters to group leads by the originating GoCanvas form without requiring a separate Form object.

GoCanvas form builder supports text, number, dropdown, photo, signature, barcode, and calculation fields. Odoo CRM custom fields (x_studio fields) handle char, float, selection, binary, and datetime types natively. We deliver a custom field creation plan per form before migration — fields like photo and signature map to Odoo ir.attachment records linked to the lead rather than stored as field values.

GoCanvas captures device type, OS version, and GPS coordinates per submission. These map to custom char and float fields on crm.lead. Latitude and longitude are useful for Odoo geo-filtering and map integrations if your team installs a geo-mapping module. Device type data helps identify which form versions are in use and whether submissions originate from mobile or desktop clients.

Files attached to GoCanvas submissions are re-uploaded as ir.attachment records linked to the corresponding crm.lead. Photos and signatures become binary attachments; PDF exports of submissions become ir.attachment with mimetype application/pdf. The original filename and submission date are preserved in the attachment's name and create_date fields.

GoCanvas records a submission date (UTC) per submission. Odoo's create_date on crm.lead reflects the migration run date, not the original submission date. We preserve the original GoCanvas submission timestamp in a custom datetime field x_gocanvas_submission_date so Odoo reports show the true field completion date.

GoCanvas users are tied to submissions as the submitter. In Odoo CRM, the user_id field on crm.lead assigns a sales rep. We match GoCanvas user email addresses to res.users records by email lookup. Unmatched users are flagged before migration — your Odoo admin either creates the user or assigns records to a fallback user.

GoCanvas Reference Data allows form fields to pull values from an uploaded CSV (e.g., product catalog, asset registry). Odoo CRM has no native Reference Data equivalent. We map these fields as plain text char fields on crm.lead — your Odoo admin can rebuild the lookup as a many2one relation to an Odoo product or asset model if needed.

GoCanvas text fields flagged as 'description' or 'notes' within a form map to a mail.message record on the crm.lead with body=note text, message_type=notification, and subtype=mt_note. This keeps notes visible in Odoo's activity timeline on the lead form view. The mail.message approach ensures notes appear chronologically alongside other lead interactions and email communications in the Odoo chatter.

GoCanvas Groups organize users and form access. Odoo crm.team organizes sales reps and pipeline assignments. We map GoCanvas groups to Odoo crm.team records by name, then assign crm.lead.user_id based on the submitter's group membership in GoCanvas. Teams with no direct Odoo equivalent are created as new crm.team records during the migration setup phase.

GoCanvas Workflow enables multi-user handoffs (submit → review → approve) within a single submission. Odoo CRM has no native handoff chain equivalent. Handoff history is preserved as a series of mail.message notes on the crm.lead, but the approval chain structure is not transferred — Odoo approval flows (server actions, automated actions) must be rebuilt separately.

GoCanvas automations trigger email or webhook actions based on form events. Odoo CRM automated actions, server actions, and base.automation rules provide equivalent functionality but must be rebuilt from scratch. We export your GoCanvas automation definitions as a reference document for your Odoo admin to reconstruct them in Odoo's automation studio.

GoCanvas captures how long a submitter takes to complete a form (from first field interaction to submission). This maps to a custom float field x_gocanvas_completion_minutes on crm.lead. Useful for Odoo reporting on form efficiency and identifying bottlenecks in field data collection workflows.