Migrate from VBOUT to Odoo CRM

VBOUT Contacts with CRM type = Customer map to Odoo res.partner with partner_type = contact. Standard fields (name, email, phone, address) migrate directly. We apply a deduplication check on email before insert using Odoo's dedupe_criteria = email. Unlimited contacts on VBOUT translate directly; Odoo has no per-contact pricing cap, removing a migration blocker that VBOUT customers on Free and Starter tiers frequently encounter.

VBOUT Contacts with no purchase history, no closed deal, or CRM type = Lead map to Odoo crm.lead as Prospects. We apply a routing rule during scoping based on the customer's VBOUT CRM type field and lead score threshold. Lead score from VBOUT (hs_lead_score or equivalent custom field) migrates to a custom integer field on crm.lead. The original lifecycle stage or lead source from VBOUT is preserved in a custom Char field for audit and reporting continuity.

VBOUT Companies map to Odoo res.partner with is_company = True and partner_type = contact. VBOUT's company domain, industry, and annual revenue map to Odoo partner fields website, industry_id, and annual_revenue. Companies are loaded before Contacts so that the parent_id reference is resolved at the moment of Contact insert, satisfying Odoo's commercial partner requirement.

VBOUT Leads (distinct from Contacts in VBOUT's soft CRM model) map directly to Odoo crm.lead. Lead score, source attribution (utm_source, utm_medium), and assignment data migrate to crm.lead fields priority, source_id, and user_id. Any tag assignments on VBOUT Leads are transferred as Odoo tag records linked to the crm.lead.

VBOUT Tags migrate to Odoo crm.tag records. Tags serve multiple roles in VBOUT: pipeline stage encoding, segment classification, and lead source marking. We preserve all tag values and reapply them during the Contact-to-partner and Contact-to-lead migration. Tag-to-Lead routing logic is documented as a written rule set for the customer to implement in Odoo's lead routing or automated actions if needed.

VBOUT pipeline stages stored as Tags on Contacts map to Odoo crm.stage records. We create one stage set per VBOUT pipeline and configure stage sequence order, name, and fold status in Odoo. Stage probability percentages from VBOUT are set on the corresponding Odoo stage record. Odoo's Kanban view automatically renders the migrated stages with the original order and grouping.

VBOUT Smart Audiences are dynamic segmented lists with behavioral and demographic filter rules. Odoo has no native Smart Audience equivalent. We export the segmentation rule logic as a structured JSON artifact, including filter conditions, time-based criteria, and audience count at migration time. The customer uses this to recreate audiences manually as Odoo tags (for static segments) or saved ir.filters (for dynamic searches). This is a written handoff, not an automated migration.

VBOUT custom fields on Contacts and Leads require Odoo Studio field creation before import. Dropdown-type custom fields in VBOUT map to Odoo selection fields with equivalent option lists. Conditional and payment field types in VBOUT have no direct Odoo equivalent and are flagged during scoping for either custom field type selection or post-migration manual entry. We pre-create all destination fields in the Odoo test database during the sandbox phase before any data loads.

VBOUT email campaign history (campaign name, subject, send date, open/click metrics) migrates as tagged crm.lead records with a custom Char field crm_lead_campaign__c storing the original campaign name. Send volume statistics are stored as custom Float fields for reporting. The actual email template body cannot be transferred from VBOUT's editor; we export campaign metadata as a CSV artifact and the customer rebuilds templates in Odoo's email composer if needed.

VBOUT automation workflows are stored in a proprietary JSON schema tied to its trigger-action builder. This schema is not portable to Odoo Actions. We export the full workflow definition (triggers, conditions, delays, actions, branch logic) as a structured JSON file and produce a step-by-step written rebuild guide mapped to Odoo Studio Actions. The customer or an Odoo partner rebuilds each workflow post-migration.

VBOUT landing pages are stored as VBOUT-specific page definitions with drag-and-drop layouts that cannot transfer to Odoo Website. We export page metadata (URL slug, form field configurations, redirect rules, traffic source tags) as a structured document. The customer rebuilds landing pages in Odoo Website using the exported field list and redirect configuration as a specification.

VBOUT form definitions (field names, types, conditional logic, and submission rules) export cleanly as structured data. Standard and multi-step form field definitions migrate to Odoo as documentation artifacts for rebuilding in Odoo Website or CRM form views. Payment form submissions migrate as tagged lead records with transaction metadata; payment processing requires reconfiguration with an Odoo-compatible payment provider (Stripe, PayPal, or Odoo's payment acquirer).

VBOUT engagement history (calls, emails, meetings, tasks) is preserved as Odoo mail.message records or crm.lead note entries, depending on the engagement type and Odoo configuration. We tag the parent crm.lead with the campaign name, date, and engagement type, and store open/click data as custom fields. This preserves the activity timeline at the record level but does not produce native Odoo call or meeting records with attendee linking.

VBOUT dashboards are UI-native visualizations that cannot be exported or transferred. We export the underlying raw data sources (email open rates, form submission counts, lead activity counts, campaign performance) as CSV files so the customer can rebuild equivalent reports in Odoo Pivot and Graph views. The dashboard layout and chart configurations require manual rebuild in Odoo.