Migrate from Variable Soft CRM to Pipedrive

VSCRM Leads map to Pipedrive People records using the contact's email as the dedupe key. VSCRM's lead source, lead status, and owner assignment transfer to Pipedrive People custom fields since Pipedrive's native People model does not have a separate lead flag. We preserve the original VSCRM lead status in a custom field vs_crm_lead_status__c for segmentation. Any VSCRM Lead without an email address is flagged during validation and held for manual review because Pipedrive requires an email for People creation.

VSCRM Contacts map to Pipedrive People records with the same email-dedupe logic. The primary difference from Lead migration is that VSCRM Contacts may have a company association that maps to the Pipedrive Organization lookup. We process VSCRM Leads and Contacts in a combined People import, using a vs_crm_record_type__c custom field to distinguish the origin (Lead vs Contact) for reporting purposes. Duplicate email addresses across VSCRM Leads and Contacts are resolved in favor of the Contact record, with the Lead data preserved in a note attached to the People record.

VSCRM Company records map directly to Pipedrive Organizations. The company name becomes the Organization name, and the company domain becomes the Website field. Organization is created before any People import so that the Organization lookup is satisfied at the moment of People insert. VSCRM Company custom fields transfer to Pipedrive Organization custom fields.

VSCRM Deals map to Pipedrive Deals with value, stage, owner, expected close date, and linked company preserved. The VSCRM deal stage name maps to the corresponding Pipedrive Stage within the target Pipeline. Deal-contact associations transfer as Deal-People links in Pipedrive. Closed-won and closed-lost dates and reasons from VSCRM custom fields migrate to Pipedrive Deal custom fields.

VSCRM's named pipelines with custom stages map to Pipedrive Pipelines and Stages. We recreate each VSCRM pipeline as a Pipedrive Pipeline, and each VSCRM stage as a Pipedrive Stage within that Pipeline, preserving the stage order and probability percentages where present. Stages with no associated deals are included as empty containers. Stage colors do not migrate and default to Pipedrive's standard palette unless specified during configuration.

VSCRM Activity records (calls, emails, meetings, tasks) associated with Contacts or Deals map to Pipedrive Activities linked to the corresponding People or Deal. Activity type, timestamp, subject, and outcome transfer to Pipedrive's activity fields. Activity content and notes require a separate extraction pass and migrate as notes attached to the parent People or Deal record. We flag any VSCRM activity records with missing parent references during validation and exclude them from migration pending manual review.

VSCRM Owner records map to Pipedrive Users by email address match. We resolve VSCRM owner_id on every record (Contact, Company, Deal, Activity) to a Pipedrive User. Any VSCRM Owner without a matching Pipedrive User email is held in a reconciliation queue for the customer's admin to provision the User before record import resumes. Inactive VSCRM owners are mapped to inactive Pipedrive Users so that historical assignment is preserved.

VSCRM custom fields on Contacts, Companies, and Deals map to Pipedrive custom fields on People, Organizations, and Deals respectively. VSCRM field names are discovered from the customer's export file since no public schema document exists. We create the Pipedrive custom fields in the target account before migration, matching VSCRM data types (text to text, numeric to numeric, date to date, picklist to single-select or multi-select). Custom field visibility is set to the relevant entity (People, Organization, or Deal) during field creation. Pipedrive's rule that leads share deal custom fields applies; VSCRM Lead-specific custom fields map to People custom fields in Pipedrive.

VSCRM tags stored on Contacts or Companies migrate to Pipedrive custom fields configured as multi-select picklists on People or Organization. If VSCRM tags function as entity classifiers for non-contact data (products, categories, locations), we evaluate whether Pipedrive's Organization object can serve as the tag container or whether the tag names should be stored in a People or Organization custom field. The customer chooses the tag strategy during scoping based on reporting needs.

VSCRM custom objects have no direct Pipedrive equivalent because Pipedrive does not support custom objects beyond its standard People, Organizations, Deals, and Activities entities. We evaluate each VSCRM custom object during scoping to determine whether it can be stored as a custom field set on an existing Pipedrive entity (for example, a Vehicle custom object storing make, model, and year maps to Deal custom fields on the associated Deal record) or whether the data should be stored as a separate Organization record with the custom object name as the Organization name and the fields as Organization custom fields. This is a configuration decision made during discovery with the customer's data model input.