Migrate from ContactWise CRM to Pipedrive

ContactWise Contacts map to Pipedrive Person records. Standard fields (name, email, phone, address, company association) map field-to-field. ContactWise's purchase_history and custom demographics properties require pre-creation of custom fields in Pipedrive before import. We run deduplication on email as the primary key. Owner assignment migrates by resolving ContactWise owner email to Pipedrive user email.

ContactWise Leads are distinct from Contacts and include status attribution and source fields. They map directly to Pipedrive Lead records with lead_status and source properties preserved as custom fields in Pipedrive. If the customer prefers to work without Pipedrive Leads enabled, Leads merge into Person records and the original lead source is stored in a custom property.

ContactWise Opportunities map to Pipedrive Deals. We preserve deal name, amount, expected close date, stage, owner, and linked Contact and Company associations. Pipeline stage mapping uses a stage table built during discovery, where each ContactWise pipeline stage name maps to a corresponding Pipedrive Deal stage in the configured pipeline. The deal probability migrates as a custom field if the customer's Pipedrive plan does not expose stage probabilities natively.

ContactWise Company records map to Pipedrive Organization. The organization name, domain, address, phone, and industry fields map directly. We create the Organization in Pipedrive before the Contact import so that the person-organization association is satisfied at insert time. Owner assignment migrates by email resolution.

ContactWise pipeline stage definitions are configurable and are documented during discovery as a stage mapping table. Each ContactWise stage name maps to a Pipedrive Deal stage within the customer's configured pipeline. We create the Pipedrive pipeline with matching stage names before Deals import begins. Stage probability percentages are stored as custom fields on Pipedrive Deals if the customer requires historical probability data.

ContactWise Workflow rules store automation logic as platform configuration rather than data records. We document every active Workflow during discovery — including trigger type (time-based, field-change, action-based), conditions, and resulting actions — and deliver a written automation inventory with each rule described in Pipedrive Automation-compatible language. The customer's Pipedrive admin rebuilds the automations in Pipedrive's Automation Rules or through a partner implementation.

ContactWise Tickets do not map to a native Pipedrive object. Pipedrive does not include a native service desk or case management object in its core CRM. We work with the customer during scoping to choose one of three approaches: (1) map tickets to a custom field group on Deals with ticket number, status, priority, and description; (2) create a separate Pipedrive Deal per ticket with a 'Support Request' label; or (3) use Pipedrive's Productboard integration for ticketing if the customer already uses or plans to adopt Productboard. The chosen approach is confirmed before migration and the mapping table is validated in a test pass.

ContactWise Time Entries are linked to Contacts, Tickets, or Projects. Pipedrive has no native time-tracking object. We export time entries to a structured format and either attach them as Notes linked to the parent record (Person, Organization, or Deal) or create custom fields on the relevant object for billable hours and time-entry metadata. The customer selects the approach during scoping based on their reporting needs.

ContactWise documents and attachments associated with Contacts, Opportunities, or Companies are exported to cloud storage and uploaded to Pipedrive as Files attached to the corresponding Person, Organization, or Deal record via Pipedrive's file attachment API. File metadata (filename, upload date, linked record) is preserved in a migration manifest for the customer's records. Large file sets may require multiple batch uploads with exponential backoff on API limits.

ContactWise users referenced on Contacts, Leads, Opportunities, and Tickets are mapped to Pipedrive Users by email address. We extract the complete owner roster from ContactWise during discovery and reconcile against the Pipedrive account's user list before migration begins. Any ContactWise owner without a matching Pipedrive user is held in a reconciliation queue for the customer's admin to provision before record import proceeds.