Migrate from inoERP to Dolibarr ERP

inoERP's GL chart of accounts with account codes, types, descriptions, and currency assignments maps directly to Dolibarr's accounting module. The account type hierarchy (Asset, Liability, Equity, Revenue, Expense) maps to Dolibarr's account classification. We export account codes, descriptions, types, and current balances. Roll-forward balances require a year-end adjustment entry in Dolibarr's accounting module rather than a direct balance import.

inoERP journal entries include header data (entry date, reference, description) and line-level data (account, debit, credit, cost center). We export all posted entries and flag entries with non-standard dimensions (like multi-company segments) that have no Dolibarr equivalent. Dolibarr's journal model supports basic entries but does not natively support inter-company journals or cost center consolidation; entries with these dimensions require manual post-processing in Dolibarr or a custom extension.

inoERP separates AR and AP as distinct subledgers with party records, invoice headers, and line items. Dolibarr consolidates customers and suppliers into a single Third Parties module with a Type field (Customer, Supplier, or both). We map inoERP's customer records to Dolibarr Third Parties with Type=Customer, and supplier records to Type=Supplier. Open AR/AP invoices migrate as Dolibarr Customer Proposals (quotes) converted to invoices, or as direct invoice records. Invoice status (open, paid, overdue) carries forward as Dolibarr status values.

inoERP item definitions with UOM, cost layers, category hierarchies, and on-hand quantities map to Dolibarr Products with stock management enabled. Multi-location on-hand quantities map to Dolibarr's multi-warehouse stock tracking. Lot and serial number traceability requires the Lot/Serial module extension in Dolibarr. We export item definitions, on-hand balances, and location assignments, and flag items with complex cost layer structures that may need simplification in Dolibarr's single cost price model.

inoERP Sales Orders with header fields (dates, terms, party references) and line items (item, quantity, price, warehouse) map to Dolibarr Customer Orders. We export open orders by status and map inoERP order status to Dolibarr order status. Closed sales orders are mapped to Dolibarr Customer Order records with a Closed status for historical reference, or excluded from migration per the customer's date-range preference during scoping. Shipping address and payment terms carry forward as line-item and header attributes.

inoERP Purchase Orders map to Dolibarr Supplier Orders using the same header and line structure as Sales Orders. We map inoERP's supplier references, lead times, and receipt status to Dolibarr fields. Closed purchase orders follow the same date-range migration logic as sales orders. Multi-unit purchase orders (orders placed in a different UOM than stock) require UOM conversion mapping at migration time.

inoERP work orders include routing steps, material issues, resource transactions, and completion records, with a WIP ledger aggregating costs per work order. Dolibarr's production module (available as a module extension) supports basic production orders but does not include a WIP ledger, multi-level routing steps, or resource capacity planning. We export full work order history as Dolibarr Production Order records with bill of materials linkage. The WIP cost aggregation is flagged as a custom field (wip_total_cost__c) on the Production Order for reference rather than a native accounting ledger entry. Historical MRP-generated planning records are flagged as Plan-Generated and should be re-run in Dolibarr post-migration rather than imported verbatim because inoERP's dynamic pull-based MRP recalculates lot sizes at runtime against historical demand conditions.

inoERP BOMs with multi-level structures, super BOMs, and phantom assemblies map to Dolibarr BOM definitions. Routing sequences map to Dolibarr BOM line order. We export the full BOM hierarchy and flag phantom BOMs and costed BOMs that require the production module's cost calculation extension in Dolibarr. Phantom sub-assemblies in inoERP map to Dolibarr BOM lines with the phantom flag where supported. Multi-level BOM flattening is available as a pre-migration step if Dolibarr's single-level BOM model creates display issues.

inoERP HR includes employee profiles, job definitions, positions, leave balances, and approval hierarchies. Dolibarr's HR module (requires activation) supports employee records with contact details, job title, and contract type but has limited support for compensation history and complex approval chains. We export employee data and position assignments. Compensation history (salary records, bonuses) is flagged as a custom field set requiring manual entry in Dolibarr or a custom HR extension. Leave balances export as Dolibarr HR leave entries where the module is activated.

inoERP role-based access control with users, roles, and permissions maps to Dolibarr Users and permission groups. We export user accounts and role assignments. Mappings must translate inoERP permission strings to Dolibarr's permission model, which uses a module-level permission grant system rather than named roles. We flag any inoERP role that does not map directly to a Dolibarr permission group and provide a permission matrix for the customer to assign post-migration. Active vs inactive user status carries forward.

inoERP asset registers with acquisition details, depreciation schedules, and asset categories map directly to Dolibarr's Asset module. We export the full asset record including acquisition cost, in-service date, depreciation method, accumulated depreciation, and book value. Depreciation methods (straight-line, declining balance) map to Dolibarr's supported depreciation calculation methods. Asset categories map to Dolibarr asset classification.

inoERP payroll generates electronic bank files for direct deposit. Dolibarr's payroll module is an optional extension with basic salary and deduction management. We export payroll registers, leave balances, and compensation history as Dolibarr salary records where the module is activated. Bank file formats are flagged as non-migratable because inoERP generates custom-format files; the customer should configure Dolibarr's bank transfer module or use a separate payroll tool for direct deposit generation.

inoERP extended attributes on any object map to Dolibarr's Extra Fields system (core_extrafields table). We export the field definitions (name, type, options) and values per record. Dolibarr's Extra Fields support varchar, text, int, float, date, datetime, select, checkbox, and link types. Complex inoERP extended fields (like formula-based calculations) are flagged as requiring post-migration review because Dolibarr does not support formula-driven calculated fields natively.