Migrate your VBOUT data

Contacts are the primary records in VBOUT. Standard fields (name, email, phone) and unlimited custom fields are supported. We perform a full field-level export and map every custom property to the destination schema during migration.

Smart Audiences are dynamic segmented lists based on behavioral and demographic criteria. The segmentation rules do not export directly; we replicate the audience logic in the destination platform's equivalent segment builder.

Leads are distinct from Contacts in VBOUT's soft CRM. We preserve the lead score, source attribution, and assignment data on each Lead record during migration.

Contacts and Leads carry Tags for classification. Tags export as a flat list and are re-applied to matching records in the destination, preserving any pipeline stage or segment context encoded in the tagging scheme.

Custom fields on Contacts and Leads are fully supported for migration but require field-type mapping because VBOUT uses dropdown, conditional, and payment field types that do not always map 1:1 to destination field types.

Automation workflows (multi-step trigger-action sequences) export as JSON definitions. VBOUT's workflow structure is not directly portable to other platforms; we document the trigger conditions, delay durations, and action chain so the workflow can be rebuilt in the destination.

Sent campaign history (subject, send date, open/click data) can be exported as CSV or via API. Template bodies are available for export but must be manually re-built in the destination's template editor.

Landing pages are stored as VBOUT-specific page definitions. We export page metadata, form field configurations, and redirect rules. The visual page layout cannot be transferred; it must be rebuilt in the destination builder.

Forms include standard, multi-step, conditional, and payment form variants. Field definitions and conditional logic export cleanly; payment form records export with transaction metadata but payment integration credentials do not transfer.

Pipeline stages export with stage name, order, and assignment rules. We map each stage to the destination pipeline schema, using Tags as a fallback for platforms without a native pipeline object.

Scheduled and published social media posts can be exported as content records with timestamps and platform targets. Media assets download separately; post metadata migrates as a content log.

VBOUT's analytics dashboards are UI-native visualizations. They cannot be exported as data. We export underlying data sources (email stats, form submissions, lead activity) so equivalent reports can be built in the destination platform.