Migrate from Formitize to Pipedrive

Formitize Clients (business-level records containing company name, address, and billing information) map directly to Pipedrive Organizations using a one-to-one field translation. The Formitize Client ID is stored as a custom field called Source_System_ID__c on the resulting Pipedrive Organization, enabling delta-run de-duplication checks and post-migration traceability back to the original Formitize record.

Formitize Contacts are person-level records linked to a parent Client, containing name, email address, phone number, and job title. Each Contact maps to a Pipedrive Person record directly. The Formitize Contact's linked Client ID is resolved to the corresponding Pipedrive Organization ID before the Person record is written, establishing the correct Person-Organization linkage in Pipedrive.

Formitize custom fields defined on the Client module (dropdowns, text fields, date fields, variables) are read from the Client export. Each is created as a matching Pipedrive Organization custom field before data import runs, using the same field type and pick-list values where applicable.

Formitize Contact-level custom fields (such as birthday, custom flags, and lead source) are migrated to Pipedrive Person custom fields. Pipedrive creates these as custom fields on the Person object using the same name and field type, so column auto-mapping picks them up during the import pass without manual reconfiguration.

Formitize Jobs (tracked work items with status, due date, assigned user, and linked Client/Contact) map to Pipedrive Deals. The Job name becomes the Deal title. Job status maps to Pipedrive Stage values, with open/active Jobs mapping to the active pipeline stage and closed Jobs mapping to a Won or Lost stage as appropriate.

Formitize Job custom fields (job type, priority, custom data captured on the job form) are pre-created in Pipedrive as Deal custom fields before migration. Pipedrive's API requires retrieving the system-generated field key before writing values, so field key resolution happens during the pre-migration schema step.

Formitize's Sales Pipeline with named stages (e.g. Prospecting, Quote Sent, Job Booked) becomes a Pipedrive Pipeline with matching stage names. We create the Pipedrive pipeline and its stages first, then map Job records to the corresponding stage by evaluating Job stage-name strings. If stage names differ between platforms, a value-mapping table maps each Formitize stage label to the equivalent Pipedrive stage label.

Formitize records for Calls, Meetings, and Tasks carry subject, timestamp, duration, outcome notes, and assigned user. These map directly to Pipedrive Activities with matching type values. The linked Formitize Job ID is preserved in the Pipedrive Activity's deal_id field so activity history stays associated with the correct Deal.

Formitize Assets (equipment records with GPS coordinates, zones, client link, and custom fields) have no native Pipedrive equivalent. We create a Pipedrive custom object named Asset or map key asset fields (asset name, location, zone, GPS lat/long) to Organization custom fields. GPS coordinates cannot render as a map field in Pipedrive — they are stored as text lat/long fields for reference.

Formitize's Workflow module (multi-stage compliance processes, incident reporting, form-to-job routing, auto-task actions) has no migration path to Pipedrive. Pipedrive Automations and Sequences handle deal-stage triggers and email sequences but not field-service or compliance process logic. We export Formitize workflow definitions as a structured document so your Pipedrive admin can rebuild the equivalent logic using Pipedrive's Automation builder.

Formitize Smart Forms with conditional routing, QR-code intake, client portal links, and job-trigger logic cannot be imported into Pipedrive. Pipedrive's LeadBooster Web Forms are a separate product (requires Growth+ plan) with a different builder. We document the Formitize form schema (field names, conditional rules, submission targets) so your team can recreate the equivalent in Pipedrive's form builder or a third-party form tool integrated via API.

Formitize users (staff members assigned to Jobs, Contacts, and Workflows) are matched to Pipedrive users by email address. The migration plan flags any Formitize user without a corresponding Pipedrive account before migration runs — those records are assigned to a fallback Pipedrive user or held for admin to create the account first.