Migrate from MERCI to Odoo ERP

MERCI Customer records map to Odoo res.partner with partner_type set to 'contact' for billing entities. Address fields (street, city, state, zip, country) flatten into Odoo's standard address fields. Where MERCI uses custom customer classification codes, we map to res.partner.category_id (tags) or create custom Char fields on the partner model. Email, phone, and website map directly. Foreign-key references from orders and invoices resolve through partner_id during the Customer phase before dependent objects import.

MERCI Sales Orders map to Odoo sale.order. Order header fields (order number, date, customer reference, payment terms) map directly. Line items from MERCI map to sale.order.line with product_id resolved from the Items phase. Order status (draft, confirmed, shipped, invoiced) maps to Odoo state values. Order-to-invoice linkage preserves by storing the MERCI order number in a custom field on the corresponding Odoo account.move record.

MERCI Invoices map to Odoo account.move with move_type = 'out_invoice' for AR invoices and 'in_invoice' for AP. Payment terms, invoice dates, and due dates migrate. Open versus closed status maps to state (draft, posted, cancelled). Where MERCI invoices reference a source Sales Order, we embed the MERCI order ID in a custom field on the Odoo account.move for audit trail. Tax codes require verification against Odoo's tax structure.

MERCI Items (products and services) map to Odoo product.product. Item type (good, service, bundle) maps to Odoo's product.type field. Pricing tiers from MERCI map to Odoo product.pricelist.item records. Bundle and kit compositions in MERCI require expansion into Odoo's product.pack.line records or BoM structures depending on complexity. SKU from MERCI maps to product.default_code.

MERCI Account codes and names map directly to account.account.code and name. MERCI uses a simplified five-type taxonomy; Odoo uses the standard accounting type enumeration (receivable, payable, liquidity, etc.). We verify account type mapping during schema profiling and flag any MERCI accounts that require reclassification in Odoo before migration. Account codes must be alphanumeric per Odoo's account.account model.

MERCI Vendor records map to Odoo res.partner with partner_type set to 'contact' and supplier_rank = 1. Vendor contacts, payment terms, and bank account details map to the partner record. The same address-flattening logic used for Customers applies. Vendor-specific fields (such as W-9 status) map to custom fields on the partner record.

MERCI Employee records map to Odoo hr.employee. Department, job title, and employment status migrate directly. Compensation fields map to hr.contract or hr.employee fields depending on Odoo HR module configuration. Effective-dated compensation history flags as a reconciliation item for the customer's HR admin to validate against Odoo's payslip history if payroll is activated.

Order line items are processed as a child phase after the parent order is created in Odoo. Each line resolves product_id from the Items phase, maps quantity and unit price, and applies the correct tax IDs verified against the Odoo tax chart. Discounts from MERCI map to Odoo's discount field (percentage or amount depending on line configuration).

Invoice lines migrate after the parent account.move is created in Odoo. Line items map with product_id, quantity, price_unit, and tax IDs. Analytic account distribution from MERCI maps to Odoo's analytic_distribution field if the Analytic module is active in the destination Odoo instance.

Binary attachments stored in MERCI's blob store cannot be retrieved via any documented API endpoint or standard CSV export. We flag all Attachment records as unsupported migration scope. Customers must download files manually from the MERCI UI or request a full blob export directly from MERCI's account manager. If blob export is provided as a file share, we can ingest it into Odoo's ir.attachment records during a supplementary migration phase.

MERCI stores relationships in foreign-key columns rather than explicit join tables. During the profiling phase, we trace every foreign key (customer_id on orders, order_id on invoices, item_id on lines, vendor_id on purchases) and build a dependency graph that determines migration sequence. Parent records (Customers, Vendors, Items) must import before child records. Circular references or missing foreign keys are flagged in the reconciliation report.