Migrate from Iptor ERP to Acumatica

Iptor customers map directly to Acumatica Business Accounts. The primary address, contact name, email, and phone from Iptor's BP contact subrecord become the Business Account's default address and contact information. Additional BP contact rows map to secondary contact records in Acumatica linked by the same account ID.

Iptor suppliers are mapped directly to Acumatica Vendors in the Payables module. The supplier's primary address and contact details transfer as the vendor's default address and contact information. Remit-to addresses from Iptor's supplier records populate the corresponding vendor remit-to fields in Acumatica. Payment terms codes from Iptor are translated to Acumatica Terms IDs through a lookup table, ensuring consistent payment schedules carry forward without manual reconfiguration.

Iptor Items with stock control flag map to Acumatica Stock Items; non-stocked items map to Non-Stock Items. Item classification codes from Iptor become Item Classes in Acumatica, which drive default posting settings and tax categories. Unit of measure from Iptor maps to Acumatica's UOM definitions per item.

Iptor's item classification hierarchy (multi-level codes like CAT-A-001) maps to Acumatica's Item Class structure. Where Iptor uses a single hierarchy for both purchasing and sales classification, Acumatica may require separate Item Classes for purchasing group and sales category — we surface this in the mapping plan.

Iptor Sales Order headers map to Acumatica Sales Orders — order number, order date, customer reference, and payment terms transfer directly. Order lines map with line type determined by item type (Stock, Non-Stock, or Miscellaneous). Warehouse assignment on each line maps to the Acumatica warehouse ID.

Iptor Purchase Orders map directly to Acumatica Purchase Orders with all header information preserved — including vendor reference, order date, payment terms, and shipping instructions. Line items transfer with their quantities, unit costs, and extended amounts. The line-type determination mirrors the sales order logic: items flagged as stocked in Iptor become Stock line types in Acumatica, while non-stocked items use the Miscellaneous line type. This ensures proper inventory impact and purchasing workflows in Acumatica's receiving process.

Iptor shipments that are linked to sales orders map to Acumatica Shipment documents, which are generated from the related Sales Order in Acumatica's fulfillment workflow. The warehouse code from the Iptor shipment determines the Acumatica warehouse location used for picking, packing, and shipment confirmation. Shipment status, carrier information, and tracking references from Iptor transfer to corresponding fields in the Acumatica shipment record to maintain complete fulfillment history.

Iptor AR invoices map to Acumatica Sales Invoices. Invoice number, date, customer, and line amounts transfer directly. Tax calculation in Acumatica uses the tax zone assigned to the customer and item class — we apply Iptor's tax code mapping as the basis for this assignment.

Iptor AP bills map to Acumatica Bills in the Purchases module with full header and line preservation. The vendor reference, invoice number, invoice date, and due date transfer directly to corresponding Acumatica Bill fields. Line amounts, expense categories, and distribution percentages from Iptor's expense allocation grid map to the Acumatica Bill's expense allocation grid, ensuring accurate cost center assignment in the general ledger.

Iptor customer payment receipts map to Acumatica Payments applied to open AR invoices. Payment method and reference number transfer; where Iptor tracks partial payments as separate records, Acumatica's application logic links each payment to its corresponding invoice by document number.

Iptor AP payments — including checks and electronic payment records — map to Acumatica Checks and Payments applied to open AP bills in the Payables module. Payment method, check number, payment date, and vendor reference information transfer directly. Where Iptor recorded voided payments, that logic carries forward as payment reversals in Acumatica, maintaining the complete payment history trail and ensuring accurate cash forecasting.

Iptor warehouse codes and location addresses map to Acumatica Warehouse records. Each Iptor warehouse-location bin maps to Acumatica's Location within the warehouse using the same bin code. Floor location hierarchy in Iptor translates to the Location's label structure in Acumatica.

Iptor item stock levels per warehouse become Acumatica Item Site records — one per item-warehouse combination. Current on-hand quantity, allocated quantity, and available quantity from Iptor map to the corresponding Item Site fields. Acumatica calculates availability dynamically from these seeded values.

Iptor's account codes and segment structure map to Acumatica's GL account number and Subaccount dimensions. Where Iptor uses multi-segment account codes (e.g., 4-5000-01), Acumatica splits these into the account number plus a Subaccount segment — we assign one segment to the account number and remaining segments to a configurable subaccount scheme.

Iptor manual journal entries and system-generated GL transactions map to Acumatica Journal Transactions. Debit and credit amounts, account assignments, and posting dates transfer. Iptor's batch and entry number references are preserved as reference fields in Acumatica's journal record.

Iptor EDI transaction definitions — including ANSI X12 standards such as 810 invoices, 850 purchase orders, and 856 advance ship notices — have no direct equivalent in Acumatica's core ERP platform. These EDI transaction sets require implementation through Acumatica's native EDI framework or a third-party EDI connector following migration completion. We provide comprehensive EDI mapping documentation and value tables for your integration team to reference when rebuilding these connections in the target system.

Iptor workflow definitions for document approval, escalation rules, and conditional routing do not transfer to Acumatica. We export the workflow name, step sequence, and condition logic as a reference document. Acumatica's screen automation or REST API-based automation must be designed by your team post-migration.

Iptor's batch and serial tracking codes for lot-controlled items map to Acumatica's Lot Class and Lot Number assignments within the inventory management module. Each Iptor lot record — including lot number, expiry date, quantity on hand, and supplier lot reference — becomes an Acumatica Lot/Serial Number record linked to the corresponding item and warehouse location. This ensures full traceability throughout the supply chain.

Iptor customer-specific pricing and volume discount rules map to Acumatica Customer Price Classes linked to Price Lists. Iptor's quantity-break pricing tiers become Acumatica's price rule quantity breaks. Where Iptor stores inline price overrides on orders, those values seed the Acumatica unit price field directly.

Iptor sales territories and region codes map to Acumatica Branches for organizational reporting and segmentation purposes. The Acumatica Branch structure enables geographic or divisional financial reporting across your organization. The original Iptor territory code is preserved in a custom field (UsrSourceTerritory__c) on Business Account records to maintain historical reference and ensure continuity in sales performance reporting after migration.

Iptor user-defined fields attached to any standard table require migration to Acumatica's custom field extension framework — each Iptor field becomes a Usr-prefixed field on the corresponding Acumatica Data Access Class (DAC). We deliver a comprehensive field extension plan documenting the target DAC, recommended field type, default value logic, and any pick-list or validation rules that must be configured in Acumatica's Customization Project editor before data loads can populate those fields with values.

Iptor document attachments (PDFs, images, linked files) on orders, invoices, and items migrate to Acumatica's Files entity attached to the corresponding record. File name and original upload date are preserved; Acumatica's 25MB per-file limit applies for large attachments.