Migrate from LOGIC ERP to Acumatica

LOGIC ERP customers map 1:1 to Acumatica Customer records. Acumatica requires a CustomerClassId assignment—so we apply a default class and flag it for your admin to refine. Customer-level addresses and contacts attach via the Contact object linked by CustomerID. Custom address fields can be stored as extended attributes if required.

LOGIC ERP vendors map to Acumatica Vendor records. The VendorClassId is assigned a default value; your team configures the class taxonomy post-migration. Primary contact information transfers to the Vendor-Contact relationship table. Custom vendor attributes such as tax IDs or payment methods are preserved as extended attributes if they exist.

LOGIC ERP item type determines the Acumatica item class: Stock items become Stock Items, Non-Stock items become Non-Stock Items, and Service items use the Service item class. Item status (Active/Inactive) maps to Acumatica's ItemStatus field. We preserve all item attributes as DAC custom attributes.

LOGIC ERP sales orders map to Acumatica Sales Orders with OrderType, customer reference, line items, amounts, dates, and status. Acumatica's order types (SO, Invoice, Credit Memo) must be configured before migration; we assign a default type and provide a mapping plan.

Purchase orders transfer as Acumatica Purchase Orders with vendor reference, line items, amounts, expected dates, and status. Status values transform per LOGIC ERP-to-Acumatica status mapping rules documented in the field-level plan. The mapping also preserves the purchase order number, ensures the correct vendor account is linked, and retains any internal notes or attachments. Custom fields on the PO are transferred as DAC attributes after they are defined in Acumatica.

LOGIC ERP chart of accounts transfers to Acumatica GL accounts. The account code, name, type, and sub-account dimension structure map directly. Active/inactive status preserves on the Account record. Sub-account segments require Acumatica sub-account dimension configuration before load. If your LOGIC ERP uses detailed cost center codes, they can be mapped to Acumatica sub-account segments using a custom dimension. Any inactive accounts are flagged and can be activated post-migration after review.

LOGIC ERP warehouse codes and bin locations map to Acumatica Site (warehouse) and LocationID (bin) records. Each LOGIC ERP location becomes an Acumatica LocationID under its parent Site. Inventory balances transfer as opening quantities linked to the correct Site and LocationID.

LOGIC ERP POS receipts require custom transformation because Acumatica has no native POS entity. Each receipt header becomes an Acumatica Sales Order or AR Invoice; receipt line items become order/invoice lines; customer reference, item reference, and payment method transfer as notes or custom fields. This step requires bespoke mapping logic and is flagged for advance validation.

LOGIC ERP payment term codes (Net 30, Net 60, etc.) map to Acumatica PaymentTerm records by code match. If LOGIC ERP uses custom term descriptions, we create the corresponding PaymentTerm in Acumatica before mapping the field. The mapping also includes the due days, discount percentages, and installment schedules where applicable. Any variations in term naming are normalized to match Acumatica's standard PaymentTerm format.

LOGIC ERP custom fields that do not map to a standard Acumatica field require pre-creation as DAC attribute extensions in the Acumatica customization project. FlitStack delivers an attribute creation plan listing each custom field, its data type, and the target DAC entity, so your Acumatica admin publishes the customization before the data migration runs.