Migrate from Grow CRM to Pipedrive

Grow CRM's Contact object maps directly to Pipedrive Person. Standard fields (name, email, phone, address, tags) migrate cleanly. Grow CRM custom fields on Clients are extracted during scoping from the UI or database, pre-created as matching custom fields in Pipedrive (available from Essential plan upward), and mapped during import. Tags are normalized as comma-separated values in a custom field since Pipedrive's standard plans do not have a native multi-select tag taxonomy. Grow CRM's email-to-contact linking for the client portal does not transfer to Pipedrive because the portal authentication model is destination-specific.

Grow CRM Company records map directly to Pipedrive Organization. Business details (name, domain, address, phone) migrate as standard fields. The foreign key relationship between Grow CRM Contact and Company is preserved at import time by resolving the Organization ID before Contact insert, ensuring each Person is linked to its parent Organization. Pipedrive's Organization supports multiple linked Persons, matching Grow CRM's contact-to-company relationship model.

Grow CRM's separate Lead object from Opportunities requires a split decision during scoping: Leads that have not yet entered an active sales process are migrated as Pipedrive Leads (the default), and Leads that have already been qualified and assigned to an owner are migrated as Pipedrive Persons tied to an Organization. Grow CRM Lead status, source, and owner assignment fields migrate to Pipedrive Lead status and owner custom fields. The split is designed during scoping based on the customer's Grow CRM lead lifecycle.

Grow CRM Opportunities map directly to Pipedrive Deals. Deal value, stage, expected close date, and owner assignment migrate. Grow CRM pipeline stages and probabilities are documented during scoping and pre-configured as Pipedrive pipeline stages with matching probability percentages. Stage history is not natively stored in Grow CRM and cannot be migrated; we document the current stage as the starting point in Pipedrive.

Grow CRM Tasks map to Pipedrive Activities with type Task. Custom fields on Tasks in Grow CRM are extracted during scoping from the UI or database, pre-created as custom fields in Pipedrive (via the Fields API), and mapped during import. Grow CRM's task assignment linking to team members resolves via the User mapping by email match. Pipedrive's Essential plan supports up to 3,000 open deals; we verify the customer's deal volume against the target plan tier during scoping.

Grow CRM Invoices (line items, totals, tax, status, and client link) have no direct Pipedrive equivalent because Pipedrive's standard plans do not include native invoicing. We map each Grow CRM Invoice to a Pipedrive Deal with custom fields: invoice number (custom_text), total amount (custom_number mapped from deal_value), invoice status (custom_picklist), and payment gateway reference (custom_text). Closed-paid invoices migrate as Won deals; open invoices migrate as Open deals. Grow CRM invoice attachments are exported as files and mapped manually to the corresponding Pipedrive Deal via filename reference in a custom field.

Grow CRM Payment records (amount, gateway, date, linked invoice) link to the migrated Deal representing the invoice. We create a Pipedrive Note attached to the Deal recording the payment amount, gateway (Stripe or PayPal), and date. Pipedrive's standard plans do not have a native payment tracking object, so the Note preserves the payment paper trail in the Deal's activity timeline. Any Grow CRM payment attachments migrate as files mapped manually to the corresponding Note.

Grow CRM Estimates (quotes or proposals with line items, totals, validity dates, and status) map to Pipedrive Deals. Each Estimate becomes a Deal with a custom field (estimate_number and estimate_status) distinguishing it from standard pipeline Deals. Validity dates migrate as custom date fields. Grow CRM's Estimate-to-Invoice conversion history is not migratable because Pipedrive does not have a native estimate-to-deal conversion link.

Grow CRM Help Desk Tickets have no direct Pipedrive equivalent. Ticket status, priority, assignee, and conversation history migrate as Pipedrive Notes attached to the relevant Person, Organization, or Deal. Conversation threads are exported as plain text and formatted as timestamped entries in the Note body. Ticket status and priority are stored as custom picklist fields on the Note. Pipedrive does not have native ticket management; teams requiring full help desk functionality plan a separate Service Cloud or Zendesk integration post-migration.

Grow CRM team member roles and access control are extracted as a user roster with assigned roles during scoping. Grow CRM role definitions are not structurally exportable and cannot be applied directly to Pipedrive, which uses a simpler user-role model (admin versus non-admin at the org level, with no granular per-object permission tiers on standard plans). We deliver a user-role mapping document to the customer's Pipedrive admin for manual provisioning post-migration. Grow CRM's team member records serve as the source-of-truth for the user list during reconciliation.