Migrate from Orion ERP to Dolibarr ERP

Orion stores the COA as a core master-data structure with multi-segment support. We extract account code, name, type, and currency settings via the financial report export. In Dolibarr, the accounting module must be activated before importing. We create each Orion account as a Dolibarr bank account record or general ledger account under the accounting menu, preserving the account code as the primary identifier. Multi-segment COA splits into parent and child account codes per Dolibarr's hierarchical account plan structure. Currency and type metadata map to Dolibarr account attributes.

Orion customer master records include contact details, billing address, payment terms, and credit limits. We extract via the standard customer listing report. Dolibarr uses a unified Third Party object with a Mode flag (Customer, Supplier, or Both). We import Orion customers as Dolibarr Third Parties with Customer mode enabled, mapping billing address to Dolibarr's address fields, payment terms to the payment condition dictionary, and credit limits to the risk management fields. Tax ID format validation is applied per country during transform.

Orion vendor master includes name, tax ID, payment terms, and bank details. We extract through the vendor report export. In Dolibarr, vendors import as Third Parties with Supplier mode enabled. We map Orion vendor payment terms to Dolibarr's supplier payment condition dictionary, and tax registration numbers to the specific VAT/SIRET/SIREN extra fields Dolibarr supports for EU and international jurisdictions.

Orion GL entries include header metadata (date, journal number, description) and line items (account, debit, credit). We extract full GL history via the financial report export and import as journal entries into Dolibarr's accounting module. Each Orion journal type maps to a corresponding Dolibarr journal (sales, purchases, bank, miscellaneous). Debit and credit columns map directly to Dolibarr debit and credit fields. Historical GL migration requires the accounting module to be active and the fiscal year to be open in Dolibarr before entries are posted.

Orion stores open AP as live financial records rather than separate aging snapshots. We extract open invoices with vendor reference, invoice number, amount due, and due date as a distinct scope item. In Dolibarr, open AP injects as opening-balance supplier invoices or miscellaneous journal entries with an opening-balance account rather than new invoices to avoid double-posting during the go-live period. The customer's AP team reviews the opening-balance invoice list before posting.

Orion open AR records include customer reference, invoice number, amount receivable, and due date. We extract open AR as a distinct scope item separate from historical AR. In Dolibarr, open AR maps to customer invoice records with opening-balance treatment via a dedicated AR opening-balance account, or as draft invoices that the customer's AR team validates before posting. Due dates and aging buckets are preserved as invoice due dates or migrated to Dolibarr's payment schedule feature.

Orion item master records include SKU, description, unit of measure, cost, and warehouse location. We extract via the inventory management report. Dolibarr's product module must be activated, and we import items as products with stock tracking enabled. Orion SKU maps to Dolibarr's ref (reference) field; description maps to the product label; unit of measure maps to the unit dictionary. Current stock quantities per warehouse import into Dolibarr stock warehouses. Note that Dolibarr's stock management is designed for simple setups and does not support advanced manufacturing or multi-level BOM tracking.

Orion PO headers and lines are available through the procurement module report export. We extract PO status, vendor assignment, and line-item quantities. Open versus closed PO status is preserved: open POs import into Dolibarr as draft or validated supplier orders depending on their Orion status, and closed POs import as historical records for audit. Line items map to Dolibarr supplier order lines with product reference, quantity, and unit price resolved against the imported product catalog.

Orion sales order records include customer reference, product lines, pricing, and order status. We map order headers and lines separately and flag fulfilled versus pending lines to align with Dolibarr's order statuses (Draft, Validated, Shipped, Closed). The customer reference from Orion becomes Dolibarr's ref_customer field. Pricing migrates with the same currency and discount treatment as the source. Pending orders import as draft or validated customer orders; fulfilled orders import as closed records for historical reporting.

Orion employee records include name, department, job title, compensation, and employment dates. We extract through the HR management module report. Dolibarr's HR module must be enabled. Employee records map to Dolibarr users if the employee needs system access, or to contacts linked to a dedicated employee third-party structure if Dolibarr is used primarily for HR record-keeping without full system login. Effective-dated compensation history requires us to sequence records chronologically and inject as Dolibarr HR salary records if the HR module includes salary tracking.

Orion allows custom fields on master and transaction records with data types that vary by edition and customer configuration. We detect all custom properties during the scoping export. In Dolibarr, custom fields are implemented via Setup > Dictionaries > Extra Fields on the target object. We pre-create the Dolibarr extra field schema before migration, mapping Orion data types to Dolibarr field types (text, varchar, int, float, date, select, checkbox). Custom field values migrate as part of the standard record import using Dolibarr's extrafields column naming convention (extrafields_keyname).

Binary attachments and uploaded documents stored within Orion's document management layer are not accessible via the standard report export. We do not migrate attachments as part of the standard migration scope. We log every record with an associated attachment and deliver a manifest to the customer's admin team identifying which records had documents in Orion. The customer coordinates a separate export of the document management directory, and we can advise on the target Dolibarr document root structure (dolibarr_main_data_root) for manual re-association post migration.

The Orion Manufacturing Cloud edition includes bill of materials and work order objects not present in Dolibarr. Dolibarr has no dedicated manufacturing module, no BOM capability, and no production order tracking. If the customer uses Orion Manufacturing Cloud with BOM data, we scope this as a write-off and deliver a written inventory of BOM records and work order statuses for the customer to evaluate Dolibarr alternatives (Odoo Manufacturing, ERPNext) or handle in a separate manufacturing-specific migration.