Migrate from Vendasta to Odoo CRM

Vendasta Accounts represent SMB businesses managed by the partner. They map directly to Odoo CRM Partner records with address, phone, website, and industry fields preserved. We use the Vendasta Account ID as an external reference field on the Odoo Partner for dedupe and audit. Multi-location accounts (accounts with multiple service addresses in Vendasta) map to one Partner with multiple Odoo Contact addresses linked via partner_id relationship, not to separate Partner records, because Odoo's Contact model supports multiple addresses per Partner.

Vendasta Contacts tied to Accounts map to Odoo CRM Contacts linked to the corresponding Partner. The critical migration consideration is Vendasta's partner-to-SMB relationship model: Contacts in Vendasta are often SMB decision-makers (the partner's client contacts) rather than internal sales team members. We map them to Odoo Contacts with the partner_id pointing to the SMB Account Partner, preserving the Vendasta lifecycle-stage data in a custom contact field for reporting. Any Contact records without an associated Account are held in a staging table for the customer to resolve before import.

Vendasta Users who are internal partner staff (not SMB contacts) map to Odoo Users by email match. Vendasta User roles (Admin, Member, Sales rep) map to Odoo User groups (Access Rights: CRM / Sales / Inventory) and a custom vendor_role__c field for audit. Users without an active Odoo instance are held in a provisioning queue for the customer's admin to create Odoo accounts before Contact and Opportunity import proceeds.

Vendasta Orders (created when a partner activates a product or service for an SMB account) map to Odoo Sale Orders. The Vendasta order line items—each representing a marketplace product activation (listings, reputation, SEO, advertising)—become individual Sale Order Lines in Odoo with product_id references to Odoo Product records. We reconstruct the order total, taxes, discounts, and fulfillment status from the Vendasta order and map the Vendasta order state (pending, confirmed, fulfilled, cancelled) to Odoo sale_order state (draft, sale, done, cancel). Order date and shipping address map to Odoo Order date and partner_shipping_id respectively.

Each active marketplace product activation stored as a Vendasta Order line item splits into an Odoo Product record (Standard Price Book entry) and an Odoo Sale Order Line. Products include pricing tiers, activation requirements, and fulfillment state from Vendasta. We preserve the fulfillment status as a custom field on the Odoo Product or as a note on the Sale Order Line. Products without an existing Odoo catalog entry are created during migration staging; the customer chooses whether to map them to a generic Service product or to build out a full product catalog post-migration.

Vendasta Subscriptions represent recurring billing relationships tied to active product activations. They map to Odoo Subscription records if the customer licenses the Odoo Subscription application ($25/user/month add-on). We map subscription billing frequency (monthly, annual), recurring amount, start date, and renewal date to the corresponding Odoo Subscription fields. Subscriptions without the Odoo Subscription app license map instead to Odoo Sale Orders with recurring templates in the Sale app, and we document the manual Subscription app configuration required post-migration.

Vendasta Invoices generated from subscriptions or created manually map to Odoo Account Move records (type=out_invoice) in the Odoo Accounting app. Invoice line items, amounts, taxes, discounts, due dates, and payment status migrate directly. We map Vendasta invoice state (paid, open, cancelled) to Odoo move_state. Vendasta payment method references (credit card, ACH) map to Odoo journal_id assignments during migration. The Odoo Accounting app must be installed for this object to import; if not present, we create a structured invoice inventory document for the customer's accountant to enter post-migration.

Vendasta partner-scoped custom fields on Accounts map to custom fields on the Odoo CRM Partner model (res.partner) using Odoo Studio. We extract the full custom field manifest during discovery, validate field types (text, number, date, picklist, checkbox), and pre-create equivalent fields in Odoo before Account import. Enumerated picklist values from Vendasta custom fields require explicit value mapping to Odoo selection fields to avoid silent data loss. Custom fields that have no Odoo equivalent are documented in the migration field map with a manual-rebuild recommendation.

Vendasta custom fields on Orders map to custom fields on the Odoo Sale Order model (sale.order) or Sale Order Line model (sale.order.line) depending on whether the field applies to the order header or individual line items. We extract the Vendasta custom field manifest, validate field types, pre-create Odoo fields via Studio, and map picklist values explicitly. Fields scoped to the partner's billing configuration (e.g., internal cost margin fields) that have no Odoo equivalent are flagged as manual-rebuild items in the migration inventory.

Vendasta automation workflows triggered by email campaigns, product adoption stages, and upsell opportunities map to Odoo Action Rules configured via Odoo Studio in the CRM or Sale app. Workflow steps, conditions, and CRM actions are documented in a written automation inventory delivered alongside the migration. We do not migrate workflow definitions as code because the trigger-event and action model differ between Vendasta and Odoo. The customer's admin uses the inventory document to rebuild each workflow in Odoo Action Rules or to engage an Odoo partner developer.

Vendasta Snapshot Reports provide SMB clients with automated online presence assessments across listings, reviews, and social channels. These are report artifacts rather than transactional records and do not have a direct Odoo equivalent. We extract the most recent Snapshot Report per Account as a PDF attachment linked to the Odoo Partner record. The customer's admin rebuilds recurring report generation in Odoo using the Reporting app, scheduled Actions, or a third-party reporting integration.

Vendasta AI Employees are proprietary platform-native agents that automate marketing, sales, and operations tasks within Vendasta. There is no standard API schema or Odoo equivalent for AI Employees. Workflows that depend on AI Employees (automated lead qualification, content generation, client engagement) are documented in the automation inventory as requiring a manual rebuild strategy—either via Odoo AI integration partners, third-party AI agent platforms, or Odoo Studio-based process automation. No AI Employee data migrates into Odoo.

Vendasta engagement history (emails, calls, meetings, notes) tied to Contacts or Accounts maps to Odoo CRM Log Notes (chatter messages), Tasks, and Calendar Events in the CRM app. Email content and subject migrate as Odoo chatter messages on the corresponding Partner or Contact record. Calls migrate as Odoo Tasks with a custom call_disposition field. Meetings migrate as Odoo Calendar Events with attendee links to the relevant Partner or Contact. The original Vendasta timestamp is preserved on each record to maintain engagement chronology in Odoo's CRM timeline view.

Vendasta marketplace product definitions (listings, reputation management, SEO services, advertising tools that partners resell to SMBs) map to Odoo Product records with product_type=service. Each Vendasta product's pricing tier, activation requirement, and fulfillment state are captured in custom fields on the Odoo Product record or in product description notes. We extract all product definitions during discovery and create them in Odoo during schema staging so they are available as sale_order_line product_id references when Order import begins.