Migrate from Orion ERP to Acumatica

Orion customers migrate as Acumatica Business Accounts with the Customer check-box enabled under the Relationships tab. Primary contact, address, and credit terms map to the corresponding Business Account fields. Multi-address support handled via Location records on the Business Account. Shipping and billing addresses are maintained as separate Location entries with distinct defaults for each document type.

Orion vendors map to Acumatica Business Accounts with the Vendor check-box enabled under the Relationships tab. The 1099 reporting flags, W-9 status, and payment terms (Net-30, Net-60) transfer as attributes on the Business Account's Payment Settings tab. Remit-to addresses become separate Location records on the vendor account. Tax Registration IDs are stored in the Tax Registration ID field for compliance tracking.

Orion's flat account codes (e.g., 5000-Revenue) expand into Acumatica's segment-structured accounts using the Account segment field. If Orion uses a cost-center suffix, that suffix becomes the Subaccount segment in Acumatica, enabling Branch-Account-Subaccount posting combinations that Orion's flat model cannot express. The account type (Asset, Liability, Equity, Revenue, Expense) maps directly to Acumatica's Type field.

Orion's multi-company configuration maps directly to Acumatica Branches, where each Branch represents a distinct legal entity or operating location within the tenant. Each Orion legal entity becomes an Acumatica Branch with its own posting ledger and branch-specific account restrictions. Intercompany transactions between Orion companies require Acumatica Inter-Branch accounting configuration post-migration to maintain proper elimination entries.

Orion inventory item types (stock, non-stock, service) map to Acumatica Item Class and item-level settings. Stock items in Orion carry unit cost, reorder point, and warehouse quantities — these become Acumatica Stock Item records with Warehouse Details and Default UOM conversions preserved. Item class assignments determine which posting accounts (Sales, COGS, Inventory) are used at transaction time.

Open AR invoices migrate with original invoice number preserved in the Reference Nbr. field. Line items, tax amounts, and payment terms carry forward. Note that Acumatica requires customer Location to be set before AR invoices can post — location records must migrate before or alongside open invoice data. Partially paid invoices carry forward remaining balance as the document amount, with payment applications migrated as separate records.

Open AP invoices migrate with original vendor invoice number stored in the Reference Nbr. field. Discount terms and due dates transfer to Acumatica's payment schedule logic, with the Payment Terms ID field controlling due date calculations. Prepayments recorded in Orion map to AP Payment applications on the vendor account, maintaining the linkage between prepayment documents and their application against invoices.

Open and recently closed Sales Orders migrate with line items, scheduled shipments, and pricing. Acumatica's Confirmation / Allocation / Picking / Shipping workflow state maps from Orion's order-status lifecycle. Completed orders migrate as historical records; in-flight orders require status reconciliation against Acumatica's status values (Open, Pending, Completed, Cancelled, Draft). Order dates and customer references are preserved for audit trail purposes.

Open Purchase Orders migrate with vendor account, line items with item IDs and quantities, and expected receipt dates carried forward. Acumatica's Drop-Ship and Blanket Order features represent optional configurations available post-migration if Orion utilized those capabilities. Order status values map to Acumatica Purchase Order statuses (Open, Pending, Completed, Cancelled, Draft) to maintain accurate workflow state representation.

Orion project records (from the Contracting Cloud or Project module) map 1:1 to Acumatica Projects with tasks as child records under the same Project. Budget lines, billing rules, and employee assignments transfer as Project Attributes and员工 allocations. Integrated Invoicing flag maps to Acumatica's billing rule structure, preserving automatic invoice generation settings from Orion's project configuration.

Orion UDFs are catalogued by data type (string, integer, date, pick-list) and mapped to Acumatica custom fields using the Customization Project editor or the VTECHAPI endpoint's Writeback field slots (Custom String 1–3, Custom Integer 1–3, Custom Boolean 1–3, Custom Date 1–3). Pick-list UDFs require value-by-value mapping when source and destination enumerated values differ.

Orion fixed asset records (asset tag, acquisition date, depreciation method, book value) map to Acumatica Fixed Asset records with all details preserved. Accumulated depreciation posts to the linked GL account, and asset classes determine the depreciation template applied in Acumatica. The asset record includes acquisition cost, useful life, and salvage value fields that drive the depreciation calculation schedule.