Migrate from Variable Soft CRM to HighLevel

VSCRM Lead records (with source, status, owner, and lifecycle stage properties) map to GoHighLevel Contacts. The lead status field in VSCRM maps to GoHighLevel's Contact status or a custom field depending on the export's available columns. We use email address as the primary dedupe key during import. If the VSCRM export includes both Lead and Contact objects, we merge any records sharing an email address into a single GoHighLevel Contact and flag duplicates in the reconciliation report.

VSCRM Contact records map directly to GoHighLevel Contacts. The full name, phone, email, company association, and lifecycle stage properties migrate to GoHighLevel's standard Contact fields. We resolve the VSCRM company association to a GoHighLevel Location or Contact field based on GoHighLevel's single-Contact data model. Any lifecycle stage values that do not map to GoHighLevel's native status options are stored as a custom text field for reporting.

VSCRM Company records map to the Company field on GoHighLevel Contacts rather than a separate object, since GoHighLevel does not use a distinct Account object at the same level as Salesforce. We import Companies first, then use the company name as a matching key when importing Contacts to link each Contact to its parent company. If GoHighLevel Locations (Agency tier feature) are in scope, we map VSCRM Companies to Locations for richer address and contact grouping.

VSCRM Deals map to GoHighLevel Opportunities. The deal value, stage name, owner, expected close date, and pipeline assignment migrate to GoHighLevel's Opportunity fields. Stage names from VSCRM are recreated as Pipeline stages in GoHighLevel before import so that the stage values are valid on ingest. We preserve deal-contact associations through the email-address matching done during the Contact import phase.

VSCRM named pipelines with custom stage sequences are recreated as GoHighLevel Pipelines. We capture the full stage list from the export file (including empty stages with no associated deals) and configure the matching GoHighLevel Pipeline structure before any Opportunity data is loaded. Stage order and stage probability percentages migrate as part of the Pipeline configuration step.

VSCRM Activity records linked to Contacts and Deals migrate to GoHighLevel Activities and Tasks. Activity type (call, email, meeting, task), timestamp, and linked entity migrate. The linked entity resolves through the email-address matching established during Contact import. We import Activities after Contacts and Opportunities are loaded so that the contact and opportunity lookups are satisfied. Activity content and body text are imported where present in the export file.

VSCRM custom fields on Contacts, Companies, and Deals are discovered from the export file header row since no public schema document exists. We map each VSCRM custom field to either a GoHighLevel native Contact custom field (for single-value fields) or a GoHighLevel Custom Object (for relational or multi-value fields). GoHighLevel's Custom Objects support CSV import with field mapping, and we provision the destination schema before import begins. Any VSCRM custom fields that cannot be typed from the export data are flagged for manual confirmation before provisioning.

VSCRM workflow automations are not exportable as portable logic and do not migrate. We run a discovery interview to document every active automation rule (trigger event, conditions, actions, and assigned owner) and deliver a written rebuild checklist with GoHighLevel Workflow equivalents for each rule. The customer's admin reconstructs the automations in GoHighLevel's Workflow builder post-migration.