Migrate from Impact ERP to Odoo ERP

Impact ERP's hierarchical COA structure maps to Odoo's Account model under Accounting > Configuration > Chart of Accounts. We preserve account codes, descriptions, and group assignments (Asset, Liability, Equity, Revenue, Expense) with validation against Odoo's account type whitelist. Indonesian localization adds account tags for PPN input/output, withholding tax (PPh 23, PPh 26), and fiscal reporting categories. COA migration runs first because all journal entry lines reference account IDs as foreign keys.

Impact ERP customer masters map to Odoo Contact records with the Customer checkbox enabled. NPWP tax ID migrates to Odoo's fiscal country code and Tax ID field, with Indonesian localization creating a dedicated NPWP field. Billing address, shipping address, payment terms (net 30, net 60, etc.), and credit limits map to their Odoo counterparts. Custom fields on the customer master require pre-creation in Odoo before import.

Vendor masters mirror customer structure with the Vendor checkbox enabled. NPWP tax ID, bank account details for payment runs, and lead-time fields used in procurement map to Odoo's Contact vendor fields. Effective-dated changes on vendor records require sequential import: we extract each change event from Impact's history and insert Odoo Contact records with the most recent effective date values, flagging prior values in a custom history table if audit trail is required.

Impact ERP Item masters with SKU, description, unit of measure, cost, and inventory valuation method map to Odoo Product records. The inventory valuation method (standard cost, average cost, FIFO) maps to Odoo's costing method on the product form. We extract items from Impact's export, classify them as Odoo storable products (inventory-tracked), consumables, or services based on the source item type field. Unit of measure conversion tables are created where Impact and Odoo use different UoM conventions.

Manufacturing BOMs and routings attached to items in Impact ERP must be extracted separately from the item master export. Each BOM becomes an Odoo BoM record linked to the migrated Product. Routing steps become Odoo Work Centers with time efficiency and capacity records. BOM component quantities and operation times migrate as Odoo BoM line items and work order operations. Re-association at the destination requires the product ID to exist first, so BOM migration runs after the product import phase completes.

Open payables and receivables from Impact ERP carry invoice number, due date, amount, and currency. We migrate open items as Odoo draft Vendor Bills (AP side) and Customer Invoices (AR side) with the residual balance as the total amount. These are imported as draft records so the customer's accounting team validates and posts them against the new Odoo chart of accounts before finalization. Fully-paid historical records are flagged for optional carry-forward depending on whether the customer requires open period reporting.

Past invoices, purchase orders, receipts, and payment records from Impact ERP are stored in transaction tables with journal-entry links. We extract these in date-range chunks (typically fiscal year increments) and map to Odoo Account Move records (Accountant > Journal Entries). Header-level fields (date, reference, partner) map directly; line items require account ID resolution against the migrated COA. Odoo locks posted journal entries; only draft moves can be corrected after import.

Impact ERP GL journal entries map to Odoo Account Move records with header fields (date, reference, memo, department) mapped to their Odoo equivalents. Line items require field-level mapping: debit/credit amounts, account references, analytic account tags, and tax account assignments all resolve against the migrated chart of accounts. Department-level journal entries from Impact map to Odoo's analytic accounting (cost centers) if the customer uses that layer.

Impact ERP user accounts include role assignments and department assignments. We map these to Odoo User records with corresponding Access Rights groups (Settings > Users > Access Rights). Internal users get employee records linked to the User for timesheet and leave management if those Odoo apps are active. Passwords are not migratable; we provision new accounts at the destination and provide a role-to-group mapping spreadsheet for the customer's admin to assign credentials before go-live.

Impact ERP custom fields and user-defined objects have no standardized schema. We identify custom field definitions via exported metadata and pre-create equivalent Odoo custom models using the Settings > Technical > Models interface (or programmatically via XML data files). All custom fields, picklist values, and validation rules deploy to the destination before any data import begins. Lookup relationships between custom objects and standard objects (Contacts, Products) require careful order planning so that parent records exist at the time of child import.

Attached documents (PDFs, images, scanned files) stored in Impact ERP's document management module cannot be reliably extracted via standard export. We recommend a separate file-level migration: export the document repository to a network share or cloud storage bucket, then re-attach files to Odoo records manually or via Odoo's document management app post-go-live. This is out of standard migration scope.