Migrate from Elvis Business ERP to Odoo ERP

Elvis Customer records map to Odoo res.partner with partner_type set to 'contact' and customer_rank set to flag as a customer. Address fields (street, city, state, zip, country) migrate to partner address fields. Payment terms reference maps to Odoo property_payment_term_id. Any Elvis custom customer fields require field-level mapping to res.partner custom fields that we pre-create in the destination database before import.

Elvis Vendor records map to Odoo res.partner with supplier_rank set to flag as a vendor. Banking details and payment terms migrate to res.partner bank accounts (res.partner.bank) and property_supplier_payment_term_id. If Elvis vendors have a separate classification from customers, we use Odoo's commercial partner relationship to maintain a parent company record for each vendor entity.

Elvis Items with variants (size, color, unit) split into Odoo product.template (the base product) and product.product (the specific variant). Items without variants create only a product.template record. Elvis item type (stockable, consumable, service) maps to Odoo type field. Unit of measure from Elvis migrates to product.uom via Odoo's unit-of-measure framework. Vendor-specific item pricing from Elvis becomes Odoo supplierinfo records on the product.

Elvis Chart of Accounts migrates to Odoo account.account with account_type assigned per Odoo's classification (asset, liability, equity, income, expense). Account code structure from Elvis maps directly; account names migrate to name. Odoo requires each account to have a root account_type, so we validate each Elvis account's type before import. Any Elvis custom account segments (cost center, department) are held as account.common.report at migration scope unless Odoo Accountant or Advanced Accounting is licensed.

Elvis open Accounts Payable and Accounts Receivable migrate to Odoo account.move records in draft state with move_type set to 'out_invoice' (AR) or 'in_invoice' (AP). Open amounts, due dates, and reference numbers are preserved. Odoo reconciles these against bank statements post-migration during the cutover window. Partially paid invoices carry the paid_amount as a monetary field and remaining balance; Odoo's payment register tool applies partial payments during reconciliation.

Elvis historical invoices migrate to Odoo account.move records with move_type for the invoice type, line items mapped to account.move.line with matching account_id and analytic_distribution. Invoice status (paid, open, voided) is encoded in the move state and payment_state fields. PDF attachments associated with invoices in Elvis are exported as binary files and re-attached to the Odoo account.move records via ir.attachment. We track parent document associations during file export to ensure correct linkage at re-upload.

Elvis user records (name, email, role) map to Odoo res.users with login set to email. Elvis role names map to Odoo access groups (Employee, Manager, Billing, etc.) or custom access rights groups we create during setup. Active/inactive status from Elvis migrates to res.users active flag. If Elvis has role-based permissions not present in Odoo's standard groups, we document the mapping for the customer's Odoo admin to assign post-migration.

Elvis document attachments export as binary files with parent record metadata (Customer ID, Vendor ID, Invoice number). We re-associate each file with the correct Odoo res.partner or account.move record via ir.attachment with res_model and res_id pointing to the migrated record. File name and content type are preserved. Large binary attachments (>5 MB) are chunked during upload using Odoo's attachment import with res.model scoping to prevent timeout.

Elvis custom fields added to Customers, Vendors, Items, or Invoices migrate to Odoo as custom ir.model.fields on the respective model (res.partner, product.template, account.move). Field type mapping follows: text to char or text, numbers to float or monetary, dates to date, and picklists to selection fields. We pre-create the custom fields in the destination Odoo database before any data import begins. If Elvis stores custom fields on non-standard tables, we flag those during discovery and document them as out-of-scope or requiring a custom script.

If Elvis HR and CRM modules contain active records, we migrate employee contacts to hr.employee and any CRM leads or opportunities to crm.lead. Elvis HR data quality is verified against the Elvis data schema during discovery because HR and CRM use in Elvis may be partial depending on the customer's subscription tier. Odoo CRM requires the CRM app to be installed; we confirm app availability in the destination Odoo edition before scoping this mapping.