Migrate from Vonigo to Odoo CRM

Vonigo clients combine contact details, company information, and billing properties in one record. Odoo uses res.partner with company_type set to 'company' for business clients and 'person' for individuals. Franchise-specific client properties migrate as custom char or selection fields on the partner record.

When a Vonigo client has multiple named contacts such as a dispatcher, billing contact, and site manager, each contact becomes a separate res.partner record with parent_id pointing to the company partner, preserving the relationship hierarchy that Vonigo stores implicitly within the client record.

Vonigo work orders contain job details, line items, assigned technician, status, and signature. Odoo sale.order stores the commercial relationship; line items map to sale.order.line with product_id, quantity, and price_unit. Odoo Enterprise Field Service adds task-level tracking if structured work-order steps are needed.

Vonigo work order states (Scheduled, In Progress, Completed, Invoiced, Cancelled) map to Odoo sale.order states (draft, sent, sale, done, cancel). Status transition timestamps from Vonigo are preserved in custom datetime fields on the order for reporting continuity and historical tracking.

Vonigo's multi-location franchise model uses brand-level controls and territory assignment. Odoo handles this via res.company subsidiaries or project-based segmentation with team_id scoping. FlitStack creates the company hierarchy in Odoo and maps Vonigo territory fields to custom fields or project assignment rules.

Vonigo estimates map directly to Odoo sale.order in draft state. Line items migrate as sale.order.line records with pricing from Vonigo's estimate totals. If the estimate was converted to a work order in Vonigo, the Odoo order is marked as confirmed (sale state) and linked to the corresponding work-order order.

Vonigo invoices migrate to account.move with move_type='out_invoice'. Original Vonigo invoice numbers are stored in the Odoo invoice's ref field for traceability. Payment state is computed from linked account.payment records. Credit notes map to move_type='out_refund' for proper accounting treatment.

Vonigo payment records map to account.payment linked to the corresponding account.move via reconcile. Payment method (credit card, ACH, check) is stored in Odoo's payment_method_line_id or as a custom field if the method codes differ from Odoo's standard set of payment method types.

Vonigo staff records are matched to Odoo res.users by email for precise user resolution. Vonigo role-based permissions (Dispatcher, Technician, Admin) map to Odoo security groups: base.group_user for general staff, project.group_project_user for technicians, and base.group_erp_manager for admin access. Unmatched users are flagged before migration for manual resolution.

Vonigo service categories map to Odoo product.category for catalog organization. Products themselves migrate to product.product with service=True for non-stocked service items, with the category_id linking to the mapped category for proper product classification.

Vonigo franchise-specific client properties (e.g., program_fee_enabled, territory_code, preferred_payment_method) require custom fields on res.partner in Odoo. FlitStack identifies all Vonigo custom fields during the discovery phase and creates the corresponding x_ prefixed fields before migration loads the data.

Vonigo stores customer signatures, job photos, and checklist attachments on work orders. These are downloaded from Vonigo's file storage and re-uploaded to Odoo as ir.attachment records linked to the corresponding sale.order via res_model and res_id. Original upload timestamps are preserved in the attachment's create_date.