Migrate your inoERP data

inoERP stores the full chart of accounts with account types, balances, and currency assignments in the GL module. We export account codes, descriptions, types, and current balances. Roll-forward balances are mapped to the destination's fiscal year structure.

Journal entries in inoERP carry header-level and line-level data including debit/credit amounts, account assignments, and reference numbers. We preserve all posted entries but flag entries with non-standard currency or exchange rate data for manual review before import into the destination.

Open AR and AP subledgers include customer/supplier records, invoice headers, and line items. We extract open invoices by status and map inoERP's party structures to the destination's customer and vendor objects. Closed historical records require value mapping based on the destination's retention policy.

inoERP tracks items with UOM, cost layers, category hierarchies, and on-hand quantities across multiple inventory locations. We export item definitions, on-hand balances, and location assignments. Lot/serial number history is preserved where it exists in the source.

Open and closed orders in inoERP contain header fields (dates, terms, party references) and line items (item, quantity, price, warehouse). We export order status so that closed orders can be mapped to historical records while open orders are re-created as active documents in the destination.

Work orders in inoERP include routing steps, material issues, resource transactions, and completion records. The WIP ledger aggregates costs per work order. We extract the full work order history but note that post-completion cost updates in inoERP may need to be reconciled against the destination's costing module after import.

BOMs and routings define the product structure and manufacturing steps. inoERP supports super BOMs and multi-level structures. We export the full BOM hierarchy and routing sequence. Phantom BOMs and co-products are mapped to the destination's equivalent structures.

inoERP HR includes employee profiles, job definitions, positions, compensation records, leave balances, and approval hierarchies. We extract employee data and position assignments but flag compensation records that include effective-dated pay components requiring alignment with the destination's payroll effective-dating model.

inoERP uses role-based access control with users, roles, and permissions defined in the Admin module. We export user accounts and role assignments. Mappings must translate inoERP role names and permission sets to the destination's equivalent RBAC model.

inoERP supports document storage in its CMS module, but attachment links are stored as paths to locally hosted files. We do not migrate binary attachments. Customers should migrate file references separately and re-link documents in the destination system post-migration.

inoERP payroll generates electronic bank files for direct deposit. We export payroll registers, leave balances, and compensation history. Bank file formats are customisable via JavaScript REST APIs and may require destination-specific formatting before use in the new payroll system.

Asset registers in inoERP include acquisition details, depreciation schedules, and asset categories. We export the full asset record including book values and accumulated depreciation. Depreciation methods are mapped to the destination's equivalent schedule definitions.