Migrate from Variable Soft CRM to Microsoft Dynamics 365 Sales

VSCRM Lead records map directly to Microsoft Dynamics 365 Lead. The VSCRM lead source, status, owner, and any custom fields discovered in the export become Dynamics 365 Lead standard fields and custom fields created in the target environment before import. We use the VSCRM export field headers to infer data types and map them to the correct Dynamics 365 field type (string, integer, date, picklist). If the VSCRM export omits fields that were created in VSCRM but never populated, we surface that gap before production import.

VSCRM Contact records map to Dynamics 365 Contact with name, phone, email, company association, and lifecycle stage preserved. The primary company link from VSCRM resolves to the Dynamics 365 Account created from the VSCRM Company object. Duplicate contacts flagged during a pre-import deduplication pass are merged before insert. Any VSCRM lifecycle stage property becomes a custom picklist field on Contact since Dynamics 365 does not have a native equivalent.

VSCRM Company records map to Dynamics 365 Account. The company name becomes Account Name; domain or website becomes the Website field; industry and address fields map to standard Account fields where present in the export. Account is imported before Contact to satisfy the parent Lookup relationship at insert time. If the VSCRM export includes related Contact IDs, we resolve them against the migrated Account records during the Contact import phase.

VSCRM Deal records map to Dynamics 365 Opportunity. Deal value maps to Amount, deal stage maps to StageName via a mapping table we build during discovery, owner maps to OwnerId via email-based User lookup, and expected close date maps to CloseDate. If the VSCRM export includes a pipeline name, we map it to a Microsoft Dynamics 365 Sales Process or Record Type created in the destination before import.

VSCRM pipelines and their custom stages are mapped to Dynamics 365 Record Types on Opportunity with corresponding Sales Processes that whitelist the stage values. Each VSCRM pipeline becomes a distinct Record Type so that stage values remain scoped per line of business. Stage probability percentages from VSCRM round to the nearest integer allowed by Dynamics 365. Empty stage containers from VSCRM are recreated as inactive stage values in Dynamics 365 for historical record accuracy.

VSCRM activity records (calls, emails, tasks, meetings) linked to Contact or Deal records map to Dynamics 365 Task (for calls and tasks) and Event (for meetings) objects. Call duration and disposition transfer to custom Task fields. The linked Contact or Deal reference resolves to the migrated Dynamics 365 record ID during import. Activity timestamps are preserved as ActivityDate on Task and StartDateTime/EndDateTime on Event. Activity content and body text migrate as the Description field; attachments migrate separately as file references or notes.

VSCRM custom fields on Contacts, Companies, and Deals are discovered from the customer export file headers. We create matching custom fields in Dynamics 365 via the maker portal or metadata API before the production migration, matching the inferred data type (text, number, date, picklist, lookup). Any lookup relationships between custom fields and VSCRM objects are translated to Dynamics 365 lookup or regarding relationships against the appropriate Account, Contact, or Opportunity record.

VSCRM owner references on Lead, Contact, Company, and Deal records map to Dynamics 365 User by email address match. We extract the distinct owner set from the export and reconcile against the destination User table. Any VSCRM owner without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before the Contact and Deal import phases proceed.