Migrate from etEngine to Odoo ERP

etEngine account codes and names map to Odoo's account.account records with account_type (asset, liability, equity, income, expense) set per Odoo's mandatory taxonomy. Currency assignments map to res.currency if etEngine uses multi-currency; otherwise company_currency_id defaults to the configured company currency. We pre-create the fiscal year and required journals in Odoo before any journal entries import, because Odoo enforces journal-account linkage at the point of posting.

etEngine Customer records map to Odoo res.partner with customer_rank set to distinguish primary customers. Contact details (name, email, phone, address) migrate directly. Payment terms from etEngine map to account.payment.term. We set address data using Odoo's composite address fields (street, city, state, zip, country_id via country lookup). The res.partner record is created before any related invoices import so that partner_id references are satisfied at insert time.

etEngine Vendor records map to Odoo res.partner with supplier_rank set. Contact details, payment terms, and bank information migrate as-is. Purchase history from etEngine (if applicable) maps to purchase.order records after the vendor res.partner is created. We flag any etEngine vendor records missing a contact email or phone for customer admin review before final import.

etEngine Item masters map to Odoo product.template with product_type (consumable, service, storable) set per etEngine item type. SKU, description, list_price, and standard_price migrate to product.template fields. If etEngine uses item variants (size, color), we map to product.template with product.attribute and product.template.attribute.line creating the variant structure. Category assignments map to product.category for inventory categorization.

etEngine open AP records map to Odoo account.move records with move_type=in_invoice; open AR records map to move_type=out_invoice. Original invoice dates and amounts are preserved. The reconciled flag from etEngine determines whether the record imports as an open invoice or a posted journal entry. We flag any etEngine records marked as reconciled for customer admin review because carrying fully reconciled items into a new system can create duplicate postings. Credit memos map to account.move with move_type=out_refund or in_refund.

Past journal entries and transaction history are exported from etEngine in fiscal period order and loaded into Odoo account.move records with move_type=entry. We sequence by posting date to maintain chronological audit trail integrity. Each journal entry's account lines are validated against the Odoo Chart of Accounts before import. Multi-currency amounts map to Odoo's currency and amount_currency fields. Any etEngine journal entries with missing or ambiguous account references go to a reconciliation queue for customer admin resolution before those entries are posted.

etEngine user accounts map to Odoo res.users by email match. Active/inactive status is preserved. Odoo access rights and groups (security.group) are mapped from etEngine role names during scoping, with the customer admin confirming group assignments before migration. Any etEngine user without a matching email in Odoo goes to a reconciliation queue for admin provisioning before record migration continues because OwnerId references on account.move and res.partner require a valid res.users record.

etEngine attached files and linked documents are exported to a structured file store with original filenames and record associations preserved in a lookup table. We then link each file to the corresponding Odoo record (account.move for financial documents, res.partner for contact documents) via ir.attachment with res_model and res_id set. The customer admin configures the Odoo document repository settings (ir_attachment.location) during setup.

etEngine custom fields on any mapped object are enumerated during discovery and mapped to Odoo Studio custom fields of the equivalent type (char, float, integer, boolean, selection, many2one). Relational custom fields (many2one, many2many, one2many) require pre-creating the destination related model and are imported after the related records exist. Unsupported etEngine field types (such as computed or formula fields) are documented in the migration inventory for customer admin resolution; we do not recreate computed fields as Odoo computed fields because source business logic does not transfer.

etEngine payment terms on Customer and Vendor records map to Odoo account.payment.term with line definitions (number of days, end of month, etc.). Fixed-amount and percentage-based payment term lines migrate directly. The customer admin confirms payment term assignments during scoping because Odoo applies payment terms at the sales or purchase order level rather than at the contact level.

etEngine tax codes and rates map to Odoo account.tax records with amount_type (group, fixed, percent), amount, and tax_scope (sale, purchase, none). Tax account assignments are validated against the Odoo Chart of Accounts. Tax groups (where applicable) map to account.tax.group. We flag any etEngine tax records that reference deprecated or inactive accounts for admin review before import.