Migrate from Variable Soft CRM to Salesforce Sales Cloud

VSCRM Lead records map directly to Salesforce Lead. VSCRM does not publish a field schema externally, so we derive field names from the customer's exported dataset during discovery. The lead source, status, and owner assignment transfer to LeadSource, Status, and OwnerId respectively. Any VSCRM custom fields on Lead are mapped to Salesforce custom fields (CustomField__c) which we pre-create in the destination org before import.

VSCRM Contact records map to Salesforce Contact with AccountId resolved via Company lookup. VSCRM stores Contact-Company associations as a related-object link in the export; we extract the Company identifier and match it to the pre-created Account record using the Company name or domain as the dedupe key. Duplicate contacts flagged during VSCRM data profiling are held in a reconciliation queue for the customer's review before final import.

VSCRM Company records map to Salesforce Account. The Company name becomes Account Name, and the Company domain or website URL maps to Account Website for deduplication. VSCRM's Company object acts as a container for Contacts and Deals, so we create Account records before Contact import to satisfy the AccountId foreign-key constraint on Contact.

VSCRM Deals map to Salesforce Opportunity. The deal value (amount), stage, owner, expected close date, and pipeline assignment transfer to Amount, StageName, OwnerId, CloseDate, and the Record Type respectively. VSCRM pipeline stages are stored as label strings in the export; we map these to Salesforce StageName values under a Sales Process that corresponds to the source pipeline. If VSCRM stores a deal-contact association, we link the Opportunity to the Contact via OpportunityContactRole after both records are inserted.

Each named VSCRM pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Stage labels from VSCRM migrate to StageName picklist entries under the new Sales Process. Probability percentages map to StageProbability on each stage entry. We configure the Page Layout assignment per Record Type so stage values remain scoped to the correct line of business in the Opportunity UI.

VSCRM deal stages are label strings in the export without a published reference to their probability values. We derive the probability mapping from the customer's VSCRM pipeline configuration during discovery and create corresponding Opportunity Stages in Salesforce with matching probability percentages rounded to the nearest integer allowed by Salesforce.

VSCRM call activity records map to Salesforce Task with TaskSubtype set to Call. Call disposition, duration in seconds, and timestamp transfer to custom Task fields. ActivityDate is set to the original VSCRM activity timestamp to preserve timeline ordering. The WhoId on Task points to the migrated Contact or Lead; the WhatId points to the related Opportunity or Account.

VSCRM email activity records migrate as Salesforce EmailMessage (the email body and headers) linked to an Activity Task (the timeline entry). The WhoId on EmailMessage points to the migrated Contact or Lead; the WhatId points to the related Opportunity or Account. EmailMessage body and subject transfer from VSCRM's activity content field.

VSCRM meeting records map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendee information from VSCRM migrates as EventRelation records linking the Event to the relevant Contact, Lead, or User.

VSCRM task activities map to Salesforce Task with Status, Priority, Subject, and ActivityDate preserved. Owner assignment migrates by resolving VSCRM owner identifiers to Salesforce User IDs via the User mapping table built during owner reconciliation.

VSCRM custom fields are discovered from the customer's export file since no public schema document exists. We create matching Salesforce custom fields (CustomField__c) before data import, inferring data type from VSCRM export column content (text fields, numeric fields, date fields, picklist-like values). VSCRM custom fields with picklist-like values (e.g., stage names stored as strings) are created as picklist fields in Salesforce with the source values whitelisted.

VSCRM workflow automations are server-side with no export mechanism. We document every active automation rule during discovery—its trigger event, conditions, actions, and affected objects—and deliver a written rebuild checklist mapping each VSCRM rule to a Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds the automations post-migration. No automation logic migrates as code.

VSCRM owner identifiers map to Salesforce User records by email address match. We build an owner mapping table from the VSCRM export and resolve each owner against the destination Salesforce org's User table. Any VSCRM owner without a matching Salesforce User enters a reconciliation queue; the customer's admin provisions the missing User before record import proceeds.

VSCRM notes associated with Contacts, Companies, or Deals migrate to Salesforce Note records linked via ContentDocumentLink to the parent record. Note body transfers as rich text. If VSCRM stores note attachments as separate files, those migrate as ContentDocument records with a ContentDocumentLink to the parent.