Migrate from Decision Builder to Acumatica

Decision Builder customer records map to Acumatica's AR Customer entity. Acumatica requires a Customer Class to be assigned at creation — we use the primary industry segment from Decision Builder or a default 'Standard' class. Customer addresses and contacts are stored as sub-entities in Acumatica.

Decision Builder vendors map to Acumatica's AP Vendor entity. Like customers, vendors in Acumatica require a Vendor Class assignment determined by the vendor's primary business type. We pull the primary payment terms and remittance address from Decision Builder's vendor record, translating these to Acumatica's Terms schedule and address sub-entity structure respectively. Vendor balance carryforward uses the most recent Statement as-of date.

Decision Builder items migrate as Acumatica Inventory Items with their item type preserved (stock vs non-stock vs service). Stock items require a default warehouse assignment and valuation method mapping — Decision Builder's cost layer configuration (FIFO, Average, or Standard cost) translates directly to Acumatica's ValMethod field. Item class assignments carry forward using name matching against Acumatica's Inventory Item Class list.

Decision Builder GL accounts map to Acumatica Accounts in the Chart of Accounts. Account numbers are preserved as-is for AccountCD continuity. Account type (Asset, Liability, Equity, Revenue, Expense) maps to Acumatica's Account Group structure. Subaccounts in Decision Builder map to Acumatica subaccounts using the subaccount mask defined in your Acumatica Configuration Settings.

Open sales orders migrate as Acumatica Sales Orders with their current status preserved (Open, On Hold, Pending). Order numbers, line items, quantities, and pricing are all preserved through direct field mapping. Released and invoiced orders migrate as completed documents if historical posting is included in scope, with their original completion dates and invoice references carried forward.

Open purchase orders in Decision Builder become Acumatica PO Orders with Open status preserved. The vendor reference, line items with quantities and expected receipt dates, and drop-ship flags are all carried forward. Closed or received purchase orders migrate as history records if the Accounts Payable audit trail is in scope, preserving original receipt dates and assignment details.

Open and recently posted AR invoices from Decision Builder map to Acumatica AR Invoice documents. Invoice number, date, customer reference, line amounts, and tax amounts are all preserved through direct field mapping. Fully paid invoices migrate as history records with a Paid status flag set, maintaining the original payment date and reference for audit trail completeness.

Open AP invoices from Decision Builder migrate as Acumatica AP Invoices. Vendor reference, invoice number, date, line amounts, and tax information are preserved through direct mapping. Decision Builder payment terms are translated to Acumatica's Terms schedule attached to the vendor record, and discounts taken are captured in the discount fields on the migrated invoice.

Decision Builder BOMs with component items map to Acumatica BOM structures maintained in Manufacturing Engineering. Multi-level BOMs are replicated using Acumatica's BOM revision hierarchy with parent and child component relationships preserved. Phantom BOMs and BOMs tied to specific manufacturing orders use Acumatica's BOM versions linked to warehouse-specific configurations.

Decision Builder work orders map to Acumatica Production Orders. The linked BOM and step or operation routing are preserved as Acumatica production specifications. Operation sequences, labor estimates, and machine time requirements map to production Labor codes and Work Center assignments for scheduling accuracy.

Decision Builder projects migrate as Acumatica PM Projects with their associated task hierarchies preserved. Project status, billing rule, and customer link are translated directly. Time and material versus fixed-price billing rules map to Acumatica's billing rules on the project, and cost budgets translate to PM Budget lines with allocation by project task.

Decision Builder users with active login access migrate as Acumatica Employees and Users with corresponding login credentials. Email address serves as the matching key between systems. Unmatched users are flagged in the pre-migration report for Acumatica admin setup before the full migration commits. Branch, department, and cost rate assignments are preserved through direct field mapping.

Decision Builder custom fields on any entity migrate as Acumatica custom fields maintained in a customization project. Fields use the Usr-prefix naming convention and are defined at the DAC level in extension classes. We generate the complete customization package XML so it can be published in Acumatica's Customization Project editor before data loads occur, ensuring the schema is ready to receive the extended data.

Decision Builder approval chains and workflow logic have no Acumatica equivalent that can be migrated directly. We export Decision Builder workflow definitions as a documented reference including trigger conditions, approval thresholds, escalation paths, and notification actions. Your Acumatica administrator uses this documentation to rebuild equivalent automation using Business Events, screen-level workflow automation, and notification templates in the Acumatica workflow designer.

Custom report definitions and dashboards from Decision Builder cannot be auto-migrated to Acumatica's reporting tools. We export the complete report metadata including column names, filter definitions, sort order, grouping levels, and calculation formulas as a structured rebuild guide. Your team uses this guide to reconstruct equivalent reports using Acumatica's Generic Inquiry Query Designer and Report Designer tools.