Migrate from Base ERP to Acumatica

Base Customer maps to Acumatica Customer (BAccount with Customer type). We preserve the Base customer ID in CustomerExt.NoteID for traceability. Primary address and contact email transfer as the default location. Tax zone assignments in Acumatica must be set by your tax configuration — we flag any Base tax jurisdiction that lacks a matching Acumatica TaxZone.

Base Vendor maps to Acumatica Vendor (BAccount with Vendor type). Remit-to address and 1099 flag carry over. Multi-site vendors in Base with different PO addresses require multiple Acumatica locations — we create the primary location and flag additional addresses for manual branch assignment.

Base inventory items with stock-tracking enabled become Acumatica Stock Items. Items marked as non-stock in Base create Non-Stock Items or Service Items in Acumatica based on the item type flag. Base item class (valuation method, posting group) maps to Acumatica ItemClass with its own valuation method and deferred revenue settings.

Base flat warehouse codes become Acumatica Warehouse records scoped by Branch. If Base tracks bin locations within a warehouse, we create Acumatica Warehouse Locations under the corresponding branch — your warehouse manager configures the location type (bin, shelf, pallet) post-migration in Acumatica's IN205000 screen.

Open Base sales orders migrate to Acumatica SO301000 with original order dates, customer references, and line items. Order statuses carry over using SO.Status field values. Completed or invoiced orders do not migrate — their invoice history appears as AR Invoice records in Acumatica.

Open Base purchase orders migrate to Acumatica PO301000 preserving vendor, line items, quantities, and promised delivery dates. PO status mapping follows the same logic as sales orders, with status codes translated to Acumatica equivalents. Historical closed POs are not migrated — vendor ledger history transfers via the AP Invoice records that represent the posted payables.

Open AR invoices from Base transfer to Acumatica AR301000 with original invoice date, due date, terms, and balance. Credit memos migrate separately. We preserve the Base document number as a reference. Paid invoices older than the retain-history window are archived externally.

Open AP invoices from Base transfer to Acumatica AP301000 with original document dates and due amounts. Vendor reference numbers map to Acumatica's ExtRefNbr field for cross-system matching and audit trails. Prepayments and unapplied payments in Base migrate as miscellaneous payments with explicit allocation records to maintain proper payables structure in Acumatica.

Base GL accounts map to Acumatica GLAccount with Active flag, Type (Asset/Liability/Revenue/Expense/Header), ClassID, and BranchID assignments. Subaccounts in Base become Acumatica segment values in a configured subaccount dimension. Acumatica requires at least one active account in each Type — we flag gaps before migration.

Base manual journal entries migrate as Acumatica GL Transactions in GL301000 with original posting date, description, and line-level debits/credits. Recurring journal templates in Base do not carry over — we export the recurrence schedule as a reference for Acumatica's recurring schedule configuration.

Base payment term codes (Net 30, 2/10 Net 30, etc.) map to Acumatica CashDiscount records linked to Terms entities. Custom Base terms get recreated as Acumatica Terms with the same due days and discount percentage — your AP manager reviews the Terms screen before go-live.

Closed Base shipments and receipts that have not yet been invoiced migrate as Acumatica Shipments (SO302000) and Receipts (PO302000) respectively, preserving original shipment dates and quantities. Any shipment or receipt already linked to an invoice in Base is already represented in AR/AP and is not duplicated in the migration — the invoice record carries forward instead.

Base user-defined fields on Customer, Vendor, or Inventory entities require Acumatica schema extensions. We create the UDF as a DAC field on the corresponding Acumatica entity with matching data type. Validation rules, pick-list values, and display names are mapped per the Acumatica customization project spec.

Base users with transactional ownership (sales reps, order processors) resolve by email match against Acumatica users. Unmatched Base owners are flagged and assigned to a fallback employee until your admin creates the Acumatica user — no record lands without an owner assignment.

Base file attachments on inventory items, customer records, or orders are downloaded and re-uploaded to Acumatica's file storage. File size limits apply — files exceeding 25MB are noted for manual re-upload. Inline images in notes are extracted and stored as separate attachments.