Migrate from Standard ERP to Odoo ERP

Standard ERP's structured GL chart with parent-child hierarchy, account type (Asset, Liability, Equity, Revenue, Expense), currency assignments, and cost-center tags maps to Odoo's Account object within the Accounting app. We extract the full account hierarchy, normalize account codes to Odoo's character constraints (alphanumeric, no special characters), and preserve cost-center assignments as Odoo analytic accounts or dimension tags depending on the Odoo version. Account type mapping is validated against Odoo's allowed account types per country localization.

Standard ERP customer records including billing/shipping addresses, payment terms, contact associations, and customer-specific pricing tiers map to Odoo res.partner records with the customer flag set. Multiple shipping addresses per customer become separate res.partner records linked via parent_id. Payment terms migrate to Odoo property_payment_term_id, and customer-specific pricing tiers migrate as custom fields or product pricelist rules depending on Odoo version.

Standard ERP vendor master records including bank details, 1099 flags, and purchase terms map to Odoo res.partner with the supplier flag. Bank account information migrates to res.partner.bank records. Vendor address formats are validated against Odoo's country-specific address formatting rules during import. 1099 flags migrate to Odoo l10n_us fields if the destination is configured for US localization.

Standard ERP items with inventory, non-inventory, and service variants map to Odoo product.template with product.product variants. BOM linkages from Standard ERP migrate to Odoo's mrp.bom structures. Item type (inventory vs. non-inventory vs. service) maps to Odoo's type field (product, consumable, service). Variant attributes and values from Standard ERP become Odoo attribute lines on product.template.

Non-inventory items in Standard ERP map to Odoo product.template with type set to service or consumable depending on whether the item represents a labor or expense line. These items do not carry stock moves in Odoo.

Service items from Standard ERP map to Odoo product.template with type = service. Service-specific fields (time-tracking, recurring billing) are configured post-migration based on the customer's service delivery model.

Outstanding vendor invoices, credit memos, and payments from Standard ERP AP module migrate as Odoo account.move records of type in_invoice and in_refund. Aging detail is preserved in Odoo by setting the invoice date and payment term, which drives the due date in Odoo's accounting view. We match each open AP document to its corresponding GL account entry to ensure accounts.payable balance reconciles post-migration.

Outstanding customer invoices, credit memos, and payments from Standard ERP AR module migrate as Odoo account.move records of type out_invoice and out_refund. Aging is preserved via payment term and due date. Each open AR document is matched to its corresponding accounts.receivable account entry during import to ensure the customer balance and GL reconcile at cutover.

Standard ERP job costing links labor, materials, and overhead to specific projects. We map these to Odoo project records linked to analytic accounts for cost tracking. Phase-level breakdowns migrate as project tasks with custom fields carrying the original Standard ERP phase codes. If the customer uses Odoo Manufacturing, job costing phases may alternatively map to mrp.workorder records with time-tracking.

BOM-linked production orders from Standard ERP transfer as Odoo mrp.production records with BOM reference, scheduled date, and work-center assignments. Actual vs. estimated costs migrate to Odoo as move records and workorder entries. Routing detail from Standard ERP (work-center sequence, operation times) maps to mrp.routing.workcenter in Odoo Manufacturing. Post-migration configuration may be needed for Odoo routing settings that differ from Standard ERP defaults.

Standard ERP document vault attachments require separate extraction via HAL script or direct database query because the vault uses a proprietary format. We export vault packages as file packages and associate them with migrated records using a filename-to-record-ID mapping table built during discovery. Large attachment volumes (over 50,000 files) require staged transfer with Odoo's ir.attachment records linked to the appropriate res.partner, account.move, or product.product records.

Standard ERP user accounts, roles, and permission sets migrate as Odoo res.users records. We map Standard ERP user IDs to Odoo user logins by email match. Permissions that lack a direct Odoo equivalent are flagged in the inventory document for admin review. Active vs. inactive status migrates directly from Standard ERP.