Migrate from Acumatica to Infor CloudSuite Corporate

Acumatica Business Account records map to Infor CloudSuite Customer. The primary contact, billing address, and shipping address on the Business Account become Customer contact records and address records in Infor. Business Account classification (Customer vs Prospect vs CustomerAndProspect) maps to Infor Customer Type. We resolve the Acumatica CompanyID tenant filter during extraction and map customer records to the appropriate Infor operating unit. Custom fields on Business Account (UDFs stored in extension DACs under the custom namespace) map to Infor custom fields via the Migration Utility column rules.

Acumatica Vendor records map to Infor CloudSuite Supplier. AP settings, tax settings, and payment terms migrate as Supplier configuration records. The vendor's main address and contact information map to Supplier address records. We handle the distinction between Acumatica Vendors used for purchasing only versus those also used as customers by splitting into Supplier records (and optionally Customer records if the same entity appears in both roles). Vendor UDFs are discovered via the Acumatica entity schema endpoint and mapped to Infor custom supplier fields.

Acumatica Inventory Items map to Infor CloudSuite Item Master with Stock Item, Non-Stock Item, or Service Item type preserved. Item categories, units of measure, and stock item attributes (class, type, lot/serial settings) migrate through the Infor Migration Utility with predefined Item Master sequences. Warehouse-specific quantity and availability data (AvailabilityQty) are derived system fields in Acumatica and are not carried as static values; we migrate the current on-hand quantities by warehouse as Infor inventory transactions or on-hand records. Multi-warehouse configurations map to Infor sites with location-specific stocking.

Acumatica GL Account records (account class, type, subaccount mask, active/inactive status) map to Infor CloudSuite GL Account with account structure and subaccount segmentation preserved. The Acumatica account hierarchy and rollup structure map to Infor's account hierarchy and consolidation structure. We handle the subaccount mask configuration carefully because Infor's account dimension structure can differ from Acumatica's flexible subaccount framework. Active/inactive status determines whether the account is available for posting in Infor.

Acumatica Project records with associated budgets, tasks, employees, and change orders map to Infor CloudSuite Project. The project hierarchy and task structure migrate with parent-child relationships preserved. Project attributes, custom fields, and change order history require explicit field-level mapping. We extract project-linked transactions separately and map them to Infor project cost transactions or commitment records depending on the Infor product (Industrial vs Distribution). Project status (Active, Completed, Cancelled) migrates directly.

Acumatica Sales Orders map to Infor CloudSuite Sales Orders with line items, fulfillment details, and invoice links preserved. Document status (Quote, Order, Fulfilled, Invoiced, Cancelled) maps to Infor Sales Order status with order type and processing workflow preserved. Tax calculation in Acumatica depends on customer and item tax settings; Infor interprets these through its own tax engine, so we flag the tax category mapping requirement for the customer's tax team to configure in Infor before go-live. Open orders migrate with status preserved for reactivation in Infor.

Acumatica Purchase Orders map to Infor CloudSuite Purchase Orders with vendor, line items, receipts, and amendments. The PO lifecycle (Draft, Pending Approval, Open, Closed, Cancelled) maps to Infor PO status. Receipts and amendments in Acumatica have separate schemas and migrate as related Infor records (goods receipt and PO revision). We handle the distinction between standard POs and blanket POs by mapping to the corresponding Infor order types. Vendor lead times and delivery schedules from Acumatica migrate as Infor schedule lines.

Acumatica AR/AP Invoices map to Infor CloudSuite Accounts Receivable and Accounts Payable transactions. Open invoices carry payment schedules, terms, and aging data; we preserve the payment term reference and aging bucket assignments. Historical invoices that reference balance tables require careful sequencing because Infor's GL posting depends on the account structure being fully migrated before transaction loading. Closed invoices with full history are typically migrated for audit and reporting purposes rather than for re-processing.

Acumatica Warehouse records with bin structures map to Infor CloudSuite Sites with location definitions and bin configurations. Multi-warehouse configurations in Acumatica map to multiple Infor sites within the same operating unit or across separate operating units depending on the customer's organizational structure. We map warehouse assignments on inventory items to Infor site-stock relationships. Transfer orders between warehouses in Acumatica map to Infor inter-site transfer orders.

Acumatica Employee records with compensation history, department assignments, and timecard data map to Infor CloudSuite Worker records. Employment status, job titles, and earning codes migrate directly. Effective-dated rows (compensation changes, department transfers) migrate as separate historical records with their effective dates preserved. We resolve the department reference from Acumatica to the corresponding Infor cost center or organizational unit. Worker assignments to projects and warehouses carry over as Infor labor assignments.

Acumatica Note text stored in the Note table with entity references (EntityID + EntityType) and binary attachments in NoteDoc map to Infor CloudSuite Document Management. We extract note content, the related entity reference, and file binaries separately, then re-link them in Infor as document records attached to the appropriate entity (Customer, Supplier, Item, Project, Order). If the Infor destination uses a different document attachment model, we fall back to embedding note text as an Infor custom field and files as record attachments. The migration utility's prerequisite sequencing ensures entity records exist before attachment links are created.

Acumatica tax setup (categories, zones, and rules) does not migrate directly because Infor CloudSuite has its own tax engine with different configuration semantics. We deliver a written tax mapping document that identifies every Acumatica tax category and zone in use, maps each to the nearest Infor tax configuration equivalent, and flags tax jurisdictions requiring manual Infor setup. The customer's tax team or Infor consultant rebuilds the tax engine configuration in Infor before go-live. This is explicitly a configuration handoff, not an automated data migration.