Migrate from mybizz erp to Acumatica

MyBizz ERP customers map 1:1 to Acumatica Customer records. The Customer Class (e.g., CUST-STD) must be assigned in Acumatica before import — this controls default AR account, credit terms, and tax zone. If MyBizz ERP stores multiple contacts per customer, secondary contacts migrate as related Contact records linked via the Contacts tab in Acumatica.

MyBizz ERP vendors map to Acumatica Vendor records. A Vendor Class must exist in Acumatica to assign default AP account and payment term. If MyBizz ERP tracks vendor tax registration numbers, these map to the Tax Registration ID field on the Vendor detail screen — required for VAT-compliant purchase invoices in Acumatica.

MyBizz ERP inventory items map to Acumatica Stock Items, but valuation method (Standard, Average, FIFO, Specific ID) must be assigned per item — this is an Acumatica schema decision that cannot be inferred from MyBizz ERP's data. We surface the current valuation flag in the source export and flag any items where MyBizz ERP stores a different method than what your Acumatica configuration expects.

MyBizz ERP's single-segment account codes (e.g., 4000-Sales) must be decomposed into Acumatica's multi-segment structure. The first segment is the AccountCD; subsequent segments map to sub-account dimensions. Every account must be assigned an Account Class — Sales accounts go to the SALES class, cost-of-goods sold to COGS, assets to FIXEDASSET or LIABILITY as appropriate.

MyBizz ERP account categories map directly to Acumatica Account Classes. The Account Class controls posting account defaults, tax-related settings, and whether the account type is Asset, Liability, Equity, Revenue, or Expense. We map MyBizz ERP category names to the closest Acumatica class ID (e.g., MyBizz 'Income' → Acumatica SALES).

MyBizz ERP invoice headers map to Acumatica AR Invoice rows (DocType = Invoice or CreditMemo). Invoice lines map to the Details tab with InventoryID, BranchID, WarehouseID, and AccountCode populated per line. The Acumatica BranchID field must correspond to a pre-created Branch record — if MyBizz ERP invoices do not track a branch, all lines default to the primary branch.

Purchase invoices from MyBizz ERP map to Acumatica AP Invoice rows (DocType = Invoice or CreditMemo). Line items map to Details with the same field set as AR invoices. For bills paid in a foreign currency, the exchange rate and payment差异 are preserved as separate GL lines. Tax amount lines in MyBizz ERP map to separate tax-detail rows in Acumatica.

MyBizz ERP cash receipts map to Acumatica Payments applied against open AR invoices. The Payment record is created with the customer reference, amount, and payment method; application records link the payment to the specific invoice reference number. Open (unapplied) payments remain as unapplied cash in Acumatica until reconciled manually or via the Reconcile Transactions screen.

MyBizz ERP vendor payments map to Acumatica Payments with DocType = Check or Wire. Application records link the payment to the specific AP invoice reference number. The payment method (cash, bank transfer, check) maps to the Payment Method configured in Acumatica's Cash Management module.

MyBizz ERP journal entries map to Acumatica Journal Transactions (GL batch records). Each debit and credit line in MyBizz ERP becomes a separate GL transaction line in Acumatica with the correct AccountCD, Subaccount segment values, DebitAmt, and CreditAmt. The batch date maps to the TranDate; batch reference maps to ExtRefNbr for traceability.

MyBizz ERP opening balances for customers, vendors, and GL accounts map to Acumatica's Opening Balance workspace. Customer opening balances become AR Invoice records with DocType = Invoice and a special reference flag. Vendor opening balances become AP Invoice records. GL account opening balances post directly to the GL with a period assigned to the opening period in the ledger calendar.

Any MyBizz ERP custom fields added to standard screens (customer notes, item classification tags, invoice custom flags) are preserved as Acumatica Usr-prefixed custom fields. These must be pre-created in Acumatica's Customization Project editor before data import runs — we provide the field definition (name, data type, pick-list values if applicable) as part of the pre-migration schema plan.

MyBizz ERP file attachments (e.g., scanned invoices, purchase orders) are re-uploaded to Acumatica's Note and Attachment framework, linked to the relevant entity record (Customer, Vendor, Invoice). Acumatica stores attachments against the entity note ID. We download source attachments, re-upload to the corresponding Acumatica record, and preserve the original filename.

MyBizz ERP tax codes with flat rate percentages do not map to a single Acumatica field. We extract the tax rate and applicable accounts, then create corresponding Tax Rev records in Acumatica grouped by Tax Group and Tax Type (Output or Input). Tax Zone assignments for customers and vendors are configured separately in Acumatica's Tax Zone screen.

MyBizz ERP user accounts and employee records do not migrate. Acumatica user accounts are provisioned through the Access Management screen and licensed per Acumatica's own user model. Employee records used for reporting or HR purposes are outside FlitStack AI's migration scope and should be handled by Acumatica HR module setup or a dedicated HR migration tool.