Migrate from Infor CloudSuite Corporate to Acumatica

Infor Company maps 1:1 to Acumatica Customer. Address, phone, and tax registration data transfer as Contact information subtab fields. Infor's multi-company hierarchy (parent/child) maps to Acumatica's parent Customer relationship. CustomerClass in Acumatica is assigned based on Infor's industry code or customer type field.

Infor Companies marked as suppliers in Infor extract to Acumatica Vendor records. A Company used in both contexts (customer and vendor) splits into both a Customer and a Vendor record, linked by the original Infor company ID preserved in Source_System_ID__c on each record.

Infor Contact maps to Acumatica Contact under the corresponding Customer or Vendor. Name, email, phone, job title, and address fields transfer directly. Infor's contact association to multiple companies collapses to the primary Company link in Acumatica, with secondary links handled via the Relations subtab.

Infor Product records map to Acumatica InventoryItem. ItemCode, Description, BaseUnit, and standard cost transfer directly. Stock items and non-stock items are differentiated by Infor's item type flag mapping to Acumatica's ItemType (Stock Item, Non-Stock Item, Labor). Warehouse-specific quantities map to Acumatica's INSiteLotSerial nnn tables per branch.

Infor Sales Order maps to Acumatica SOOrder with all line items as SOLine records. Order number, order date, customer reference, quantities, unit prices, and line totals transfer. Order status (Open, Completed, Cancelled) maps to Acumatica's SOOrder status field. Branch ID on each SOOrder is set from the Infor site code mapping established during branch configuration.

Infor Purchase Order maps to Acumatica POOrder with POLine records. Vendor reference, PO number, order date, and line details transfer. Expected and received quantities update Acumatica's POReceipt linked records. Branch ID derives from the Infor operating unit mapped during site-to-branch configuration.

Infor GL Chart of Accounts maps to Acumatica Account (GL Accounts screen). Account code, name, and account type (Asset, Liability, Revenue, Expense) transfer. Subaccount segments in Infor map to Acumatica's Subaccount dimension, configured in the Chart of Accounts screen with segment masking. GL account type mapping must be validated by a CPA before migration commits.

Infor AR Invoice records map to Acumatica ARInvoice (Accounts Receivable > Invoices > Data Entry). Invoice number, date, due date, customer reference, line amounts, and tax amounts transfer. Open invoices link to the Customer record; paid invoices carry a reference to the Payment record. Original Infor invoice ID is preserved in the invoice reference field for traceability.

Infor AP Invoice records map to Acumatica APInvoice (Accounts Payable > Invoices > Data Entry). Vendor reference, invoice number, date, due date, line amounts, and tax amounts transfer. Prepayments and credit memos map to APAdjustments linked to the invoice. Historical AP invoices are loaded as read-only records; open AP invoices can be paid through Acumatica's payment processing.

Infor GL Journal Entry records map to Acumatica JournalTransaction (General Ledger > Journal Transactions > Data Entry). Batch number, entry date, description, and all debit/credit lines with Account and Subaccount references transfer. Each line's amount, reference, and notes field are preserved. Historical closed periods are migrated as read-only entries to preserve audit trail continuity.

Infor Project records map to Acumatica PMProject (Project Management > Projects > Project Summary). Project ID, name, status, start and end dates, customer link, and budget amounts transfer. Change orders and project tasks map to Acumatica's Change Orders and Task entries under the project. Non-billable time tracking from Infor maps to ProjectTask with EmployeeTime records in Acumatica.

Infor users and owner IDs resolve by email match against Acumatica users. Unmatched Infor users are flagged before migration; the client either invites them to Acumatica first or assigns records to a fallback owner. Infor's role-based security model does not map directly to Acumatica's rights group model and must be reconfigured post-migration by the Acumatica administrator.

Infor document attachments on records (quotes, orders, invoices, items) are exported from Infor Document Management, re-uploaded to Acumatica's file storage linked to the corresponding record. File size limits and inline image handling follow Acumatica's attachment configuration. Large format files stored outside Infor's database are downloaded and rehosted during the migration window.

Infor custom fields defined in CMS470 (alphanumeric, numeric, or date type) and attached via custom field groups to items, suppliers, or purchase agreements require pre-creation of corresponding Acumatica custom fields via the Customization Editor before data loads. Field code, description, and data type are mapped; pick-list values in Infor migrate as Acumatica predefined list values on the custom field.

Infor CloudSuite workflows and automations built in Infor Ming.le, ION, or process designer have no direct Acumatica equivalent and do not migrate. FlitStack exports the workflow definitions as configuration documentation for the Acumatica team to rebuild using Acumatica's Generic Inquiries, Business Events, and Automation Schedules. All migrated data remains fully functional without workflows — business processes can continue in read-only mode while the Acumatica automation layer is rebuilt.