This checklist is designed as a leadership-level reminder tool for clients and consultants preparing to move from IFS Apps 10 to IFS Cloud. It is not a replacement for IFS’s official cutover and migration documentation, but rather a practical aid to help ensure that critical master data, transactional records, financial closures, and operational readiness items are reviewed before the final data transfer. While the list covers common checkpoints applicable to most clients, each organization should tailor it to reflect industry-specific modules, customizations, and regulatory requirements.

✅ Pre-Final Migration Checklist for IFS Apps 10 → IFS Cloud

1. Master Data

• ☐ Customer & Supplier Records
  • Confirm duplicate clean-up completed.
  • Verify mandatory attributes (addresses, tax IDs, payment terms, etc.).
• ☐ Item & Part Master
  • Validate units of measure, cost method, revision control.
  • Remove obsolete or unused items.
• ☐ Chart of Accounts / Financial Master Data
  • Reconcile with Cloud design (segment structure, posting controls).
• ☐ Org/HR Structure
  • Validate positions, org levels, employees active vs inactive.
• ☐ Site / Warehouse / Location Setup
  • Ensure mapping matches Cloud footprint.

2. Transactional Data

• ☐ Customer Orders
  • Close or cancel open orders not intended for migration.
  • Ensure remaining open orders are clean and approved.
• ☐ Purchase Orders
  • Close old POs that will not be received.
  • Verify supplier invoice matching is up to date.
• ☐ Work Orders / Projects
  • Complete, cancel, or stage only those needed for go-live.
• ☐ Inventory
  • Reconcile stock balances (physical vs system).
  • Run cycle count and freeze stock snapshot for migration.
• ☐ Accounts Receivable / Accounts Payable
  • Apply payments/receipts to clear open transactions where possible.
  • Validate aging reports for carry-forward.
• ☐ Business Opportunities
  • Review pipeline and determine which opportunities should be migrated as “open” versus archived.
  • Ensure status codes align with Cloud configuration.
  • Confirm that opportunities linked to Quotations/Orders are properly closed or transitioned.
• ☐ Shop Orders (Manufacturing)
  • Close or cancel old shop orders that will not be completed.
  • Issue/return material transactions as needed.
  • Ensure WIP balances are reconciled and only valid open shop orders remain for migration.
• ☐ Service Quotations / Request for Quotations (RFQ)
  • Finalize or cancel open RFQs that will not be awarded.
  • For Service Quotations, ensure they are either converted to orders or archived.
  • Validate that supplier responses are captured where required.

3. Configuration & Customizations

• ☐ CRIMs (Configurations, Reports, Integrations, Modifications)
  • Finalize migration impact analysis (what’s retired vs rebuilt).
  • Decommission obsolete customizations.
• ☐ Workflow & Routing Rules
  • Document current rules; ensure mapped to Cloud.
• ☐ Security & Access
  • Confirm Apps10 access aligned to migration freeze (read-only after cutover).

4. Finance & Period Closing

• ☐ General Ledger
  • Ensure last open period is closed prior to migration.
  • Run trial balance and reconcile with sub-ledgers.
• ☐ Fixed Assets
  • Complete depreciation runs.
  • Verify book balances and asset statuses.
• ☐ Cash & Bank
  • Reconcile bank accounts.
  • Apply outstanding bank statements.

5. Operational Readiness

• ☐ Data Validation
  • Perform mock migration load → reconcile reports.
  • Sign-off on critical reports (inventory valuation, AR/AP aging, GL).
• ☐ User Readiness
  • Communicate Apps10 freeze timeline.
  • Ensure training materials are distributed for Cloud processes.
• ☐ Cutover Plan
  • Define blackout window for Apps10.
  • Ensure rollback plan documented.

6. Final Activities Before Locking Apps10

• ☐ Transaction Freeze
  • Stop new orders, POs, WOs in Apps10 at agreed cutover date.
• ☐ Final Data Extract
  • Generate last migration files / ETL.
• ☐ Executive Sign-off
  • Confirm all reconciliations and readiness checkpoints passed.
• ☐ Archive Strategy
  • Ensure Apps10 archive/data warehouse accessible for audit & history.

🔹 Adaptation Notes (to tailor per client)

When using this checklist with a client:

1. Industry-Specific Modules

   • Aviation/Defense → Fleet/Asset Mgmt, Maintenance Programs.

   • Oil & Gas → Project Mgmt, Contract Mgmt, Resource Scheduling.

   • Service-centric → FSM Work Orders, Service Contracts, Warranty Mgmt.

2. Customizations (CRIMs)

   • Validate any non-standard workflows (e.g., using Business Opportunity instead of Sales Quotation).

   • Confirm interfaces/integrations are either rebuilt or decommissioned.

3. Regulatory / Finance Compliance

   • Localized tax, VAT, and reporting obligations.

   • Country-specific period closing requirements.

4. Client-Specific Exceptions

   • Identify any modules not in scope for Cloud migration.

   • Confirm with SMEs if partial data migrations are planned (e.g., only active contracts, last 2 years of history).

Closing Note

By approaching cutover with a structured reminder like this, clients and consultants can stay focused on the functional activities that most directly impact business continuity. The intention is to provide clarity and reduce the risk of missed steps, while still allowing room for each organization to adapt the list to its own context. I encourage others in the IFS Community to share their experiences, additional checkpoints, or lessons learned so we can continue strengthening our collective approach to successful migrations from Apps 10 to IFS Cloud.