Migrate from Fraction ERP to Acumatica

Fraction ERP customer records map directly to Acumatica Customers. The customer name, contact email, phone, and billing address fields transfer as-is. Fraction ERP does not distinguish between shipping and billing addresses per customer; we surface both in Acumatica's Address tab and your admin sets the default roles.

Fraction ERP parts with bill-of-materials links and stocking flags map to Acumatica Stock Items. Parts marked as non-stocked in Fraction map to Non-Stock Items. The PartID becomes the Acumatica Inventory CD; the description, unit of measure, and last purchase price transfer as attributes. Stock qty on hand requires an opening inventory adjustment import after item creation.

Fraction ERP BOMs define multi-level product structures with components and quantities-per. Acumatica's BOM uses BOMID, template materials, and warehouse-scoped line items. We flatten Fraction BOM subassemblies into Acumatica multi-level BOM structures — each nested assembly becomes a separate BOM record linked by the AsmOf field. Phantom BOMs use the Phantom BOM flag.

Fraction ERP sales orders map directly to Acumatica Sales Orders. Order number, customer reference, line items (part + quantity + unit price), order date, and promised date transfer as SOOrder records. Fraction order statuses (draft, confirmed, shipped, invoiced) map to Acumatica SOOrder status values (on hold, pending, open, completed, cancelled).

Fraction ERP purchase orders map to Acumatica Purchase Orders. Vendor, line items (part + quantity + cost), expected delivery date, and PO status transfer as POOrder records. Acumatica's receipt workflow (receiving before AP) differs from Fraction's simpler model — we surface this distinction in the migration plan for your purchasing team.

Fraction ERP works orders are the core production record. They map to Acumatica Production Orders (SOOrderType = 'Production'). The Fraction works order number becomes the Production Nbr; the linked BOM revision and warehouse determine material allocation in Acumatica. Labor posting data from shop floor data capture is preserved as production remarks and can feed into Acumatica's labor tracking if configured.

Invoiced sales orders in Fraction ERP map to Acumatica AR Invoices. Invoice number, customer, line items, tax amount, and invoice date transfer. Acumatica's invoice-to-payment workflow (AR Invoice → Payment Application → GL) differs from Fraction's simpler model — we generate an opening balance import for outstanding AR to avoid duplicate billing.

Fraction ERP inventory snapshots and cycle count adjustments map to Acumatica Inventory Adjustments. Each adjustment line specifies the inventory ID, site, qty variance, and reason code. Historical adjustments with timestamps are imported as adjustment records in date order. The site ID maps to the warehouse location in Acumatica, and reason codes are validated against the Reason Code ID list.

Fraction ERP vendors map directly to Acumatica Vendors. Vendor name, contact email, payment terms, and default GL account carry over. Acumatica's separate remittance address record requires mapping from Fraction's single vendor address — we assign the primary Fraction address as the Remit Address and flag any secondary addresses for manual entry.

Fraction ERP custom fields on parts (such as material specifications, weight, or supplier codes) do not have an Acumatica native equivalent. We create Usr-prefixed custom fields on the InventoryItem DAC via an Acumatica Customization Project. Each custom field requires a published customization package before data import; we include the schema plan and package generation in the migration scope.

Fraction ERP's accounting integrations with Xero, QuickBooks, or Sage have no Acumatica equivalent because Acumatica carries a full native general ledger, AP, and AR. Migrated transactional data flows directly into Acumatica GL accounts; no third-party sync is required. The integration links are discontinued at cutover.

Fraction ERP users with order or works-order ownership are matched to Acumatica Employees and Users by email. Unmatched owners are flagged before migration and assigned to a fallback Acumatica user so no record lands without an owner. Fraction ERP permission sets do not map to Acumatica roles and must be reconstructed in Acumatica's Access Rights by your admin.