Migrate from Everwin to Acumatica

Everwin Customer master maps to Acumatica Customer (BAccount + ARCustomer). The primary Everwin address becomes the default CRLocation record; additional Everwin address records create supplementary CRLocation rows. Customer class from Everwin maps to Acumatica Customer Class (ARContact.customerClass). Foreign-key dependencies on other Everwin entities are resolved before Customer migration begins.

Everwin Vendor master maps to Acumatica Vendor (BAccount + APVendor). Shipping and billing locations split into separate APLocation rows that precisely match Everwin's existing location records. Everwin vendor class maps to the APVendor.vendorClass field. Payment terms and tax category assignments on the Everwin Vendor record transfer to corresponding Acumatica fields during the transformation process.

Everwin contact records map to Acumatica Contact entities linked to the Customer parent via the BAccount relation. Email address, phone number, and job title copy directly to corresponding Acumatica Contact fields; additional Everwin contact attributes such as department or mobile phone become Contact.classID assignments or migrate as custom fields on the Contact DAC.

Everwin stock items map one-to-one to Acumatica InventoryItem records. Item type classification (stock/non-stock/service) maps directly to the InventoryItem.itemType enumeration field. Everwin's item class maps to InventoryItem.itemClass which governs posting rules and determines the correct COGS and Revenue account assignments. Warehouse-specific quantities transfer to INSiteStatus records linked by warehouse code.

Non-stock items and service items in Everwin map to Acumatica InventoryItem records with itemType set to Non-Stock or Service respectively. Purchasing settings from Everwin—including preferred vendor assignment and lead time—populate the VendorID and leadTime fields on the VendorID tab of the InventoryItem screen. Unit of measure conversions from Everwin transfer to the InventoryItem UOM settings.

Everwin AR documents map to Acumatica ARInvoice documents. Everwin document type (Invoice, Credit Memo, Debit Memo) maps to the ARTran.tranType field in Acumatica. Line items migrate to ARTran rows linked by InventoryID and branch ID; discount amounts migrate to ARTran.discPct.

Everwin AP documents map to Acumatica APInvoice documents. Everwin document type determines whether the record lands as APInvoice or APCreditMemo. Line items migrate to APTran rows with InventoryID and branch linkage; tax tracking on Everwin AP lines transforms into APTran taxCategoryId assignments in Acumatica. Hold status and approval flags from Everwin transfer to corresponding Acumatica document fields.

Open Everwin Sales Orders migrate to Acumatica SalesOrder with status = Open or Pending. Everwin order type maps to SOOrder.orderType in Acumatica; the SOOrderType configuration must exist before migration so order type assignment is valid. Shipments and invoices link via SOLine and SOLineSplit.

Open Everwin Purchase Orders migrate to Acumatica PurchaseOrder records. Everwin PO type maps to POOrder.orderType; POLine rows carry the linked InventoryID, branch ID, and unit cost from Everwin. POLineSplit records capture purchase-order shipment allocations in Acumatica's lot/serial split model. Expected and promised delivery dates from Everwin transfer to the Acumatica PO schedule fields.

Everwin GL accounts map directly to Acumatica Account records. Account number and name copy from Everwin to Acumatica without transformation. Active or inactive status maps to the Account.active Boolean field. Everwin account type classifications—Asset, Liability, Income, Expense, and Owner Equity—map to the corresponding Account.type enumeration values in Acumatica's chart of accounts structure.

Everwin user-defined dimension codes map to Acumatica subaccount segments. Each unique Everwin dimension value becomes a Subaccount record with the correct segment ID. Acumatica requires the Subaccount screen to be pre-configured with the same number of segments before migration runs.

Acumatica fiscal periods must be created in the FinPeriod screen before transactional migration begins. Everwin fiscal year starts and period lengths are documented from the source schema and replicated in Acumatica. Open and closed period flags are set per period.

Everwin tax codes map to Acumatica TaxZone records linked to TaxCategory entries. Each unique Everwin tax code becomes a TaxCategory record; TaxZone associations are built by matching the Everwin customer tax zone or state province designation to Acumatica's tax zone configuration. Tax rates from Everwin transfer to TaxRev records linked to each TaxCategory.

Everwin payment terms such as Net 30, Net 60, and End of Month (EOM) map to Acumatica Terms records. The Terms entity must be created in Acumatica before customer and vendor masters migrate so the TermsID foreign key resolves successfully on first import. Discount percentages and due day calculations from Everwin transfer to the corresponding Terms detail fields.

Everwin user-defined fields migrate as Acumatica custom fields on the corresponding DAC. Field names receive the Usr prefix per Acumatica convention. Field type mapping: Everwin text → Acumatica string; Everwin numeric → Acumatica decimal or integer; Everwin date → Acumatica date; Everwin pick-list → Acumatica PXString or PXInt with value list.