Migrate from CRUMP CRM to Pipedrive

Contacts in CRUMP CRM export from the Dynamics 365 Contacts entity and map directly to Pipedrive Persons. Standard fields (full name, email address, phone number, postal address) transfer 1:1. We resolve the parent Account reference to a Pipedrive Organization during import so that each Person is linked to the correct Organization record at insert time.

CRUMP CRM Accounts map to Pipedrive Organizations. The Dynamics 365 account name becomes the Organization name, and website, industry, phone, and address fields map directly. Parent-child account hierarchies from Dynamics 365 are preserved by setting a parent Organization lookup where the destination data model allows. Org deduplication uses domain name from the Website field as the matching key.

Dynamics 365 Opportunities in CRUMP CRM map to Pipedrive Deals. The deal name, value (amount), expected close date, and stage map 1:1. Pipeline stage names from Dynamics 365 are mapped to Pipedrive pipeline stages during the configuration phase, and the stage probability percentages are entered as Pipedrive StageProbability values. The Account reference on the Deal resolves to the Organization ID established during the Organization import phase.

Each Dynamics 365 Opportunity stage becomes a Pipedrive Pipeline stage. We configure the Pipedrive pipeline before migration using stage names from the source org's Opportunity Sales Stage picklist values. Stage order and probability percentages transfer from Dynamics 365 and are set on the Pipedrive pipeline configuration. If the source org uses multiple Microsoft Dynamics 365 Sales processes, each becomes a separate Pipedrive pipeline.

CRUMP CRM Tickets (Dynamics 365 Cases) do not have a native Pipedrive equivalent. We export ticket records with status, priority, subject, description, and linked Contact. In Pipedrive, we create a custom object (Case) with fields mapped from the source, or we attach tickets as Activity notes on the related Organization or Person. The customer selects the strategy during scoping. Custom fields on tickets are enumerated and mapped individually because Dynamics 365 allows per-org custom ticket fields.

CRUMP CRM Project Management module records (not to be confused with Dynamics 365 Project Service Automation) export with project name, status, dates, and assigned team members. Pipedrive has no native Project object. We create a Pipedrive custom object (Project) with a schema matching the source fields, or we convert projects to Deals with a custom Project checkbox and label field. Task-level detail within projects is assessed during scoping; deep task migrations require a separate scope and are documented separately.

CRUMP CRM Invoices export with invoice number, line items, totals, payment status, and the originating Deal or Project reference. Pipedrive does not have an invoicing module. We export invoice data as a custom object (Invoice) in Pipedrive linked to the related Organization or Deal, or we attach invoice records as Notes with a custom label. The relationship to the originating Deal is reconstructed from the Dynamics 365 export using the originatingobjectid field if present.

Dynamics 365 Users export with name, email, security role, and business unit assignment. We match by email against Pipedrive User accounts. Inactive users in the source org are archived in Pipedrive rather than imported as active to avoid ghost records. Users without a matching Pipedrive account go to a reconciliation queue for the customer's admin to provision before record import resumes.

Tasks exist across CRM, project, and helpdesk modules in CRUMP CRM. We deduplicate by Dynamics 365 activity ID, label each by origin module (CRM Task, Project Task, Helpdesk Task), and import into Pipedrive Activities with a custom Type field capturing the source module. Status, Priority, Due Date, and Owner map directly. Tasks without an assigned Contact or Account are imported as standalone Activities.

Dynamics 365 Notes attached to Contacts, Accounts, or Deals migrate as Pipedrive Notes linked to the Person, Organization, or Deal via the note's object reference. Rich text formatting in Dynamics 365 Notes is preserved as HTML in Pipedrive Notes where the destination field supports it. Notes attached to inactive or deleted source records are held in a review queue.

Dynamics 365 email activities attached to Contact, Account, or Deal records migrate as Pipedrive Activities with type Email. Subject, body, sender, recipients, and timestamp transfer. The parent object reference is resolved to the corresponding Pipedrive Person, Organization, or Deal at migration time. Email attachments are handled as a separate file export pass.

Any custom entities created on top of Dynamics 365 in the CRUMP CRM instance are enumerated during the audit phase. Each custom entity and its fields are documented individually, and the schema is pre-created in Pipedrive as a custom object before data import. Custom entity relationships to standard entities (Account, Contact, Opportunity) are preserved as lookup fields where Pipedrive supports them. No two Dynamics 365 deployments share the same custom entity landscape, making this the most variable portion of the migration scope.