Migrate from ERP Mark 7 to Odoo ERP

ERP Mark 7 Customer records map to Odoo res.partner with type=contact and customer_rank set for filtering. Address fields (street, city, state, zip, country) map to partner address fields. Payment terms and tax ID fields carry through as Odoo property_account_position_id and property_payment_term_id. We create the partner record before any Contact import so that Sales Order lookups are satisfied.

ERP Mark 7 Vendor records map to Odoo res.partner with supplier_rank set. 1099 settings and W-9 status fields from ERP Mark 7 migrate to Odoo custom fields or property references. Vendor-specific fields (tax ID, bank account details for ACH) map to Odoo's property_account_supplier_account_id and associated bank record objects.

ERP Mark 7 Items represent products, raw materials, and services with custom properties per item type (inventory vs non-inventory vs service). We map item type to Odoo product.type (product, consumable, service). Custom properties discovered during the schema audit become Odoo product.template attribute lines or product.custom_value fields. ERP Mark 7 item codes become Odoo default_code (SKU) for deduplication.

ERP Mark 7 Item BoM structures (component lists and quantities per finished good) map to Odoo mrp.bom records. BoM type (kit vs manufacturing) maps to Odoo type (phantom vs normal). We resolve the finished product and each component reference at migration time to satisfy Odoo's product.product foreign key on mrp.bom.line. Routing steps from ERP Mark 7 map to mrp.workcenter lines with workcenter_id, name, and cycle time fields.

ERP Mark 7 Work Orders link Items to BOMs and routing steps. We map work_order_id to Odoo mrp.production with product_id pointing to the finished product, product_qty carrying the run quantity, and state preserved as Odoo mrp.production state values (draft, confirmed, planned, in_production, done, cancel). Custom fields on work orders (e.g., machine center, priority flags) discovered during schema audit map to custom fields on mrp.production.

ERP Mark 7 Chart of Accounts entries map to Odoo account.account records. Account number and name carry through as code and name. ERP Mark 7 account type (asset, liability, equity, revenue, expense) maps to Odoo accountType. We flag any non-standard segment configurations (e.g., cost-center subaccounts) that require manual re-creation as Odoo account.group records. Active status is preserved; inactive accounts are imported as archived records.

Open receivables migrate as Odoo account.move records of type out_invoice in posted state, with payment_state mapped to the ERP Mark 7 payment status. Aging buckets (current, 30, 60, 90 days) are preserved as Odoo aging report fields or as custom fields if the destination uses a third-party aging module. We chunk by invoice date to avoid duplicate posting and resolve partner_id via the Customer mapping.

Open payables migrate as Odoo account.move records of type in_invoice in posted state. Vendor invoices carry through invoice number, date, due date, and amount. Payment method details (ACH routing, check number) map to account.payment fields. We separate pre-close from post-close invoices and do not import voided or disputed AP records.

Historical journal entries migrate to Odoo account.move records of type entry, posted to preserve audit trails. Pre-close transactions are imported as locked historical records; post-close transactions import with the current fiscal year open. We segment the import into fiscal-year batches and require the customer to confirm year-end close boundaries before migration begins. ERP Mark 7's close status becomes a custom field on account.move to prevent inadvertent re-opening in Odoo.

ERP Mark 7 Departments map to Odoo stock.warehouse (for location-based cost tracking) or account.analytic.account (for project/cost-center reporting) depending on whether the customer uses Odoo's manufacturing or financial cost-center module. ERP Mark 7's nested department hierarchies are flattened or preserved based on the Odoo edition's hierarchy depth capability. The customer chooses the mapping strategy during scoping.

Tax codes from ERP Mark 7 map to Odoo account.tax records with country-specific tax templates pre-populated from Odoo's built-in template library. Active tax codes migrate as active=Odoo taxes; deprecated jurisdiction-specific codes are flagged for manual review. Tax rate, tax scope (sale/purchase), and tax group assignment carry through from ERP Mark 7 field values.

Documents stored as attachments to transactions, items, or customers in ERP Mark 7 export as binary files and re-attach to the corresponding Odoo record via ir.attachment. Binary attachments are chunked during export to avoid size limits. We preserve the original filename and MIME type. Attachments without an identifiable parent record go to a general document storage location for manual classification.