Migrate from Access ERP to Odoo ERP

Access ERP nominal ledgers with cost centre and department coding map to Odoo account.account with account.group defining the hierarchy. We preserve the nominal code as account.code and the description as name, and map cost centre and department dimensions to Odoo's analytic account model (account.analytic.account) which provides a secondary segmentation dimension not native to Access ERP. The customer configures the analytic plan in Odoo before migration runs.

Access ERP customer records map to Odoo res.partner with customer_rank set to indicate a customer role. Address books (street, city, state, country, zip) map to partner address fields; payment terms from Access map to Odoo property_payment_term_id; credit limits map to credit_limit on the partner. Multi-currency customers receive a property_account_position_id for tax mapping. The customer/commercial partner distinction in Odoo (is_company vs individual contacts) is resolved from the Access company flag.

Access ERP vendor records map to Odoo res.partner with supplier_rank set. Vendor payment terms, tax codes, and bank details migrate as supplier-specific fields on the partner record. Multi-currency vendor accounts receive a property_account_position_id for fiscal position mapping. The vendor's Accounts Payable nominal code from Access maps to property_account_payable_id on the Odoo partner.

Access ERP items map to Odoo product.product (stockable product variants) with product.template holding shared product attributes. Item code becomes default_code; item description becomes name. Warehouse-specific quantities from Access become stock.quant records per stock.location after location setup in Odoo. Reorder levels migrate to Odoo's stock.route rules and mrp_repairquotation.product_service_type constraints.

If the Access ERP database contains manufacturing data, BOM structures migrate to Odoo mrp.bom with bom_line entries referencing the migrated product.product records. Routing and work centre definitions from Access map to mrp.workcenter. We validate component availability and substitute part mappings before Odoo BOM import because mismatched component references are the most common BOM migration failure.

Open purchase orders migrate to Odoo purchase.order with vendor references (res.partner supplier_rank), order dates, and line items including product, quantity ordered and received, pricing, and taxes. Closed and received purchase orders migrate as historical records with state='done' for audit continuity. We preserve the purchase order number from Access as name for reconciliation against incoming goods receipts.

Open AR invoices migrate to Odoo account.move with type='out_invoice', carrying customer references (res.partner), invoice dates, due dates, and amounts from Access. Line items (product, quantity, unit price, tax) migrate as account.move.line records. Historical paid invoices migrate as account.move with type='out_invoice' and state='posted' with payment registration in account.payment for full audit trail. The Access posting date becomes the Odoo invoice date.

Open AP invoices migrate to Odoo account.move with type='in_invoice', carrying vendor references, invoice dates, due dates, and amounts. Historical paid invoices migrate with state='posted' and linked account.payment records. Bank statement lines from Access's reconciliation data map to Odoo account.bank.statement records so the customer can continue bank reconciliation from the cutover point.

Access ERP bank account masters and cash book balances migrate to Odoo account.journal (type='bank' for bank accounts, type='cash' for cash). We preserve the bank account currency and set the default_account on the journal to the corresponding payable/receivable nominal code. Outstanding unreconciled transactions become Odoo account.move.line entries in the bank journal for the customer to reconcile post go-live.

Access ERP stores document attachments at the transaction and master-record level. We export attachments in their native format and create ir.attachment records in Odoo linked to the corresponding model (purchase.order, account.move, res.partner, product.product) and res_id pointing to the migrated record's ID. Attachment filenames and create dates are preserved. Verification confirms all attachments link to valid records after migration completes.

Access ERP's highly configurable schema routinely contains custom fields and user-defined tables not present in standard exports. We run a discovery query against the live Access database to enumerate every user-defined field and non-standard table before building the extraction spec. Custom Access fields map to Odoo x_ prefix fields created via ir.model.fields with state='manual'. Access user-defined tables with complex relationships may require a custom Python migration script and are scoped separately during discovery.

Access ERP user accounts with role-based permissions and department assignments map to Odoo res.users. The Access access level and approval limits require manual configuration in Odoo's access control list (ACL) settings and multi-company rules post-migration. Inactive users from Access are created in Odoo as inactive records for historical activity attribution. We do not migrate user password hashes due to security; the customer's admin resets passwords at go-live.