Migrate from VBOUT to Zoho CRM

VBOUT Contacts with a lead score above the customer's defined qualification threshold map to Zoho CRM Contact; those below threshold map to Zoho CRM Lead. The VBOUT lead score value migrates into a custom field zv_lead_score__c on both Lead and Contact for post-migration segmentation. Email address is the dedupe key for both objects. We extract the VBOUT Tags list and apply relevant tags to the Zoho CRM record via the Tag API at insert time.

VBOUT's separate Lead object (distinct from Contacts in VBOUT's soft CRM) maps directly to Zoho CRM Lead. VBOUT lead score, source attribution, and assignment data transfer to zv_lead_score__c, Lead Source, and OwnerId on the Zoho Lead. We resolve VBOUT owner email against Zoho CRM User records during the import phase.

VBOUT Tags (on Contacts and Leads) map to Zoho CRM Tags via the Tags API. Tags encoding pipeline stage (extracted from VBOUT pipeline stage exports) are applied to Zoho CRM Deals as StageName and to Zoho CRM Contacts/Leads for segmentation. Tags used for lead qualification tiers migrate as Multi-Select Picklist values on the Lead and Contact layout if the customer prefers structured fields over tag labels.

VBOUT custom fields on Contacts and Leads require type mapping to Zoho CRM field types. VBOUT conditional fields and payment fields map to Zoho CRM Text Area or Multi-Select Picklist depending on the conditional logic structure. VBOUT dropdown fields map to Zoho CRM Picklist with the same options list. We pre-create custom fields in Zoho CRM before any record import, respecting the 300-field-per-module ceiling and flagging any field that would exceed that limit.

VBOUT Smart Audiences are dynamic segmented lists without a direct Zoho CRM equivalent. We export the Smart Audience membership as a static Contact list (CSV) and create a Zoho CRM Tag with the audience name. For ongoing dynamic segmentation post-migration, we document the Smart Audience criteria and recommend Zoho CRM's Advanced Filters or a Zoho Flow webhook that rebuilds the segment from the underlying field criteria. The customer chooses tag-based or manual list-based reconstruction during scoping.

VBOUT stores pipeline stages as Tags on Contact records. We extract the full set of distinct pipeline stage tags from the export, map each to a Zoho CRM Deal Stage Name (e.g., Qualified, Proposal Sent, Negotiation, Closed Won, Closed Lost), and create the corresponding stages in the Zoho CRM Deals layout. The original VBOUT stage tag name is preserved in a custom field zv_original_stage__c on the Deal for audit trail.

VBOUT Contact records may carry company name as a standard field. We extract the distinct company values from VBOUT Contacts, create Zoho CRM Account records for each distinct company name, and link the Contact (or Lead, post-split) to the Account via the Account Name lookup. Where VBOUT exposes a dedicated Company object, we map it directly to Zoho CRM Account with Website, Industry, and Phone fields preserved.

VBOUT sent email campaign history (subject, send date, open rate, click rate, bounce count) migrates as Zoho CRM Campaign records. Campaign Name maps from VBOUT campaign title, Campaign Start Date from send date, and Type set to Email. Open and click metrics are stored as custom fields on the Campaign since Zoho CRM Campaign does not natively track per-campaign engagement rates. Email template bodies do not migrate as reusable templates; we export them as structured HTML artifacts for manual template reconstruction in Zoho CRM or Zoho Campaigns.

VBOUT automation workflows export as JSON definitions from the API. These are not directly portable to Zoho Blueprint or Deluge scripting. We produce a structured JSON artifact of every active workflow (triggers, conditions, delays, actions) and a written rebuild guide mapping each VBOUT trigger-action pair to the equivalent Zoho Blueprint stage, Zoho Flow webhook, or Deluge function. The customer admin rebuilds automations in Zoho CRM post-migration; we do not write the Zoho automations as part of the migration scope.

VBOUT landing pages are stored as platform-specific page definitions with no portable export format. We export page metadata (title, URL slug, form field configurations, redirect rules) as a structured CSV and produce a rebuild guide referencing Zoho CRM's Web Forms, Zoho PageSense, or the customer's preferred landing page tool. The visual layout cannot be transferred and must be rebuilt manually.

VBOUT form definitions (standard, multi-step, conditional) export with field labels, field types, conditional logic, and webhook URLs. Standard and multi-step field definitions map to Zoho CRM Web Forms with the same field names and types. Conditional logic and payment form configurations are documented in a rebuild guide for Zoho Flow or Zoho Survey replacement, as Zoho CRM Web Forms does not natively support conditional branching or payment processing.

VBOUT analytics dashboards are rendered UI views with no export endpoint. We export the underlying raw data (email open rates, click maps, form submission counts, lead activity timestamps) as CSV so equivalent reports can be rebuilt in Zoho Analytics or manually in Zoho CRM Reports. The dashboard configurations themselves do not migrate. We flag this as a manual rebuild step in the handoff document.