Migrate from CRM.io by 500apps to Pipedrive

CRM.io Contact records (name, email, phone, company association) map directly to Pipedrive People. We export Contacts as CSV rows and map them 1:1, preserving email addresses as the dedupe key during import. Any company association in CRM.io resolves to the Organization record via a lookup table we build during the extraction phase.

CRM.io Lead records carry name, source, status, and owner fields. Pipedrive uses a unified People object for both contacts and leads depending on pipeline placement. We map Leads to Pipedrive Leads by default and let the customer's Pipedrive admin convert them during the sales process. Lead source and status values migrate to custom fields in Pipedrive to preserve reporting continuity.

CRM.io Account/Company records (business name, industry, size, address) map directly to Pipedrive Organization. We preserve Account-to-Contact associations via a lookup table built from the CRM.io export, then set the Organization ID on each Person record during Pipedrive import. Address fields map to Pipedrive's address subfields (street, city, state, postcode, country).

CRM.io Deals carry stage, value, close date, and owner. We map them 1:1 to Pipedrive Deals. Stage names transfer as custom label text or map to an existing Pipedrive pipeline stage, depending on what the customer has configured. The Account-to-Deal link is reconstructed using the compound key approach — we match Deal.account_id from the CSV export against the Organization ID we assigned during the Organization import phase.

CRM.io Activities link to Contacts or Deals but CSV exports may not preserve the parent object ID reliably. We reconstruct associations using date-matching and subject-matching as fallbacks when the direct ID is absent. Call and meeting logs migrate as Activity records with type, duration, and timestamp preserved. Email engagement history migrates as Activity records with subject and timestamp.

CRM.io exports Tags as comma-separated values in the CSV. We parse these, deduplicate, and load them into Pipedrive as Tag records with the activity_type and subject fields populated to match Pipedrive's tag association model.

CRM.io assigns record ownership to Users. We map Owner names to Pipedrive User emails via a lookup table provided by the customer during scoping. Any CRM.io Owner without a matching Pipedrive User is held in a reconciliation queue until the customer provisions the User in Pipedrive.

CRM.io supports pipeline stages for Deals with configurable stage names. Pipedrive pipelines have a defined stage sequence with probability values. We infer stage order from the CRM.io Deal records (the order in which stage values appear across deal rows) and create a corresponding Pipedrive pipeline with matching stage labels. Probability mapping is configurable during scoping based on the customer's stage definitions.

CRM.io Document Management stores file attachments with metadata (filename, type, associated record ID). The CSV export captures only metadata, not binary files. We handle document metadata as a structured reference and provide two options for the binary files: a bulk file transfer via secure shared storage for the customer to re-upload into Pipedrive, or a structured file-naming convention that maps each file to its target Person, Organization, or Deal record for manual re-attach.

CRM.io Email Templates are UI-resident content that does not export via standard CSV. We do not migrate Email Templates. Customers should manually export these from within the CRM.io UI if needed before the wind-down date. We document the full list of existing Email Templates during scoping and provide a rebuild inventory for the Pipedrive admin.