Migrate from RSoft CRM to Pipedrive

RSoft Company records map directly to Pipedrive Organization. We extract company name, industry, size, address, and owner. Organization is created first so that the relationship to People records is satisfied at the moment of Contact insert. The Organization name is used as the dedupe key to prevent duplicate organizations during import.

RSoft Contact records map to Pipedrive Person. We extract name, phone, email, address, lifecycle stage, and owner. The Contact's linked RSoft Company maps to a Pipedrive Organization lookup. If the same person also appears as a RSoft Lead, we deduplicate during the People import by email match and merge into a single Person record.

RSoft Lead records map to Pipedrive Person. RSoft creates a separate Contact record when a Lead converts, so both may exist for the same individual. We deduplicate by email during migration: if a matching Person already exists from the Contact import, we merge fields (preserving the earlier creation date as a custom field) and skip the duplicate. Any RSoft-specific lead score and lead source are preserved as Pipedrive custom fields.

RSoft Deal records map to Pipedrive Deals. We extract deal title, pipeline stage, amount, probability, expected close date, owner, and linked Organization and Person. The RSoft pipeline and stage structure maps to Pipedrive's pipeline and stage configuration. Multiple RSoft pipelines map to multiple Pipedrive pipelines.

Each RSoft pipeline becomes a Pipedrive pipeline, and each RSoft stage within that pipeline becomes a Pipedrive stage with corresponding probability and stage order. We extract stage position, probability percentage, and any stage-specific automation labels from RSoft and configure Pipedrive stages to match before any Deal records import.

RSoft Activities map to Pipedrive Activities using the type field to distinguish calls, emails, meetings, notes, and SMS. We extract subject, body, date, duration for calls, and linked Person and Deal. Call disposition and duration from RSoft IVR exports migrate as custom fields on the corresponding Pipedrive Activity. Note content migrates to Pipedrive Activity with type note.

RSoft product catalog records map to Pipedrive Products with name, code, unit price, and currency. Products must exist in Pipedrive before they can be linked to Deals, so Product import runs before Deal import. If RSoft products have custom pricing per deal, those values are preserved as deal-level custom fields.

RSoft tags on Contacts, Leads, and Deals export as comma-separated values in the CSV and map to Pipedrive Labels on the corresponding Person, Deal, or Organization. We deduplicate tags during import and normalize casing. Labels in Pipedrive are scoped to the object they apply to (Person label vs Deal label).

RSoft user accounts referenced as owners on Deals, Contacts, Leads, and Tickets map to Pipedrive Users. We extract the full user roster and match by email address against the destination Pipedrive account. Any RSoft owner without a matching Pipedrive User is held in a reconciliation queue for the admin to provision before record import resumes.

RSoft custom fields on Contacts, Leads, Companies, and Deals map to Pipedrive custom fields where the destination plan tier supports them. RSoft Standard and Advanced plans cap custom fields at 5; Pipedrive Essential and Advanced also cap at 5. Fields exceeding the destination limit require either a plan upgrade (Pipedrive Professional or above) or manual reconstruction by the admin post-migration. We flag all exceeded-limit fields during scoping.

RSoft Ticket records with subject, status, priority, assignee, and conversation history migrate to Pipedrive as Activity records of type note with a ticket reference tag. Pipedrive does not have a native ticket object on Essential and Advanced plans; if the customer requires full ticket management, we recommend enabling Pipedrive's Power Pack or a helpdesk integration. We document the full ticket inventory for the admin to configure the replacement system.

RSoft does not expose document attachments via CSV export. Files linked to Contacts, Deals, or Tickets must be migrated separately via direct file transfer, not inline with record migration. We identify attachment URLs in the RSoft CSV where present, extract the files, and deliver them with a filename mapping to the destination record. The customer's admin uploads them into Pipedrive Files attached to the corresponding Person, Organization, or Deal.