Migrate from AI Works to Infor CloudSuite Corporate

AI Works Users map to Infor CloudSuite User records. We extract by email address as the dedupe key, mapping role assignments and site associations to Infor's security model. Infor CloudSuite requires that all Users referenced as transaction owners exist before transactional data imports; we run the User phase first and emit a reconciliation report for any AI Works user without a matching Infor User, which the customer's Infor admin provisions before proceeding.

AI Works Accounts may serve as both customers (for sales orders and invoices) and suppliers (for purchase orders and vouchers). We split during extraction using the AI Works account_type or classification field, writing customer accounts to Infor Customer records and supplier accounts to Infor Supplier records. Address, contact, and tax registration data map to Infor's address book structure. Accounts without a classification flag go to a reconciliation queue for manual assignment.

AI Works Invoices of direction AR (accounts receivable) map to Infor CloudSuite AR Invoice records; invoices of direction AP (accounts payable) map to AP Voucher records. We require all transactions to be posted in AI Works before extraction; open, unposted invoices must be completed or voided in AI Works before the migration database is finalized. Historical invoice line items map to Invoice Detail lines with product, quantity, unit price, and tax code preserved.

AI Works Purchase Orders map to Infor CloudSuite Purchase Order records. Open POs (not yet received) migrate with status Open and full line detail. Closed, received, or cancelled POs migrate as history records. PO approval workflow status from AI Works is preserved in a custom field for the customer's Infor consultant to re-establish in Infor OS approval routing.

AI Works custom fields on any standard object map to Infor CloudSuite equivalent custom fields where a direct type mapping exists (text to String, number to Decimal, date to Date, picklist to Dropdown). Fields without a direct Infor type map to an Infor extension table with a foreign key relationship, and we document the extension table schema for the customer's admin to configure in Infor CloudSuite Configuration. AI Works ExtGen stored procedure logic that computed custom field values does not migrate; we deliver a written description of each ExtGen calculation for Mongoose-based replacement.

AI Works Product or Item master records map to Infor CloudSuite Item. We map item number, description, unit of measure, cost, and price from the AI Works product record. Inventory valuation method (FIFO, Average, Standard) maps to Infor's costing method field. Bills of Materials from AI Works map to Infor CloudSuite BOM records with revision and routing associations.

AI Works inventory transactions (receipts, issues, adjustments, transfers) map to Infor CloudSuite Inventory Transaction records. We migrate open transactions (not yet posted) as pending entries and closed transactions as history. Warehouse and location references from AI Works map to Infor Site and Warehouse codes, requiring a warehouse code mapping table to be validated before inventory transaction import.

AI Works journal entries map to Infor CloudSuite G/L Journal entries with header and line detail. Account code mapping from AI Works chart of accounts to Infor chart of accounts is required; we build the account cross-reference table during discovery. Journal entry date, description, debit/credit amounts, and dimension segments (department, cost center, project) transfer directly where the dimension structure is equivalent.

AI Works approval chains (purchase order approvals, invoice approval workflows) are automation configurations that do not migrate to Infor OS. We extract the approval chain structure (approvers, thresholds, escalation rules) from AI Works configuration and deliver it as a written document that the customer's Infor consultant uses to rebuild equivalent Infor OS approval routing. Approval history (who approved what, when) migrates as audit records on the respective transaction.

AI Works reports and dashboards are custom configurations that do not migrate as code. We deliver a written inventory of every active AI Works report (name, owner, filters, schedule) and dashboard for the customer's Infor consultant to rebuild using Infor's reporting tools or Birst. Custom SQL-based reports in AI Works require additional scoping to determine whether an Infor dataview or Birst equivalent is appropriate.

AI Works tax codes and tax rate configurations do not migrate programmatically because Infor CloudSuite requires tax authorities, tax codes, and tax schedules to be entered through Infor forms. We extract the AI Works tax code list and rates as a reference spreadsheet, and the customer's Infor consultant enters equivalent tax setup in Infor CloudSuite before transactional migration begins.