Migrate from Achiever Technology to Acumatica

Achiever Technology Customer records map to Acumatica BAccount with Type='C'. The primary contact name, email, phone, and billing address move into BAccount's Name, Email, Phone, and Address fields. If Achiever Technology stores a separate ship-to address, it creates a separate Location record under the same BAccount with a distinct LocationCD.

Vendor records map to Acumatica BAccount with Type='V'. The vendor's tax registration number, payment terms, and default currency pull into BAccount's Tax Registration ID, TermsID, and CuryID fields respectively. PO land in Acumatica's POOrder table keyed to the vendor's BAccountID.

Achiever Technology contacts that exist without a primary company require a placeholder BAccount (Type='C', Name='Unassigned') created first so Acumatica's Contact.BAccountID foreign key resolves. Contact duplicates under multiple companies in Achiever Technology surface as separate Contact records each pointing to their respective BAccount, because Acumatica Contact is 1:N with BAccount rather than N:N.

Stock items in Achiever Technology map to Acumatica InventoryItem with ItemType='Stock'. Non-stock items map to ItemType='Non-Stock'. The item's description, base unit of measure, and last purchase cost transfer to Descr, BaseUnit, and LastCost respectively. Item class assignments in Achiever Technology become INItemClass records in Acumatica.

Achiever Technology warehouse records create Acumatica INSite entries (one per warehouse). If Achiever Technology tracks bin or shelf locations within a warehouse, those become INLocation records under the corresponding INSite, allowing lot/serial assignments to resolve to a specific warehouse slot.

Open sales orders migrate to Acumatica SOOrder with status='Open' and the original order date preserved in SOOrder.OrderDate. Each order line becomes an SOLine with InventoryID, OrderQty, and Acumatica's branch/warehouse assignment derived from Achiever Technology's fulfillment location field. Achiever Technology stores the fulfillment warehouse or location code on each sales order header; this value maps to the Acumatica SOOrder.BranchID and SOLine.SiteID fields during migration. If Achiever Technology tracks multiple ship-to addresses per order, the additional addresses create separate Location records under the customer BAccount, linked to the corresponding SOLine via the shipment detail.

Open purchase orders map to Acumatica POOrder with status='Open'. Vendor is resolved via BAccountID lookup on the vendor name. POLine carries the InventoryID, POOrderQty, and Acumatica's branch/warehouse for receipt posting. Achiever Technology vendor codes map to the Acumatica BAccount.AcctCD field, and the POOrder.VendorID references the resolved BAccountID. POLine also inherits the Acumatica warehouse from the POOrder.VendorLocation or from Achiever Technology's default receiving location if one exists.

Achiever Technology invoices that are unpaid carry to Acumatica as ARInvoice with DocType='Invoice'. The customer resolves via BAccountID, the invoice number maps to RefNbr, and the outstanding amount becomes DocBal. Paid invoices migrate as ARInvoice with DocType='Payment' if you elect to carry forward payment history; otherwise they are summarized.

Unpaid vendor bills carry to Acumatica as APInvoice with DocType='Invoice', linked to the vendor BAccountID. Historical AP invoices beyond the 2-year window are summarized and the outstanding balance carries as an AP adjustment. The APInvoice.RefNbr preserves Achiever Technology's original invoice number for audit trails, and DocBal reflects the open amount at migration cutoff. Invoices older than the historical window consolidate into a single APAdjustment record per vendor to maintain the outstanding balance without bloating the transaction table.

Achiever Technology GL account codes and descriptions map to Acumatica Account records. Account.CashAccount flag, Account.Type (Asset/Liability/Income/Expense), and Account.SubaccountMask are set based on the account's role in Achiever Technology's trial balance. The CashAccount flag is set to true for accounts used in bank reconciliation or cash-on-hand tracking, while the Type field classifies accounts by their financial statement role. Achiever Technology's account code structure is preserved in Account.AcctCD, and subaccounts are created using the SubaccountMask to match Achiever Technology's natural account hierarchy.

If Achiever Technology tracks lot numbers for FIFO inventory valuation, those migrate as INLotSerial records keyed to InventoryID and INSite. Each in/out movement from Achiever Technology's stock ledger creates an INTran record preserving the lot assignment, movement date, qty, and cost at time of movement.

Achiever Technology custom fields on any entity become Acumatica Usr-prefixed custom properties (e.g., UsrOriginatingSystemID__c). The data type is preserved — text, number, date, or pick-list — and a Customization Project Editor package is generated to deploy the schema into the Acumatica tenant before data loads begin.