Migrate from ERP BOS to Acumatica

BOS ERP GL accounts map to Acumatica GL Account records. The BOS ERP account code becomes Account.AccountCode; the account description maps to Account.Description. We load all active and inactive accounts with their posting settings preserved. Accounts with subaccounts require Acumatica's subaccount segment structure to be configured before this import runs.

BOS ERP customer master records map to Acumatica Customer entities. The customer name, contact name, email address, phone, billing address, shipping address, and payment terms all transfer directly. BOS ERP credit limits become Customer.CreditLimit in Acumatica. Owner resolution happens by email match against Acumatica users.

BOS ERP vendor master records map to Acumatica Vendor entities. The vendor name, contact name, email, phone, billing address, payment terms, and terms discount percentages transfer directly. BOS ERP AP aging group assignments map to Vendor.TermsID for consistent payable categorization in Acumatica.

BOS ERP product and inventory item records map to Acumatica StockItem entities. The item number, description, unit of measure, standard cost, last cost, and inventory account link transfer directly. BOS ERP product class maps to Acumatica StockItem.ItemClass; requires Acumatica Item Class configuration before migration.

BOS ERP warehouse records map to Acumatica Location entities. The warehouse code, name, and address transfer directly as LocationCD, Descr, and AddressLine1 plus City/State/PostalCode fields. Each location must exist in Acumatica before inventory balances can be loaded under it. We sequence Location records before any inventory snapshot import to maintain referential integrity and prevent import failures.

BOS ERP inventory on-hand quantities map to Acumatica Inventory Receipt documents created with a Beginning Balance document type. The receipt date, item ID, warehouse location, and quantity transfer. Unit cost is recalculated from BOS ERP average or standard cost at migration time. Each receipt generates the appropriate GL entry to the inventory account.

BOS ERP open AR invoices become Acumatica AR Invoice documents with a status that preserves openness. The invoice number, customer ID, invoice date, due date, description, and line amounts map directly. Line items include inventory ID if applicable, quantity, and unit price. Unapplied credit memos migrate separately as AR Credit Memo documents.

BOS ERP open AP invoices become Acumatica AP Bill documents with openness preserved. The voucher number, vendor ID, invoice date, due date, and line amounts map directly. Prepayments and unapplied debit memos migrate as separate AP Payment documents. We verify vendor invoice numbers are unique per vendor before importing to avoid Acumatica's duplicate reference-number validation.

Open BOS ERP sales orders map to Acumatica Sales Order records. Order number, order date, customer ID, shipping address, and all order lines with item ID, quantity, and unit price transfer. Completed or closed orders are not migrated as transactional documents; their revenue impact is captured in the GL history instead.

Open BOS ERP purchase orders map to Acumatica Purchase Order records. PO number, vendor ID, order date, shipping address, and all PO lines with item ID, quantity, and unit cost transfer. Completed or closed POs are not migrated as transactional documents; their receipt history is captured in GL instead.

BOS ERP GL lines are grouped into Acumatica GL Batch entries keyed by BOS ERP period or document date range. Each batch receives a descriptive BatchNbr and BatchDescription referencing the source BOS ERP period. Line details—account code, subaccount, debit/credit amount, description—map directly. This is the most complex mapping because BOS ERP individual lines must be assigned to a batch header before they can land in Acumatica.

BOS ERP user and employee owner records map to Acumatica Employee entities with email and department. Owner resolution for transactional records happens by email match against Acumatica user accounts. Any BOS ERP owner without a matching Acumatica user is flagged before migration and assigned to a fallback owner until your admin provisions the account.

BOS ERP custom fields and user-defined fields migrate to Acumatica as custom attributes on the corresponding screens (Customer, Vendor, StockItem, GL Account, etc.). Each field is assessed for its data type during discovery. Acumatica supports string, integer, decimal, date, boolean, and list attributes. Fields with unsupported types are flagged for post-migration manual entry or Acumatica custom development.

BOS ERP file attachments linked to customers, vendors, or inventory items are downloaded and re-uploaded to Acumatica's document management system. File size limits apply—Acumatica enforces a 25MB per-file default. We flag any file exceeding this limit before migration so your team can decide whether to split, compress, or archive it separately.

BOS ERP tax zones and tax agencies map to Acumatica Tax Zone and Tax Agency records. The tax zone ID, description, and rate for each jurisdiction transfer directly. Tax-exempt flags on customer and vendor records are preserved as Tax Zone assignments or TaxExemptID flags in Acumatica. We validate that all BOS ERP tax codes have a corresponding Acumatica tax zone before transactional migration runs.