Migrate from GoCanvas to Pipedrive

GoCanvas submissions have no native CRM objects — mapping requires a business decision about what submissions become in Pipedrive

GoCanvas stores data as form submissions with per-form JSON schemas. Pipedrive enforces a fixed Person-Organization-Deal object model where fields must be declared before import. There is no standard rule for what a GoCanvas inspection submission or safety-check form becomes — it could be a Person record (for lead capture), an Organization record (for a job site), or a Deal (for a sales opportunity). FlitStack surfaces this decision in the migration plan: we map submitters to Persons, company fields to Organizations, and leave the object role of each form open for your team to specify before we run the import. This is a migration-planning conversation, not an automated decision.

Pipedrive custom fields use 40-character hash keys — they must be pre-created in Pipedrive before bulk import

Pipedrive's API references custom fields by a randomly generated 40-character hash key, not by the human-readable field name. When GoCanvas exports a field named 'Job Site Address', Pipedrive requires that a custom field with that label already exists in the account — the hash key must be fetched via Pipedrive's API before the bulk import can reference it. FlitStack creates all custom fields via the Pipedrive API in a pre-migration step, captures the hash keys, and uses those keys in the import payload. If your GoCanvas forms have 20+ fields each, this pre-creation step adds planning time because Pipedrive also inherits deal custom fields to Leads automatically — field scope must be defined per form.

GoCanvas Workflow Handoff chains have no Pipedrive equivalent and cannot be migrated

GoCanvas Workflow enables multi-step Handoff chains where a submission passes from one user to another for review or approval before final submission. This is a GoCanvas-native routing mechanism with no analogue in Pipedrive's Automation builder. Pipedrive Automations trigger on field changes or deal stage updates — they do not support a human-handoff queue model. FlitStack exports GoCanvas workflow definitions as a structured reference document listing each Handoff step, the assignee, the condition logic, and the notification settings. Your Pipedrive admin must rebuild this logic manually in Pipedrive Automations using the exported reference. The submission history (who touched the record and when) is preserved as Notes on the Person record.

Pipedrive's December 2024 token-based rate limits govern bulk import throughput

Pipedrive introduced token-based API rate limits in December 2024 that apply to both new and existing accounts. The limit scales with plan tier — Essential accounts have lower throughput than Enterprise accounts. FlitStack throttles bulk writes to stay within the per-token ceiling, batching records and pacing API calls. For migrations with 50,000+ submissions, this throttling extends the migration clock time. We surface the rate-limit constraint in the migration plan and provide a realistic throughput estimate based on your Pipedrive plan tier before the migration starts.

GoCanvas auto-generated PDFs and embedded media require individual download-and-re-upload

GoCanvas generates a PDF for every submission and stores photos, signatures, and attachments in GoCanvas cloud. Pipedrive has no native PDF auto-generation — submitted PDFs must be downloaded from GoCanvas and attached manually to the corresponding Pipedrive record via the Pipedrive Files API. For submissions with multiple photos or embedded signatures, each media asset requires a separate API call to download and a separate call to attach. Migration runs with heavy media usage (inspection forms, safety checklists with photos) take longer because each attachment is processed individually. We estimate attachment-processing time based on the ratio of media-bearing submissions in the source data before the migration starts.