Migrate from EBMS to Acumatica

EBMS customer records map to Acumatica Customer DAC directly. EBMS stores company name, primary contact, billing address, and payment terms in a single record. Acumatica requires the Customer record plus at least one Location record — we extract the primary address from EBMS and create it as the default Location. EBMS customer class codes map to Acumatica Customer class via a value-mapping table before insert.

EBMS contact records attached to a customer map to Acumatica Contact under the corresponding Location. The first EBMS contact for a customer becomes the Location's DefaultContact. Additional contacts are created under the same Location. EBMS contact phone and email fields map to Acumatica Contact.Phone1 and Contact.Email fields. If EBMS stores a contact title, it maps to Contact.Title.

EBMS vendor master maps to Acumatica Vendor directly. Acumatica requires a Vendor record plus at least one Location — EBMS vendor address and payment terms are extracted and used to create the default VendorLocation. EBMS vendor terms (Net-30, etc.) map to Acumatica TermsID lookup. Vendor class codes are value-mapped to Acumatica VendorClass records if they exist.

EBMS inventory items (stock and non-stock) map to Acumatica InventoryItem DAC. EBMS item type (Stock/Non-Stock/Service) maps to Acumatica's itemType field (ST, NS, SR). EBMS item description, base unit, and cost roll up into Acumatica's Description, BaseUnit, and last cost fields. EBMS item class maps to Acumatica ItemClass via value mapping.

EBMS sales orders map to Acumatica SalesOrder documents. The EBMS order header (customer, order date, warehouse, terms) becomes the SalesOrder header. EBMS line items (product, quantity, price) map to SalesOrderDetails with inventory ID lookups. EBMS order status (Open/Closed) maps to Acumatica status (Open, Pending, Completed, Cancelled). Original order dates are preserved in the TranDate field.

EBMS AR invoices map to Acumatica ARInvoice documents. EBMS invoice header (customer, invoice date, due date, amount) becomes the ARInvoice header. EBMS line items become ARInvoiceDetails. EBMS invoice payments are mapped to Payments applied to the ARInvoice. Unpaid EBMS invoices import as Open AR invoices in Acumatica.

EBMS AP bills map to Acumatica APBill documents. EBMS vendor, bill date, due date, and amount map to APBill header fields. EBMS line items become APBillDetails. EBMS bill payments are mapped to Payments applied to the APBill. Unpaid EBMS bills import as Open AP documents.

EBMS chart of accounts maps to Acumatica Account records. EBMS account numbers map to Account.AccountCD. EBMS account descriptions map to Account.Description. Account type (Asset, Liability, Equity, Income, Expense) maps to Acumatica Account.Type. Active/inactive status is preserved from EBMS.

EBMS uses a flat Department/Class field on transactions. Acumatica uses multi-segment Subaccounts. If EBMS uses a single dimension, it maps to the first active Acumatica SubaccountSegment. Multi-dimension EBMS structures require a custom mapping plan developed with your Acumatica admin before migration — we provide a SubaccountSegmentationPlan as a deliverable.

EBMS warehouses or locations map to Acumatica Warehouse records. EBMS warehouse code and name map to Warehouse.WarehouseCD and Warehouse.Descr. Acumatica requires at least one active Warehouse — if EBMS has a single default warehouse, it becomes the primary Warehouse record and the Acumatica Branch is assigned accordingly.

EBMS employee records map to Acumatica Employee DAC. Employee name, email, department, and status map to Employee.AcctName, Employee.Email, Employee.DeptID, and Employee.Status. Owner resolution during migration matches EBMS employee IDs to Acumatica Employee records by email for transactional ownership assignment.

EBMS custom tables created via the Customization Designer do not have a direct Acumatica equivalent. We extract the EBMS custom table schema and data, then create a corresponding Acumatica Usr-prefixed DAC extension. The EBMS custom table records are loaded into the new Acumatica table via bulk insert. If the EBMS custom table has foreign keys to EBMS master records, those are resolved to Acumatica record IDs before insert.

EBMS user-defined fields (UDFs) attached to Customer, Vendor, or Sales Order documents map to Acumatica Usr-prefixed custom fields. We extract the EBMS UDF schema (field name, data type, pick-list values), create the corresponding Acumatica field on the appropriate DAC, and migrate the values. Pick-list UDFs require value-by-value mapping if the source values differ from Acumatica's target pick-list.