Migrate from ECOUNT ERP to Acumatica

ECOUNT stores address fields embedded in the customer record. Acumatica requires a separate Address record linked by ContactID to the Customer record. We split address data into the Address table (AddressLine1, AddressLine2, City, State, PostalCode, Country) and load the Customer record with a reference to that AddressID. If ECOUNT holds multiple ship-to addresses per customer, each becomes a separate Acumatica Address record with its own AddressID.

ECOUNT customer type values map to Acumatica Customer Class records created before migration. Each Customer Class controls default terms, tax settings, and the reporting group. We inventory all ECOUNT customer type values, create matching Customer Class records in Acumatica, and load ClassID on every customer during migration.

Mirrors the customer address split pattern. ECOUNT vendor address fields land in Acumatica's separate Address record linked by ContactID to the Vendor record, preserving AddressLine1, AddressLine2, City, State, PostalCode, and Country. Multi-address vendors such as remit-to versus ship-from each receive their own Address record with the appropriate address purpose code, ensuring that AR/AP documents and purchase transactions pull the correct shipping or payment location automatically.

ECOUNT vendor type values create corresponding Acumatica Vendor Class records before migration. Vendor Class defaults payment terms, tax settings, and GL accounts for AP postings. We map each ECOUNT vendor type value to a Vendor Class ID so vendor ledger entries post to the correct accounts automatically.

ECOUNT item types (finished goods, raw materials, trading goods) translate to Acumatica Item Type values (Stock, Non-Stock, Service, Charge). The Acumatica Item Class controls valuation method (Standard, Average, FIFO), posting settings, and default warehouse. We map ECOUNT item type to the correct Acumatica Item Type and assign an Item Class based on ECOUNT's product category field.

ECOUNT production items with BOM structures load into Acumatica's BOM version attached to the finished goods item. Each BOM line references a component item and quantity per unit. Acumatica BOMs require a bill status of Active and an Effective Date — we use the ECOUNT BOM creation date as the effective date.

ECOUNT warehouse-specific data (safety stock, reorder point, default warehouse) migrates to Acumatica Item Warehouse records — one per item per warehouse. Acumatica requires the warehouse to exist before item warehouse records can be created, so warehouse master data loads before items.

ECOUNT contact persons linked to a customer map to Acumatica Contact records with the CustomerID as the parent. The Contact record holds Title, Department, Phone1, Fax, Email, and a Primary Contact flag. For records where ECOUNT marks one contact as the primary, we set IsPrimaryContact = true in Acumatica.

ECOUNT sales slips map to Acumatica Sales Order documents. Each line carries the InventoryID, UOM, quantity, unit price, and warehouse. The CustomerID and ShippingAddress reference the loaded Customer and Address records. OrderNbr and OrderDate preserve the original numbering and dates.

ECOUNT purchase slips migrate to Acumatica Purchase Orders. VendorID, Location, and line items (InventoryID, UOM, quantity, unit cost, warehouse) carry forward, preserving the original order number and date. Each PO line is linked to a GL distribution account from the Vendor Class, and any ECOUNT tax or freight data maps to Acumatica purchase order extensions, ensuring PO status, approval workflow, and posting behavior match your vendor terms.

ECOUNT account codes and descriptions load directly into Acumatica Account records with AccountCD and Description. We map ECOUNT account type (asset, liability, equity, income, expense) to Acumatica Account Type. If ECOUNT uses consolidation accounts, these map to Acumatica Consolidation Account records linked by ConsolidationCode.

Acumatica maintains financial periods in the Master Financial Calendar (GL > Master Financial Calendar). We load ECOUNT fiscal periods into Acumatica's period table before any GL or AP/AR data arrives. Historical periods with actual balances migrate with year-beginning opening balances if year-end closes are needed.

ECOUNT input screen custom fields and calculation formulas on customers, vendors, items, and orders migrate to Acumatica custom fields registered via the Customization Project editor (Customization > Customize Screen). We create each custom field with the matching data type (string, number, date, picklist) before loading the values into the appropriate screen.

ECOUNT approval workflows and sequence-based routing do not have an equivalent in Acumatica's data model. We export ECOUNT workflow definitions as a configuration reference document so your Acumatica partner can rebuild the logic using Acumatica's screen-level approval workflow engine or the Automation Schedule.