Migrate from VBOUT to HighLevel

VBOUT Contacts migrate directly to GoHighLevel Contacts. Standard fields (first_name, last_name, email, phone) map 1:1. Custom fields on VBOUT Contacts map to GoHighLevel Contact custom fields by field type: text, number, and date map cleanly; dropdown fields map to GoHighLevel picklist custom fields; conditional and payment fields from VBOUT require pre-migration type mapping because GoHighLevel does not support conditional field types natively. We validate UTF-8 encoding and strip any line breaks or special characters before import.

VBOUT's Lead object (distinct from Contact in VBOUT's soft CRM model) migrates to GoHighLevel Contact. We carry the lead_score, lead_source, and assignment data into GoHighLevel Contact custom fields (vbout_lead_score__c, vbout_lead_source__c, vbout_assigned_to__c). Because GoHighLevel does not have a separate Lead object at this migration tier, all leads consolidate into the Contact model, preserving the scoring and attribution context for sales follow-up.

VBOUT Tags on Contacts and Leads carry pipeline stage context, segment classifications, and source attribution. Tags export as a flat list and are applied to matching GoHighLevel Contacts during import. Pipeline-stage-encoded tags (e.g., stage-qualified, stage-proposal-sent) are parsed and mapped to GoHighLevel Pipeline stages as a pre-import transformation step. The tag list is preserved in a Contact custom field (vbout_original_tags__c) for audit trail and segmentation rebuild in GoHighLevel.

VBOUT pipeline stages are stored as Tags rather than a native object. We extract all unique stage-encoding tag values, map them to GoHighLevel Pipeline stages, and configure the destination Pipeline with matching stage names and order before Contact import. Probability percentages from VBOUT carry into GoHighLevel stage probabilities. If VBOUT has multiple pipelines with different stage sets, we configure multiple GoHighLevel Pipelines with corresponding Record Types.

VBOUT custom fields on Contacts and Leads require field-type mapping before GoHighLevel import. Dropdown fields map to GoHighLevel picklist custom fields. Date fields must be formatted YYYY-MM-DD. Payment field metadata (amount, status, last_four) maps to GoHighLevel number and text custom fields. Conditional fields do not have a GoHighLevel equivalent; we flatten the last resolved value into a text field and document the conditional logic for manual rebuild if needed.

VBOUT sent campaign history (subject, send date, open rate, click rate, bounce count) migrates to GoHighLevel Campaign records. GoHighLevel Campaign records store campaign metadata and aggregate stats; email template bodies do not transfer. We export the raw campaign performance data so the customer can populate the campaign record metrics manually or connect to a reporting tool. Email templates from VBOUT are documented separately for manual rebuild in GoHighLevel's template builder.

VBOUT automation workflows use a proprietary JSON trigger-action schema with no documented export format that maps to GoHighLevel's workflow builder. We export each workflow definition as a structured JSON artifact and produce a step-by-step rebuild guide mapped to GoHighLevel's Workflow trigger-action editor, including trigger conditions, delay actions, condition branches, and CRM update steps. The customer rebuilds automations manually; we do not migrate workflow logic as executable code.

VBOUT landing pages are stored as page definitions with form field configurations and redirect rules. The visual page layout cannot be transferred. We export page metadata (title, URL slug, publish status), form field definitions (field names, types, required flags, conditional logic), and redirect rules. The customer rebuilds the page visually in GoHighLevel's Funnel builder; we deliver a field-by-field reconstruction guide and form schema for form rebuild.

VBOUT form definitions (standard, multi-step, conditional, payment variants) export cleanly including field configurations and conditional logic. Field names and types map to GoHighLevel form fields 1:1 for standard and multi-step forms. Conditional form logic does not transfer; we document the conditions and recommend rebuilding them using GoHighLevel's form logic builder. Payment form records carry transaction metadata (amount, status, last_four) into Contact custom fields rather than a native payment object.

VBOUT Calendar Booking records (appointment title, contact reference, time, status) migrate to GoHighLevel Appointments. However, GoHighLevel's appointment scheduler does not sync with external calendar systems for slot availability, matching VBOUT's known limitation. We flag this during scoping and advise customers to treat calendar booking as requiring manual reconfiguration post-migration. Appointment metadata migrates; the calendar integration is not portable.