Migrate from Verenia to Odoo CRM

Verenia Contact records (name, email, phone, company association) map to Odoo res.partner with is_company=False. We use email as the primary dedupe key during import. The verenia_owner_id field maps to Odoo create_uid and write_uid, with a custom field verenia_owner_ref__id preserved for cross-reference. Custom contact properties from Verenia migrate as custom res.partner fields created during schema setup.

Verenia Company records map to Odoo res.partner with is_company=True. A corresponding contact res.partner record is created for the primary contact associated with each company, with parent_id pointing to the company partner. Company-to-contact relationships are preserved through the parent_id hierarchy in Odoo. Industry and address fields map to standard Odoo res.partner fields.

Verenia Quotes map to Odoo crm.lead records with type='opportunity' and stage_id set to the proposal/quotation stage. Quote line items (product, quantity, unit price, discount) migrate to crm.lead.line_ids if using the CRM native line model, or to a custom quotation_lines model we create in Odoo. Quote status (draft, sent, accepted, lost) maps to crm.lead stage and probability. The original Verenia Quote number is stored in a custom field verenia_quote_ref__c for audit and cross-reference.

Verenia Orders map to Odoo sale.order records. Order status (pending, confirmed, fulfilled, cancelled) maps to sale.order state. The customer partner is resolved via the res.partner email dedupe key computed during the Contact/Company migration phase. Order line items map to sale.order.line records with product_id, product_uom_qty, price_unit, and discount preserved.

Verenia Product Configurations encode guided-selling rules, bundle structures, and compatibility constraints that do not have a 1:1 mapping in Odoo. We decompose each configuration into its constituent product variants (one Odoo product.product record per variant combination) and capture the rule logic as structured metadata stored in an ir_attachment linked to a custom verenia_config_rule__c model. The customer receives a configuration rule inventory document enumerating each rule, its trigger conditions, its constraints, and the recommended Odoo CPQ module or manual rebuild approach. This is a documentation-and-rebuild handoff, not an automated rule migration.

Verenia Product catalog items map to Odoo product.product records. Product name, SKU (mapped to default_code), list_price, standard_price, and product type (service vs. stockable) migrate directly. Bundle products from Verenia map to Odoo product.product with a type=kits configuration using Odoo's bom_line structure if the customer licenses the Manufacturing app, or as a product template with a descriptive bundle_components field if Manufacturing is not in scope.

Verenia export archives containing Quote PDFs, Order confirmation documents, and configuration screenshots are extracted, normalized (file naming conflicts resolved by prefixing with verenia_quote_id or verenia_order_id), and loaded into Odoo ir_attachment linked to the corresponding crm.lead or sale.order record via res_model and res_id. File types (PDF, PNG, JPEG) are preserved. Attachments without a resolvable parent record are loaded to a general verenia_attachments container for manual classification.

Verenia User records are mapped to Odoo res.users by email match. Owner assignment on Quotes, Orders, and Contacts is remapped to the corresponding Odoo user. Any Verenia user without a matching Odoo user (because the customer has not yet provisioned all Odoo licenses) is logged to a reconciliation queue, and migration of dependent records is held until the customer provisions the missing users. Inactive Verenia users map to Odoo res.users with active=False.

Each line item on a Verenia Quote maps to a corresponding sale.order.line record on the linked sale.order. Product reference resolves via SKU (default_code) lookup in the product.product table. Quantity, unit price, discount percentage, and tax are preserved. Bundle line items from Verenia map to individual sale.order.line records with a custom bundle_parent_line_id linking them to the parent bundle line.

Order line items from Verenia migrate to Odoo sale.order.line records in the same manner as Quote line items, using SKU-based product resolution and preserving pricing, quantity, and tax data. Line item sequence (display order on the original Verenia order) is preserved via the sequence field on sale.order.line.

Verenia pricing tiers (volume-based discounts, customer-specific pricing) are extracted as a structured pricing rule inventory and mapped to Odoo product.pricelist records with price computation rules (min_quantity, fixed_price, or percentage discount). We create one pricelist per Verenia pricing tier and assign it to the relevant customer res.partner records. The customer must validate pricing tier applicability in Odoo because Verenia's guided-pricing logic (conditional discounts based on product combinations) may require manual configuration of Odoo pricelist rules or a CPQ add-on.

Verenia bundle structures (configurable products with required or optional sub-components) are mapped to Odoo product.product variants linked via product.template attributes. If the customer licenses Odoo Manufacturing (mrp module), we use mrp.bom records to model the bill of materials for each bundle. If Manufacturing is not in scope, bundle structures are preserved as product.template attribute configurations with a custom bundle_structure__c JSON field documenting the component hierarchy. This is a schema mapping that enables manual guided-selling rebuild in Odoo.