Migrate from Access CRM to Pipedrive

Access CRM Contacts map directly to Pipedrive People. Name, email, phone, address, and owner assignment migrate 1:1. We extract the full contact field manifest during scoping and map each to a typed Pipedrive Person field. Any contact linked to an Access Pay & Bill worker record is flagged during the cross-module reference audit and either stripped or replaced with a text note in the Person record.

Access CRM Companies (sometimes called Accounts) map to Pipedrive Organizations. The parent-child hierarchy migrates as a flat organisation tree. We flag any circular reference or orphaned child company during extraction and resolve it before insert. The organisation name becomes the Organization name field, and domain or website data maps to the Organisation's Website field if populated in Access CRM.

Access CRM Opportunities carry Worst/Likely/Best monetary values and stage-based probability logic. We map the Likely value to Pipedrive Deal value; the Worst and Best values migrate to custom numeric fields deal_worst_value__c and deal_best_value__c on the Deal. Probability migrates as a custom field probability_override__c because Pipedrive computes stage probability from the stage definition; the custom field preserves the original Access CRM probability for forecast audit.

Access CRM pipeline stage names are tenant-defined free text with no standard vocabulary. We capture the full stage list during the scoping audit and produce a stage-mapping matrix before any records are touched. Each tenant-defined stage maps to a corresponding Pipedrive stage in the destination pipeline, with probability percentages carried forward from Access CRM or set by the customer during scoping. Unmapped stages default to an Archive pipeline unless the customer directs otherwise.

Access CRM Cases track problem lifecycles routed to customer-service, warehousing, or accounts teams. Pipedrive does not have a native Case object. We offer two routing options during scoping: cases that represent pre-sale service enquiries map to Pipedrive Leads, and cases that represent post-sale support map to a custom Deal pipeline named Support with a Deal field case_type__c set to support. The customer selects the routing strategy before migration.

Access CRM User records (name, email, role) migrate to Pipedrive Users. We resolve by email match. The customer provisions the Pipedrive Users before migration begins so that OwnerId references on Contacts, Companies, and Deals resolve at import time. Unresolved owners are held in a reconciliation queue and set to a designated placeholder User until the customer's admin provisions the correct account.

Access CRM call activities map to Pipedrive Call activities. Call duration, disposition, and timestamp migrate to typed Pipedrive activity fields. The activity is linked to the resolved Person record using the Pipedrive Activity API with the person_id reference. Call recording URLs from Access CRM migrate as text notes attached to the activity if the destination Pipedrive plan supports attachment.

Access CRM email activities map to Pipedrive Email activities. Subject, body, recipient address, and timestamp migrate directly. HTML bodies are preserved in the Pipedrive Email body field. The email activity is linked to the resolved Person and Organisation records. Outbound emails from Access CRM web-enquiry forms migrate as separate activity entries with a note indicating the original form source.

Access CRM notes associated with Contacts, Companies, or Opportunities migrate to Pipedrive Note activities. The note content and timestamp migrate verbatim. Notes are linked to the resolved Person or Organisation record using the Pipedrive Activity API. Note ordering is preserved by setting the activity timestamp to the original Access CRM created date.

Access CRM custom fields are tenant-specific and not self-documented in the admin UI. We extract the full field manifest via the admin knowledge base and cross-reference against the Access CRM data export. Each custom field maps to a typed Pipedrive custom field (text, number, date, dropdown, checkbox). Pipedrive's field creation requires the destination plan to support custom fields — we confirm the plan tier before the scoping session and advise on any upgrade required.

Access CRM web-enquiry forms capture leads directly and feed them as Opportunities or raw leads. Form field structures are configurable. We treat each form as a custom field set on the originating Deal or Lead record, mapping form field values to corresponding Pipedrive Deal fields or custom Deal fields. The original form name is preserved as a text note on the Deal for lead-source audit.

Attachments on Access CRM Contacts, Companies, and Opportunities migrate as file references pointing to the original upload location. We confirm that the destination Pipedrive plan supports file attachments on Person and Organisation records. Files that can be resolved as accessible URLs are re-linked as external file references in Pipedrive; inaccessible or proprietary-format files are flagged in the migration report with a download link for manual re-upload.