Migrate from e-Emphasys ERP to Odoo ERP

e-Emphasys Customer records carry full contact details, billing addresses, and linkage to equipment and service history. Odoo uses a Contact model where individuals are Contacts linked to Companies (similar to Account). We map e-Emphasys customer_name and address fields to Odoo Contact fields, with the customer type (individual dealer vs corporate account) determining whether the record lands as a standalone Contact or a Company with child Contacts. Billing address and shipping address from e-Emphasys map to Odoo's partner address fields (type=billing and type=delivery). The customer's source system ID is preserved in a custom reference field for audit.

e-Emphasys serialized equipment records include OEM codes, VIN-equivalent identifiers, branch assignment, and current status (in-stock, sold, rental, demo). We map these to Odoo Product records with the product type set to storable, and we populate the lot/serial number field with the OEM equipment identifier. Branch assignments map to Odoo's operating unit or multi-company structure if the destination is configured for multi-location. Equipment status from e-Emphasys becomes a custom product attribute field in Odoo because Odoo's base product model does not natively carry dealer-specific equipment lifecycle status.

Non-serialized parts in e-Emphasys include bin locations, vendor links, cost tiers, and price tiers. We map e-Emphasys part_number to Product product_tmpl_attribute_line or product_variant fields, map vendor link to Odoo's vendor pricelist on the product, and preserve cost and price tiers as multiple vendor price lines. Stock levels and reorder points map to Odoo's quant quantity and reordering rules. The mapping handles multi-branch parts by creating separate Odoo warehouse records per branch with quants scoped to the relevant warehouse.

Serialized parts in e-Emphasys track bin locations, warranty claim associations, OEM cost tiers, and equipment linkage. We map the serialized part number to Odoo's lot/serial tracking on the Product quant record, and we preserve the equipment linkage as a custom many2one field linking the serialized part quant to the destination Product record representing the parent equipment. Because Odoo's standard serial number model does not natively associate a serialized part with a parent serialized equipment record, we generate a reconciliation report listing every serialized part and its linked equipment for manual verification after import.

e-Emphasys service work orders tie to equipment records, technicians, labor rates, line items, and warranty claim associations. We split work order data across Odoo's project management and timesheet modules: the work order header maps to a Project (or Task within a Project), the labor line maps to Timesheet entries linked to the assigned technician as an Odoo Employee, and parts consumed on the work order map to Odoo stock moves. Warranty claim associations from e-Emphasys become a custom field on the Odoo project/task record for follow-up.

e-Emphasys rental contracts include equipment assignments, daily/weekly/monthly billing tier structures, and early return conditions. Odoo does not have a native dealer-specific rental contract object with multi-tier billing. We map active rental contracts to Odoo sale orders using the sale_subscription app if Odoo Enterprise is licensed, or to sale order lines with recurring invoice configuration if Community is used. Rate schedules that exceed Odoo's billing configuration (e.g., tiered daily/weekly/monthly in a single contract) are flagged in a contract reconciliation report for manual verification before go-live.

e-Emphasys whole goods sales orders and quotes link to customer and equipment records with pricing tiers and OEM incentive associations. We map these to Odoo Sale Orders, with the customer field resolved to the mapped Contact or Company, and the equipment line resolved to the mapped Product record. OEM incentive amounts from e-Emphasys migrate as order line discounts or as custom fields on the sale order depending on the customer's reporting needs. The order status from e-Emphasys (quote, confirmed, invoiced, closed) maps to Odoo's sale order state.

e-Emphasys GL accounts, journal entries, and account balances export from the financial module with chart of accounts structure and period associations preserved. We map e-Emphasys account numbers to Odoo account.account codes, journal entries map to account.move records (posted or draft depending on the source status), and account balances are validated against Odoo's trial balance after import. Branch-level GL assignments in e-Emphasys map to Odoo's analytic account structure if multi-branch reporting is required.

Vendor invoices and payment records in e-Emphasys export with full vendor linkage and PO-to-invoice associations where they exist. We map vendor invoices to Odoo account.move records with move_type=in_invoice, and payment records map to account.move records with move_type=in_payment linked to the original bill. Vendor records are resolved by matching vendor name to Odoo partner records created during the Customer/Company phase. Open AP balances are validated against Odoo's vendor aging report after import.

Customer invoices, payments, and AR aging data in e-Emphasys export with customer linkage and payment history preserved. We map invoices to Odoo account.move records with move_type=out_invoice, and payment records map to account.move records with move_type=out_payment. Open invoice balances and AR aging data are validated against Odoo's customer aging report. The original invoice reference from e-Emphasys is preserved in Odoo's invoice reference field for traceability.

Employee records in e-Emphasys include labor rates, certifications, and branch assignments. We map these to Odoo Employee records, with labor rate tiers preserved as salary structure fields (if HR Payroll is active) or as custom fields on the employee record for service billing. Branch assignments from e-Emphasys map to Odoo's department or operating unit structure. Technician certifications (e.g., OEM-specific repair certifications) become custom fields on the Odoo employee record because Odoo's standard HR module does not carry equipment-specific certification data.

e-Emphasys warranty records tie to serialized equipment and OEM claims with coverage periods and claim history. Odoo does not have a native warranty management module. We map warranty coverage periods to custom date fields on the Product or Project record linked to the equipment, and we preserve claim history as activity notes attached to the relevant record. OEM warranty codes are preserved as custom fields for integration with OEM portals if the customer continues using manufacturer warranty systems post-migration.