Migrate from Berry crm to Pipedrive

Berry CRM Contact records map to Pipedrive Person objects. Standard fields (name, email, phone, address) map directly. We resolve the Contact-to-Company link from Berry CRM and attach the Person to the corresponding Pipedrive Organization record after the Organization import phase completes. Any custom fields on Contact are flagged for explicit type resolution against Pipedrive's custom field type system before the Person import batch runs.

Berry CRM Company records map to Pipedrive Organization objects. Company name maps to Organization name, domain or website maps to the Organization website field, and any custom fields migrate as Pipedrive Organization-level custom fields. We import Organizations before Persons so that the Organization-Person relationship is satisfied at insert time, preventing orphaned Persons without an Organization link.

Berry CRM Deals map to Pipedrive Deals with the stage name mapping handled as a pre-import configuration step. We create a Pipedrive pipeline matching the Berry CRM pipeline structure (or the default pipeline if only one exists), set stage names to match the source stage labels, and import deal amount, close date, and owner by resolving the Berry CRM owner email to a Pipedrive user. The deal-organization and deal-person associations migrate as linked Activity records.

If Berry CRM contains multiple deal pipelines, we configure the equivalent Pipedrive pipelines before Deal import begins. Each Pipedrive pipeline gets its own stage set matching the source pipeline's stage names. Pipedrive supports multiple pipelines from Lite tier, so there is no tier constraint on the destination side.

Berry CRM Sales Quotes migrate to Pipedrive Deals with line items represented as Products attached to the Deal. Quote totals and status (draft, sent, accepted, rejected) are preserved as Deal custom fields or Activity notes. Pipedrive's native quote generation requires the Smart Docs add-on; if the customer does not have Smart Docs, we preserve the quote content as structured data in a custom field set rather than attempting to generate PDF output.

Berry CRM Product catalog entries map to Pipedrive Products. Product name, description, and pricing migrate directly. If the source product has multiple Price Book entries (different prices per list), we create the equivalent Pipedrive Price Books and link them to the Product before import. Inactive or archived products are imported with an inactive flag for the customer to review post-migration.

Berry CRM Price Books map to Pipedrive Price Books. We handle the Price Book-to-Product relationship by creating the Price Book first, then attaching Product price entries to it. Pipedrive supports multiple price lists per product; we preserve the source pricing hierarchy so that the customer's catalog structure is intact in Pipedrive.

Berry CRM Project records map to Pipedrive Projects if the destination Pipedrive account has the Projects add-on enabled on Growth, Premium, or Ultimate. Project metadata (name, status, description) migrates directly. Tasks associated with a Project migrate as Project tasks within Pipedrive. If the customer does not have the Projects add-on, we flag Projects for the scoping call to determine whether Projects should migrate as Activities or as Deals with a project-type tag.

Berry CRM Task records map to Pipedrive Activity entries with type Task. We preserve task title, due date, assignee (resolved by email match to Pipedrive user), completion status, and any linked Contact, Company, or Deal associations. Activities are imported after the parent Contact, Organization, and Deal records exist to ensure the correct Person and Organization IDs are available for linking.

Berry CRM Invoices have no direct Pipedrive native equivalent unless Smart Docs is enabled. We handle Invoice migration as a structured data import: invoice number, line items, totals, payment status, and due date migrate as a set of custom fields on an Activity record linked to the relevant Person and Organization. The customer should confirm whether Smart Docs will be used post-migration for formal invoice generation; if so, we flag the invoice data for Smart Docs template population.

Berry CRM custom fields on any primary object are detected during the discovery export phase and mapped to Pipedrive custom fields of the corresponding type. Pipedrive requires custom fields to be created before data import, so we handle schema provisioning as a pre-import step. Field types (text, numeric, date, single-select, multi-select, address) are inferred from the source data values and confirmed against the customer's scoping input before the migration pipeline runs.