Migrate from Variable Soft CRM to Zoho CRM

VSCRM Lead records map to Zoho CRM Leads. We extract the Lead object from VSCRM's export file, identify standard fields (name, email, phone, source, status, owner) by inspecting the export headers, and map them to Zoho's standard Lead fields. Any custom Lead fields discovered in the export are pre-created in Zoho during the schema setup phase before migration begins. Owner assignment resolves via email match against Zoho User records; any VSCRM owner without a matching Zoho User is placed in a reconciliation queue for the customer's admin to provision before Lead import resumes. VSCRM lifecycle stage labels that have no direct Zoho equivalent are stored in a custom field vs_crm_lifecycle_stage__c for admin review post-migration.

VSCRM Contact records map directly to Zoho CRM Contacts. Each Contact in VSCRM carries name, email, phone, company association, and lifecycle stage. We map the primary company link to Zoho's Account Lookup, preserving the parent-child relationship by ensuring that the Account record is committed before the Contact import phase begins. Any duplicate contacts identified during the export audit are flagged before import so the customer can decide on a deduplication strategy. Custom Contact fields from the VSCRM export are created as custom fields in Zoho during schema setup.

VSCRM Company records map to Zoho CRM Accounts. VSCRM uses Company as a container object for Contacts and Deals, which maps directly to Zoho's Account structure. We map company industry to Account Type, employee count to Number of Employees, and website to Website. The VSCRM company identifier is preserved in a custom field vs_crm_company_id__c for cross-reference during reconciliation. Accounts must be committed before Contacts because Zoho requires the AccountId lookup to be satisfied at the time of Contact insert.

VSCRM Deal records map to Zoho CRM Deals. Each Deal carries deal value, pipeline stage, owner assignment, expected close date, and associated contact link. We map VSCRM dealstage to Zoho Stage, preserving the original stage label as a custom field vs_crm_deal_stage__c. Owner assignment resolves by email match against Zoho Users, with unmapped owners held in a reconciliation queue. Expected close date maps to Closing Date. Pipeline stage labels from VSCRM that do not have direct Zoho equivalents are mapped to a custom picklist field vs_crm_pipeline_stage__c for admin review and reclassification post-migration.

VSCRM's multiple named pipelines with custom stages are recreated in Zoho's Deals module. Each VSCRM pipeline name becomes a Zoho pipeline configuration, and the custom stage sequence is built in Zoho with matching stage labels and probability percentages where available from the export. Stages with no associated deals in the export are included as empty stage containers. If a VSCRM pipeline uses a stage name that Zoho does not support natively, we map it to the closest Zoho stage and flag the mapping in the reconciliation report.

VSCRM activity records (calls, emails, tasks) linked to Contact and Deal records map to Zoho CRM Tasks and Events via the Zoho API. We preserve the activity type, timestamp, linked entity (Contact or Deal), and activity content. Activity history import runs after core records are committed to ensure that the parent record lookup succeeds. Calls map to Tasks with TaskSubtype=Call, meetings to Events, and tasks to Tasks with Status and Priority preserved. The original activity timestamp is set as ActivityDate to maintain timeline ordering in Zoho's history view.

VSCRM supports custom fields on Contacts, Companies, and Deals, but the field list is not available via public API or documentation. We discover custom field names and data types by inspecting the export file headers and sample values during the discovery phase. Each discovered custom field is pre-created in Zoho with the closest-matching Zoho field type (text to multi-line text, numeric values to number fields, date values to date fields, multi-option values to multi-select picklists) before any data import begins. Any fields where the type cannot be confidently inferred from the export are flagged in the mapping document for the customer to review and resolve.

VSCRM workflow automations are stored server-side with no export mechanism and cannot be migrated as code or configuration. We document every active automation discovered during the discovery call, capturing the trigger type, conditions, actions, and affected records, and deliver this as a written rebuild checklist. The checklist maps each VSCRM automation to a recommended Zoho Blueprint or Workflow Rule equivalent with the relevant module, stage, and action configuration noted. The customer's admin or a Zoho partner rebuilds the automations post-migration. No automation logic is carried forward in the data migration itself.

VSCRM notes attached to Contact, Company, and Deal records migrate as Zoho Notes linked via ContentDocumentLink to the parent record. We extract the note body and timestamp from the VSCRM export, create a Note record in Zoho, and attach it to the corresponding Contact, Account, or Deal by resolving the parent record ID at migration time. Note ordering in Zoho's timeline reflects the original VSCRM timestamp.

VSCRM owner references on Leads, Contacts, Deals, and Activities are resolved by email address against Zoho User records. We extract the distinct owner email list from the export file and attempt to match each email to an existing Zoho User. Any VSCRM owner without a matching Zoho User is logged to a reconciliation queue, and the customer's admin provisions the missing Zoho User before the migration resumes. Owner references on records are updated to the resolved Zoho User ID during import. Inactive VSCRM users are mapped to inactive Zoho Users if the customer wants to preserve the historical assignment record.