Migrate from Method CRM to Pipedrive

Method CRM Contacts map directly to Pipedrive Person records. The Contact's name, email, phone, address, and custom fields migrate 1:1. We use the Contact email as the primary dedupe key. Any Contact without an email address is flagged in the reconciliation report for the customer to supply or merge.

Method CRM Companies map to Pipedrive Organizations. The Company name, domain, address, and custom fields migrate directly. We resolve the Organization ID for each Company before Contact migration begins so that Person records can be linked to their parent Organization via the org_id field.

Method CRM Opportunities map to Pipedrive Deals. The Opportunity amount, close date, stage name, and owner assignment migrate directly. Pipedrive Deals are attached to an Organization (required for the Organization link) and optionally to a Person; we resolve both references from the migration's Company and Contact mapping before Deal inserts.

Method CRM pipeline stages are enumerated values on Opportunities. We create matching Pipedrive pipeline stages before Deal migration, preserving the stage name and order. Pipedrive stages carry a default probability percentage; we adjust these to match Method CRM's stage probabilities where data exists.

Method CRM Activities map to Pipedrive Activities using the activity type field to set the correct Pipedrive Activity type (call, meeting, task, note). Activity date, description, and owner assignment preserve. Each Activity is linked to its parent Person or Organization using the WhoId and OrgId fields resolved from the Contact and Company migration. Email activities migrate as notes with a [Email] prefix in the subject.

Method CRM Estimates have no direct Pipedrive equivalent because Pipedrive lacks a native estimate or quote object. We migrate Estimate line items as Pipedrive Deal Products linked to the corresponding Deal. The Estimate status and QB linkage metadata are preserved as custom fields on the Deal for the customer's admin to reference. Any Estimate with an active QB linkage is flagged for manual review because that linkage cannot be restored in Pipedrive.

Method CRM Invoices have no native Pipedrive equivalent. We migrate Invoice header data (invoice number, date, total, balance due) as custom fields on the linked Deal, and line items as Deal Products. Paid invoices are set to a Won status on the corresponding Deal. Invoices with active QB linkage are flagged separately because the payment reconciliation history does not transfer.

Method CRM Sales Orders are available on Pro and Enterprise. Pipedrive has no native Sales Order object. We migrate Sales Order records as Deals with a custom field so_sales_order_number__c and line items as Deal Products. The original Sales Order status migrates as a custom field value for the admin to interpret post-migration.

Method CRM custom fields on Contacts, Companies, and Opportunities map to Pipedrive custom fields. We pre-create all destination custom fields with matching data types (text, number, date, dropdown) before any data import. Pipedrive custom fields are shared between Deals and Leads; if the customer uses Leads, we verify that custom field visibility is correct for both record types. Pipedrive Important Fields that reference missing data will display warnings in the UI but will not block record creation.

Method CRM Users map to Pipedrive Users by email address match. We run owner reconciliation before the main migration: any Method CRM owner without a matching Pipedrive User is held in a reconciliation queue. Pipedrive requires that users already exist in the account before the migration runs; if the migration is initiated before Pipedrive Users are provisioned, all records are owned by the initiating admin account. The customer provisions Pipedrive users before migration begins.

Method CRM tags on Contacts and Companies migrate as flat string labels to Pipedrive Labels. Labels are stored as a list on the Person or Organization record. We extract all distinct tag values, create them in Pipedrive, and associate them with the migrated Person and Organization records.

Method CRM Files are exported via the Files API with binary content and metadata preserved. We re-associate attachments to the correct parent Person or Organization in Pipedrive. File content migrates as a Pipedrive File record linked via a note or activity. Files larger than 25 MB may require chunked upload handling; we flag oversized files in the discovery report.