Migrate from SoulCRM to Pipedrive

SoulCRM Company records map directly to Pipedrive Organization. SoulCRM stores company-level fields including name, address, phone, website, and any custom fields capturing India-specific data like GST number or regional segment. We import Organizations first because every Contact must link to an Organization during migration. The Organization name field is the dedupe key; we validate for duplicates before inserting.

SoulCRM Contact records map to Pipedrive People. Each Contact's email address is the primary key used for deduplication. We resolve the Organization link (Org ID in SoulCRM) to a Pipedrive Organization ID during import so that the relationship is established at insert time rather than requiring a post-import linking step. Any SoulCRM custom fields on Contact migrate as custom fields on the Person record in Pipedrive.

SoulCRM Lead records from the Marketing Module map to Pipedrive Lead object. Lead status, source, and assignment fields migrate as custom fields or standard Pipedrive Lead fields. Pipedrive automatically creates a corresponding Person record when a Lead is imported with contact information, which means teams will see duplicate Person records if Leads and Contacts overlap. We flag this during scoping and recommend either excluding Leads with existing Contact records or a deduplication step post-migration.

SoulCRM Deal records map to Pipedrive Deal. The dealstage, amount, probability, owner, and expected close date fields migrate directly. SoulCRM pipeline stages map to Pipedrive pipeline stages; we configure the Pipedrive pipeline and stages before migration so that the stage mapping is explicit and Deal records insert into the correct pipeline at migration time. Closed-Lost and Closed-Won statuses transfer cleanly.

SoulCRM pipeline stages become Pipedrive pipeline stages. We create the pipeline in Pipedrive with matching stage names before Deal import so that the stage assignment on each Deal record is valid. Probability percentages map from SoulCRM to Pipedrive StageProbability. If SoulCRM uses multiple pipelines, each becomes a separate Pipedrive pipeline, and Deal records are routed to the correct pipeline during the transform step.

SoulCRM Activity records (email, call, task) map to Pipedrive Activity records of the corresponding type. Activity notes and timestamps migrate cleanly. Email body content from SoulCRM may use a different HTML format than Pipedrive's activity notes; we normalize the content to plain text or a safe subset of HTML to ensure readability. Call duration and disposition fields migrate to custom fields on the Call activity. We link each Activity to the correct Person or Deal using the relationship IDs resolved during the Person and Deal import phases.

SoulCRM Marketing Campaign records (name, type, start/end dates, budget) map to Pipedrive Campaign object. Campaign membership linking Contacts and Leads requires a separate association mapping table because the relationship between a Contact and a Campaign in SoulCRM is a distinct data point that must become a CampaignMember record in Pipedrive. We build this association table during the transform phase and insert it after both Campaign and Person records exist in the destination.

SoulCRM custom fields are supported across modules and include India-specific data like GST identifiers, regional segments, and industry classifications. We review every active custom field for data usage before migration. Fields with zero records are dropped. Fields with data migrate as Pipedrive custom fields on the corresponding object (Person, Organization, Deal, or Activity). Pipedrive's custom field type system (text, number, date, dropdown, checkbox, etc.) may require type conversion from SoulCRM's field types, which we document in the mapping workbook before import.

File attachments linked to SoulCRM Contacts, Companies, or Deals migrate as binary blobs via Pipedrive's attachment API. We extract attachments from the CSV exports or separate file storage, then re-upload to the corresponding Person, Organization, or Deal record in Pipedrive. Folder hierarchy in SoulCRM does not carry over; attachments land at the record level without the original folder structure.

SoulCRM Owner records map to Pipedrive User accounts. We resolve owners by email address match. The customer's Pipedrive administrator must provision User accounts in Pipedrive before migration begins; we cannot create Users programmatically. Any SoulCRM Owner without a matching Pipedrive User goes to a reconciliation queue, and the Deal or Contact records are held until the customer resolves the missing User.