Migrate from FowCRM to Pipedrive

FowCRM Account records map directly to Pipedrive Organization. The account name becomes Organization name, and we preserve all standard and custom properties attached to the Account model. Organization is the first object imported because Contacts, Deals, and Cases all reference it as a parent. We run FowCRM's Model enumeration step first to ensure all Account-level custom fields are captured before export begins.

FowCRM Contact records map to Pipedrive Person. Each Contact carries a required link to an Account, which we resolve to the corresponding Organization during import by matching account_id to the Organization ID generated during the Account import phase. Custom properties on the Contact model are enumerated via FowCRM's Fields endpoint after the Model enumeration step, and all typed fields (picklist, text, date, number) are matched to Pipedrive Person custom fields.

FowCRM Deal records map to Pipedrive Deal with the pipeline and stage preserved. We map FowCRM pipeline stages to the corresponding Pipedrive Pipeline and Stage values, creating the Pipeline in Pipedrive before Deal import if it does not already exist. Probability percentages migrate from FowCRM to Pipedrive Stage probability fields. Deals referencing closed-won or closed-lost states carry their final status and are imported as closed with historical timestamps preserved.

FowCRM Pipelines with their configurable stage names, stage order, and probability fields are mapped to Pipedrive Pipelines with corresponding Stages. We create the Pipedrive Pipeline definition first using Pipedrive's pipeline API endpoint, then populate Stages with matching names and probability values. Stage mapping configuration is validated against Pipedrive's allowed stage count per pipeline before migration begins.

FowCRM Cases (also called Requests and Complaints) are only available on Professional and Enterprise plans. During discovery we detect the source plan tier; if the Standard plan is active, the Cases API endpoint returns 403 and we skip the object gracefully. If Cases are present, they map to Pipedrive Deals (if no Service Cloud add-on) or to Pipedrive Cases (if Service Cloud is active on the destination account). Case status, priority, and custom case-type fields are mapped to corresponding Pipedrive custom fields or Deal properties at migration time.

FowCRM Activity records (calls, emails, notes) linked to Contacts or Accounts migrate to Pipedrive Activities attached to the corresponding Person, Organization, or Deal. We resolve the parent record reference by matching FowCRM's contact_id and account_id to the Pipedrive Person and Organization IDs generated during earlier import phases. Activity timestamps (start time, duration for calls) are preserved in Pipedrive Activity fields. Email content migrates as Activity description text; call notes and dispositions migrate as custom Activity fields.

FowCRM Custom Fields are defined per Model and require a two-step API discovery process: enumerate all Models first, then fetch Field definitions for each Model individually. We execute this discovery step before any data export, building a complete model-to-field index. Custom field types (picklist, text, date, number) are matched to equivalent Pipedrive custom field types. Pipedrive custom fields are created via the API before data import begins so that field IDs are available at mapping time.

FowCRM Survey definitions and response data are available on Professional and Enterprise plans. Survey schemas differ significantly between platforms, so we treat Survey data as a mapping exercise rather than a direct data migration. We export Survey definitions as structured JSON and deliver a written schema mapping document to the customer, identifying which Pipedrive form tools or custom objects can replicate the survey structure. Response data is delivered in a structured export for manual re-entry or integration via Pipedrive's web form and data import tools.

FowCRM User records (email, role, department) are exported and matched to Pipedrive Users by email address. Owner-to-deal and owner-to-contact assignments are preserved via the user_id reference, which maps to Pipedrive OwnerId. A pre-migration user alignment session is recommended because FowCRM role hierarchies do not have a direct Pipedrive equivalent and may require admin to map to Pipedrive's admin and regular user permission levels.

FowCRM integration configurations and webhook subscriptions are not exposed via the public API and cannot be extracted programmatically. We do not migrate integrations or webhooks. We deliver a written inventory of detected webhook endpoints and integration configurations for the customer's admin to reconfigure in Pipedrive post-migration using Pipedrive's webhooks API and the Marketplace integrations catalog.