Migrate from Access ERP to Infor CloudSuite Corporate

Access ERP nominal ledger codes with cost centre and department coding map to Infor Cloudsuite's Accounting Structure. We extract the full account code, account name, account type (asset, liability, income, expense), and the cost centre and department hierarchies. In CloudSuite, these map to the Account master within Infor Financials, with the fiscal year and legal entity structure configured before account import. Multi-currency account settings from Access ERP carry to the Accounting Structure currency definition.

Access ERP customer records with address books, payment terms, credit limits, and tax codes map to Infor Cloudsuite Business Partner records with the Customer role active. The customer account code from Access ERP becomes the Business Partner ID; the customer name and address fields map to the BP name and address book. Payment terms and credit limits transfer to the Financials tab of the Business Partner form. We extract all customer balances (AR aged trial balance) to set opening balances in Cloudsuite after the account master is created.

Access ERP vendor records map to Infor Cloudsuite Business Partner records with the Supplier role active. Supplier address books, payment terms, and tax registration codes transfer to the corresponding Cloudsuite BP fields. We preserve the vendor account code as the BP ID and extract outstanding AP balances to set post-migration opening balances. Multi-currency vendor accounts carry the currency definition from Access ERP.

Access ERP items with warehouse-specific quantities, reorder levels, and BOM structures map to CloudSuite Product records with the appropriate stocking and engineering attributes. We extract the item master, warehouse stock quantities per location, and bill of materials. CloudSuite Industrial customers require BOM data to migrate into the Engineering module; CloudSuite Distribution customers require warehouse stocking data in the Inventory module. The item unit of measure and UOM conversion tables from Access ERP map to Infor's UOM framework, which requires a reference table setup step before item import begins.

Open and historical purchase orders migrate with line items, quantities ordered and received, pricing, supplier references, and order status. We preserve the order status (open, partially received, closed) and match closed orders to their received quantity records. Closed purchase orders transfer as historical records with no open quantity remaining. All purchase order records reference the Business Partner (Supplier role) record created during the vendor master import phase.

Open AR invoices migrate with customer references, invoice dates, due dates, outstanding amounts, and invoice line items. We carry the full transaction history needed for credit management and debt collection in Cloudsuite. Closed invoices migrate as historical records with their original payment references and bank statement line identifiers preserved. The invoice header references the Business Partner (Customer role) and the sales GL account from the chart of accounts mapping.

Open AP invoices migrate with vendor references, invoice dates, due dates, amounts, and invoice line items. Historical paid invoices migrate as closed records with their original payment references, payment method, and bank statement line identifiers preserved. AP opening balances are established post-migration using the outstanding invoice totals extracted from Access ERP at the cut-off date.

Access ERP bank account masters and cash book balances migrate including any outstanding unreconciled transactions. We preserve the bank account currency, reconciliation cut-off date, and the unreconciled transaction lines. The cut-off date is agreed during migration planning and documented in the runbook: any transactions posted in Access ERP after this date are excluded from migration and become manual journal entries or a parallel-running reconciliation in Cloudsuite.

Access ERP stores document attachments at the transaction and master-record level. We export attachments in their native format and map them to Infor Document Management (IDM) records linked to the corresponding CloudSuite business object. Attachment types supported include PDF, Office documents, and images. We reattach documents to the corresponding Business Partner, Purchase Order, Sales Invoice, or Product record using IDM's object linking. If the destination CloudSuite environment does not include IDM, we deliver the attachment package as a structured file directory with a manifest mapping each file to its parent record identifier.

Access ERP custom fields and user-defined tables are extracted during schema discovery and mapped to Infor Cloudsuite Extended Fields where the target object supports user-defined attributes, or to custom CloudSuite tables where no standard object exists. We document the full schema delta between the Access ERP live database and a standard installation, then present a configuration map for the Cloudsuite admin to implement before data import. Fields with no Cloudsuite equivalent are flagged in the migration inventory with a recommendation to either implement as extended fields or deprecate.

Access ERP user accounts with role-based permissions, department assignments, and workflow approval limits extract to a user roster with permission profiles. We map Access ERP role names to Infor OS role definitions and flag any Access ERP permissions that have no direct Cloudsuite equivalent (such as approval workflow configurations that are handled differently in Infor Financials workflows). Inactive Access ERP users are imported as inactive Infor OS users for audit trail continuity.