Migrate your Orion ERP data

Orion stores the COA as a core master-data structure. We extract via the built-in report engine, preserving account code, name, type, and currency settings. Multi-segment chart-of-accounts requires us to detect and flatten or restructure hierarchies depending on the destination ERP's requirements.

Customer master records include contact details, billing address, payment terms, and credit limits. We extract via the standard customer listing report and map to the destination's account or contact object, flagging any custom fields for explicit value mapping.

Vendor master includes name, tax ID, payment terms, and bank details. Extracted through the vendor report export and mapped to the destination's vendor/supplier object. Tax ID format validation is applied during scoping to catch country-specific formatting differences.

General ledger 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 entry batches. Effective-dated transactions require chronological ordering during load.

Open AP records include vendor reference, invoice number, amount due, and due date. Orion stores AP as a subset of the financial module. We flag open invoices separately from historical AP for opening-balance treatment in the destination ERP.

Open AR records include customer reference, invoice number, amount receivable, and due date. Similar to AP, we extract open AR as a distinct scope item and map it to the destination's open invoice or AR aging report structure.

Item master records include SKU, description, unit of measure, cost, and warehouse location. Extracted via the inventory management report. BOM (bill of materials) data for the Manufacturing Cloud edition is treated as a separate object requiring additional field mapping.

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 must be preserved to ensure the destination creates or closes matching records correctly.

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 the destination's fulfillment workflow.

Employee records include name, department, job title, compensation, and employment dates. Extracted through the HR management module report. Effective-dated compensation history requires us to sequence records chronologically during the import to preserve pay-grade changes.

Orion allows custom fields on master and transaction records. Custom field existence and data types vary by edition and customer configuration. We detect all custom properties during the scoping export and apply explicit value-mapping rules for each before load.

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 package. Customers should export documents manually or via a separate document management export if required.