Migrate from Access SupplyChain to Infor CloudSuite Corporate

Access SupplyChain Customer records (name, contact details, payment terms, delivery address, VAT registration) map to Infor CloudSuite Customer records. The customer's payment terms code in Access maps to the Pay Terms Code in CloudSuite; the Credit Limit maps to Customer Credit Limit. We flag any Access custom fields added via Access Studio and create matching custom fields in the CloudSuite Customer form before import. Customer type (trader, government, cash) maps to the Customer Type code in CloudSuite.

Supplier records from Access SupplyChain (address, bank details, category assignments, attachments) migrate to Infor CloudSuite Supplier. The bank account details and sort code fields in Access map to the Payment Details section of the CloudSuite Supplier. Supplier categories map to the Supplier Category code in CloudSuite. Any attachments on the Supplier record are exported and linked via Infor Document Management after the Supplier record is created.

Open and historical purchase orders migrate to Infor CloudSuite Purchase Order. Status values (Draft, Sent, Received, Closed) in Access map to the corresponding PO Status values in CloudSuite. We apply a status filter during scoping: only Open and Part-Received POs migrate as active records; Closed and Invoiced POs migrate as read-only history unless the customer requires full transactional history. PO line items (item, quantity, unit cost) map to PO Line records in CloudSuite with the supplier's part number preserved.

Item master records from Access SupplyChain (SKU, description, unit of measure, cost price, sales price, category) map to Infor CloudSuite Item. Where Access items have been merged or archived, we apply a deduplication filter during extraction and flag duplicates in a reconciliation report. The item's stock category in Access maps to the Item Category in CloudSuite; the default warehouse assignment maps to the Primary Location. UoM conversions from Access carry forward to the CloudSuite UoM setup.

Warehouse records and bin locations migrate to Infor CloudSuite Location records. We extract stock-on-hand as a snapshot at a point-in-time agreed during scoping and apply it at go-live rather than mid-migration to avoid mid-migration discrepancies. Location codes from Access map to Location codes in CloudSuite; any multi-warehouse configurations are preserved as separate Location records with the correct bin structure.

The chart of accounts structure migrates with explicit per-entity mapping required. Organisations running Access SupplyChain across multiple legal entities typically have distinct account code structures per entity. We conduct an account structure interview during discovery, produce a mapping matrix for each entity's accounts to the destination chart, and validate that CloudSuite company codes are configured to accept the migrated account structure before any transactional data loads. Account type (Asset, Liability, Expense, Revenue) maps to the Account Category in CloudSuite.

Outstanding invoices, credit notes, and partial payments migrate as open items to Infor CloudSuite AP and AR modules. We apply the invoice date, due date, outstanding amount, and payment status from Access. Allocations and partial receipts require explicit matching during import because CloudSuite does not auto-allocate outstanding invoices at import time. We provide a reconciliation worksheet listing each open item, its counterparty, and its allocation status for the customer's AP/AR team to verify and finalize post-import.

If the customer uses the Coins Evo construction module, project-level cost tracking data (project name, budget, cost codes, supplier risk scores, approved supplier lists) maps to the corresponding project or job entity in the Infor CloudSuite Construction edition. AI-assisted forecasting rules and risk scoring are not migrated as automation logic; we document the risk scoring methodology and recommended Infor equivalents for the customer's admin to configure post-migration. The Coins Evo chart of accounts integration is reviewed during the account structure interview.

Custom fields created in Access Studio are enumerated during discovery and mapped individually to CloudSuite custom fields. We flag any Access custom fields with unsupported data types (e.g., embedded objects, cross-references, or Access-specific UI controls) and agree on a handling strategy with the customer before migration. Standard text, number, date, and checkbox fields map directly. The migration user requires Infor administrative access to create custom fields via Mongoose Designer or the Infor OS Configuration Console before data import begins.

User accounts from Access SupplyChain migrate to Infor CloudSuite Users with role assignments. Role naming conventions differ between Access SupplyChain versions and CloudSuite, so we produce a role mapping matrix during scoping rather than applying a default mapping. We extract the user's full name, email, and Access role profile and match against the CloudSuite user provisioning list. Inactive Access users migrate as inactive CloudSuite users to preserve audit history. The customer's Infor administrator provisions CloudSuite users before production migration begins.

Documents attached to suppliers, items, and purchase orders in Access SupplyChain are exported to a file share and linked to their destination records in Infor CloudSuite Document Management. Very large files or non-standard formats (e.g., macro-enabled spreadsheets, proprietary file types) are flagged during scoping for a file size and format check. We use the Infor ION Document Management API to upload and attach files to the corresponding CloudSuite records after the base data migration completes.