Migrate from Zenscale to Acumatica

Zenscale items map to Acumatica's InventoryItem DAC. Stock items (tracked with qty) become StockItem = true; non-stock items (consumables, services) become StockItem = false. Unit of measure from Zenscale's UOM field maps to Acumatica's InventoryUOM. Branch assignment defaults to your primary warehouse unless you specify a branch mapping rule.

Zenscale customer records map directly to Acumatica Customer DAC. The customer class from Zenscale maps to Acumatica's CustomerClass. Zenscale's GST/tax registration number becomes the Tax Registration ID (TaxRegistration Nbr) on the customer. Multiple Zenscale contact persons per customer map to Acumatica Contact records linked via the Contact DAC.

Zenscale vendor records map to Acumatica's Vendor DAC with the vendor class used as CustomerClass. Payment terms from Zenscale translate to Acumatica PaymentRule and PaymentTermID on the vendor. Zenscale's vendor GST number migrates as TaxRegistration Nbr. Primary contact becomes an associated Contact record.

Zenscale employee records map to Acumatica's Employee DAC with the employee type determining the Acumatica EmployeeType (Salaried, Hourly, or Contract). Department from Zenscale becomes the DepartmentID. If Zenscale payroll is used, salary and bank details are carried over to Employee DAC attributes — but tax filing and payroll processing remain a separate Acumatica Payroll configuration.

Zenscale BOMs map to Acumatica's BillOfMaterials DAC linked to the finished item. Material components and quantities transfer as BOMLine records. Zenscale's operation routing (if any) maps to Acumatica's routing steps. Multi-level BOMs in Zenscale create nested BOM revisions in Acumatica — we flatten and create a revision per BOM level.

Zenscale production orders map to Acumatica ProductionOrder records. The production item links to the finished good BOM. Material issue and labor step records become material and labor allocations in Acumatica. Open Zenscale production orders transfer as Unreleased or In Process; completed ones become Closed with actuals carried over as completed quantities and timestamps.

Open Zenscale purchase orders map to Acumatica POOrder records. PO lines map to POLine with vendor, item, quantity, and unit cost. Zenscale's PO status (open/closed) determines Acumatica's status (Open, Pending Approval, or Closed). Completed POs migrate as Closed with receipt history preserved as landed-cost allocations.

Zenscale sales orders map to Acumatica SOOrder records. Customer, line items, quantities, and pricing transfer to SOLine. Zenscale's order status (confirmed/fulfilled) becomes Acumatica's status (Open, Completed, Cancelled). Open sales orders migrate as open; invoiced orders in Zenscale may require AR Invoice creation in Acumatica.

Zenscale's stock-on-hand balances per item per warehouse transfer to Acumatica as opening inventory receipts via INReceiptEntry with ReceiptType = Adjustment. Each receipt line carries the item, quantity, location, and unit cost from Zenscale. These are posted in migration mode so they don't generate GL entries — the trial balance is set separately.

Open Zenscale customer invoices transfer to Acumatica as ARInvoice records with DocType = Invoice. Customer, invoice number, date, line items, tax, and balance due carry over. We post these in migration mode so they don't trigger GL — the opening AR balance is reconciled via a separate trial-balance journal. Invoiced-and-paid Zenscale invoices are optionally migrated as historical records for audit continuity.

Open Zenscale vendor bills map to Acumatica APBill records with DocType = Bill. Vendor, bill number, date, line items, tax, and amount due transfer. Posted in migration mode to avoid duplicate GL entries. Paid bills may be migrated as historical records or omitted depending on your audit requirements — we surface this decision in the pre-migration scope document.

Zenscale journal entries — including payroll journal, cost allocation, and adjustment entries — merge into Acumatica GLBatch records. Each Zenscale debit/credit pair becomes a GLTransaction line. Because Acumatica uses branch-aware posting, we assign all migrated journal lines to the primary branch unless you specify multi-branch distribution. Historical journal migration is optional and scoped to your last 12–24 months.

Zenscale custom properties on items, customers, or vendors become Acumatica Usr-prefixed extension fields on the corresponding DAC (e.g., UsrHSNCode on InventoryItem). We create these via a customization project during setup. Data types map: text → string, number → decimal, date → date, picklist → selector or string.