Migrate from EBMS to Odoo ERP

EBMS Customers are documents in the Customers table with name, address, payment terms, and contact details. We export via the Customer Address for Mail Merge report or equivalent and map to Odoo Partner records. B2C customers map to Odoo res.partner with type=contact; B2B customers with multiple contacts at the same organization map to a parent res.partner (company) with child contact records attached. EBMS Customer Portal accounts with assigned price levels and payment terms migrate to Odoo res.partner with a corresponding Pricelist assignment and payment term ID on the partner record.

EBMS Products are defined in the inventory module with pricing, stock levels, units of measure, and serial numbers. We export via inventory reports and map to Odoo product.template records. Products with multiple attribute values (size, color, material) from EBMS custom fields require Odoo product variant generation. EBMS serial number tracking maps to Odoo lot/serial number records on stock.move. Units of measure migrate to Odoo uom.uom records with the relevant category.

EBMS Sales Orders (synced from eCommerce or created manually) export as order headers and line items via order reports. The EBMS order header carries customer reference, order date, payment terms, and pricing as calculated in EBMS. We map to Odoo sale.order and sale.order.line records. Pricing calculations that EBMS computed at order creation replicate in Odoo through the Pricelist rules attached to the customer record. Any custom fields on EBMS order headers require explicit mapping to Odoo sale.order custom fields created via Studio before import.

EBMS Purchase Orders export from the purchasing module via PO reports. Line items carry vendor part numbers, quantities, and unit costs. We map to Odoo purchase.order and purchase.order.line. Custom fields on PO headers or lines require explicit mapping to Odoo purchase.order fields. EBMS vendor-specific pricing that determines landed cost requires mapping to Odoo vendor Pricelists on the product template.

EBMS Invoices linked to customers and sales orders export via AR aging and invoice reports. We map to Odoo account.move records with move_type=out_invoice. Open invoices (not yet paid) and historical paid invoices both migrate. Payment history requires date-range scoping: we flag any invoices with payment activity spanning the cutover date and coordinate with the customer on whether to close the AR period in EBMS before migration or handle mid-period payments as a reconciliation step. EBMS payment terms map to Odoo account.payment.term records.

EBMS vendor invoices export via AP reports. We map to Odoo account.move records with move_type=in_invoice. Date-range scoping applies similarly to AP: any vendor bills paid across the cutover date require coordinated handling. Vendor-specific tax codes from EBMS map to Odoo account.tax records, which must be configured in Odoo with the correct tax type and accounts before AP import begins.

EBMS Vendor records include contact information and purchasing terms. We export via vendor reports and map to Odoo res.partner with supplier_rank > 0 to classify them as vendors. Custom fields on vendor records migrate to custom fields on the partner record. Purchasing terms map to account.payment.term records linked to the vendor partner.

EBMS eCommerce product data (pricing, availability, photos, attribute values) exports from inventory reports. We map to Odoo product.template with product images via the Odoo product.image relation. EBMS price levels per customer segment migrate to Odoo product.pricelist records with corresponding rules on the product template. The annual sales volume cap that applied in EBMS has no direct Odoo equivalent; we confirm during scoping whether the customer's pricing model was constrained by EBMS tier limits and map to the appropriate Odoo Pricelist without artificial volume restrictions.

EBMS B2B portal accounts carry assigned price levels, payment terms, and customer-specific product visibility. We export portal account data and map to Odoo res.partner records with the appropriate pricelist_id and payment_term_id assignments, and create portal user accounts in Odoo for the customer's customers via Odoo's portal invitation mechanism. Price-level visibility that EBMS enforced via portal tiers migrates to Odoo Pricelist rules scoped to the specific customer or customer group.

EBMS custom fields added via the Customization Designer to any entity (Customer, Product, Order, Vendor, Invoice) require discovery before mapping. We request read-only SQL access during data profiling to enumerate all custom field columns in the EBMS database, including developer-created fields whose definitions cannot be edited in the UI. We then create matching custom fields in Odoo via Studio (or via XML data migration for fields that Studio cannot create) before exporting EBMS data. Any EBMS custom field that maps to a picklist or multi-select in EBMS requires Odoo selection or many2many field configuration with equivalent values.