Migrate from BizAutomation Cloud ERP to Acumatica

BizAutomation Customers map to Acumatica Business Accounts. Every Business Account requires a CompanyID assignment — BizAutomation's single-company context maps to the primary Acumatica company. Customer type (reseller, distributor) migrates as a custom classification field.

BizAutomation Contact records map to Acumatica Contacts linked to the corresponding Business Account via the AccountID field. Primary contact flags, roles, and email addresses are preserved. Contacts without a parent Customer receive the default migrated account.

BizAutomation inventory items map to Acumatica Stock Items with ItemID as the key. The Item Class determines the default posting accounts. BizAutomation's warehouse assignment on the item record translates to the primary Warehouse ID on the Acumatica Inventory Item — secondary warehouses require additional line-level records.

BizAutomation orders map to Acumatica Sales Orders using Order Nbr as the external reference. BizAutomation's order-status values map to Acumatica's Shipment Status and Invoice Status pick-list values. Line items map to Sales Order Details with Inventory ID, UOM, quantity, and unit price.

BizAutomation invoices map to Acumatica AR Invoices. The Invoice Nbr becomes the Invoice Reference Nbr. Payment terms, due dates, and hold status are preserved. BizAutomation's one-step invoice generation splits into separate Invoice and Payment applications in Acumatica.

BizAutomation POs map to Acumatica Purchase Orders with the PO Nbr as external reference. Vendor assignment maps by email match to Acumatica Vendors. Line items with landed-cost details become separate PO line entries with the Inventory ID and vendor part number.

BizAutomation Vendors map to Acumatica Vendors. Payment terms, tax zone assignments, and the Remit-to address copy over directly. Multi-address vendors use Acumatica's address record model with a primary default flag.

BizAutomation's flat chart of accounts maps to Acumatica's segmented Account structure. Each BizAutomation account code becomes an Acumatica account with up to six configurable subaccount segments. Account type (Asset, Liability, Income, Expense) maps to the Account Group field, and the active/parent flags translate to IsActive and UnitID on the account record.

BizAutomation journal entries map to Acumatica GL Journal Transactions with the Batch Nbr as external batch reference. Each line's account code resolves to the Acumatica AccountID + SubID combination. Debit and credit amounts, the transaction date, and the description copy over. Historical entries are migrated as read-only batches.

BizAutomation stores a single warehouse reference on items. Acumatica's Warehouse entity requires a SiteCD, SiteName, and BranchID assignment. We create Acumatica Warehouse records per unique warehouse identifier in BizAutomation and surface any secondary warehouse usage as a custom field on the Inventory Item.

BizAutomation prospects that have been converted to customers merge into the Business Account object. Unconverted prospects migrate to Acumatica Leads. Both paths preserve the original create date, owner assignment, and any custom fields.

BizAutomation project records map to Acumatica Projects with the Project ID as the external reference. Customer assignment links via the CustomerID lookup. Budget lines, milestones, and tasks migrate as Project Tasks — original dates and completion percentages are preserved in custom fields.

BizAutomation user-defined fields on any object map to Acumatica custom fields (DAC attributes with the PXDimension attribute) or as free-text UDFs. Field type mapping: text fields map to varchar, numeric fields to decimal, pick-lists to the Acumatica string field with a documented value map.

BizAutomation file attachments on orders, customers, and items re-upload to Acumatica's Note records linked to the target entity via the NoteID foreign key. Files are stored in the Acumatica database or attached storage per the instance configuration. Original filenames and upload timestamps are preserved.