The complete ifs applications migration checklist: scope, customization, reporting, integration, regulatory, security, Fusion readiness, cutover logistics. Two-week structured walk-through replaces six months of consultant-led discovery. Every item owned, decided, dated.
IFS Applications customers carry decades of accreted complexity. Walk the ifs applications migration checklist in week three and the architecture phase starts on solid ground. Skip it and the project finds the surprises in month seven.
Industrial and Financial Systems (IFS, Swedish-origin, founded 1983) has been the ERP backbone for asset-heavy enterprises in aerospace & defense, energy & utilities, oil & gas, construction, manufacturing and telecom across Europe, Middle East and Asia Pacific for four decades. Customers like Emirates Airlines and ADNOC in the UAE, alongside hundreds of large IFS sites across the Nordics, EU and APAC, have built operational dependencies on Custom Events (event-driven workflow triggers), Custom Fields (the IFS analogue of EBS DFFs), bespoke PL/SQL packages enforcing customer-specific business rules, IFS BI dashboards on SSAS/SSRS/Power BI that finance and MRO ops have built their working day around, and IFS Connect integrations to dozens of downstream systems.
The ifs applications migration checklist below is the structured way to surface every one of those dependencies before the migration architecture is signed off — not after, when changing them costs ten times more. Eight areas, 60+ items, two-week structured walk-through. Each item gets an owner, a decision (retire / replace / rebuild / preserve as-is) and a target completion date. By end of week three, the architecture phase starts with a complete, signed-off picture of what's actually in production and what needs to land in Fusion.
The ifs applications migration checklist isn't paperwork for its own sake — it's the mechanism that prevents the three failure modes that wreck IFS migrations: underestimating Custom Event translation labour (discovered in month four when business signs off the AMX approval flows and realises 40 IFS Custom Events need behaviour-equivalent rebuilds), descoping the IFS BI rebuild at planning time (discovered in month six when finance asks where the month-end close reports are), and missing IFS Connect endpoints (discovered at cutover when EDI partner 850 inbound messages start failing because the OIC flow wasn't built). The ifs applications migration checklist surfaces all three in week three.
Each area below is a section of the checklist. Click through to see every item.
IFS version and patch level, module footprint, regional deployments, history depth per domain, transaction volume per year, satellite Oracle DB applications, infrastructure footprint, total database size, RAC and Active Data Guard topology, integration partner count.
Custom Event inventory, customized PL/SQL packages, Custom Field catalog, Custom Objects, IFS Lobbies customizations, aurena page customizations, custom command-bar actions, bespoke data-loading utilities, custom scheduled tasks, custom IFS reports (RDF), Background Job customizations, bespoke PL/SQL integrations.
IFS BI dashboards and KPIs, SSAS cube inventory, SSRS report list, Power BI dashboards and datasets, IFS Information Sources catalog, ad-hoc IFS BI queries, statutory reporting templates per country, regulatory reports, customer-facing documents, internal management reports.
IFS Connect REST endpoints, IFS Connect SOAP endpoints, Background Job registry, IPC queues, file-based EDI gateways, IFS Document Management integration, bespoke PL/SQL outbound APIs, BI/warehouse extracts, replication to downstream systems, partner-specific integrations.
FAA 14 CFR Part 121.380, ITAR/DFARS, NRC 10 CFR 50, NERC CIP, OSHA 29 CFR 1910.119 PSM, SOX 7-year retention, GDPR, country-specific statutory (UK Companies Act, UAE VAT, German GoBD, etc).
IFS Solution Manager OAuth credentials, Oracle DB Active Data Guard read access, network paths, certificate management, audit logging, role mapping IFS → Fusion.
A structured sequence designed to land every checklist item with an owner, a decision and a date by end of week three.
Sponsors aligned, business owners identified per area (finance, MRO ops, projects, supply chain, IT integration, compliance). Read-only IFS Solution Manager and Oracle DB Active Data Guard credentials provisioned to Syntra ETL discovery engine.
Discovery engine walks the Logical Unit catalog, Custom Event registry, PL/SQL package list, Custom Field catalog, IFS BI report library, SSAS cube inventory, SSRS report list, IFS Connect endpoint catalog and Background Job registry. Inventory delivered as structured artefacts.
Finance and projects business owners walk the customization inventory, classify Custom Events and PL/SQL packages retire/replace/rebuild. Sign off the IFS BI rebuild scope for finance reporting. Agree the AMX approval workflow design covering retired Custom Events.
MRO ops and supply chain business owners walk the EAM, manufacturing and supply chain customizations. Classify work-order Custom Events, configuration-management PL/SQL, MRO BI reports. Sign off Fusion Maintenance / SCM rebuild scope.
IT integration owners walk the IFS Connect catalog, classify each endpoint retire/re-implement on OIC/Fusion REST/ESS. Compliance owners walk the regulatory profile (FAA/ITAR/NRC/OSHA PSM/SOX/GDPR), confirm retention requirements and audit-chain depth.
Full ifs applications migration checklist signed off — every item with owner, decision, target date. Architecture phase kicks off with no open scope questions. Risk register published with quantified high/medium/low items.
Tangible artefacts that drive every subsequent decision in the migration programme.
Every Custom Event, PL/SQL package, Custom Field and Custom Object with business purpose, classification (retire/replace/rebuild) and Fusion-equivalent target (AMX, Application Composer, OIC, BI Publisher).
Every BI report classified business-value, retired-duplicate or mapped to OTBI / BI Publisher / Fusion Analytics Warehouse target. Sequencing on the critical path — rebuild starts month three not month seven.
Every IFS Connect endpoint mapped to OIC flow, Fusion REST or ESS scheduled job. Cutover-window plan per partner — atomic-switch vs dual-route. EDI partner notification timelines.
Domain-by-domain sized estimate (Financials weeks, EAM weeks, Project weeks, history-load weeks) feeding the high/medium/low ifs applications migration cost model. Sign-off ready for finance.
Quantified risks per area with mitigation owners. Top risks typically: Custom Event translation labour, IFS BI rebuild duration, IFS Connect partner-cutover coordination, MRO history audit-chain preservation.
Signed-off scope, customization decisions, BI rebuild plan, integration plan, regulatory commitments. Architecture phase starts with no open scope questions — which is what separates 6-month projects from 18-month projects.
An ifs applications migration checklist is the structured pre-migration inventory and decision list that gets every IFS-specific risk surfaced and owned before extract work begins. The Syntra ETL ifs applications migration checklist covers 60+ items across eight areas: scope definition (IFS version, modules, history depth), customization inventory (Custom Events, PL/SQL packages, Custom Fields, Custom Objects), reporting estate (IFS BI, SSAS cubes, SSRS reports, Power BI dashboards), integration topology (IFS Connect endpoints, Background Jobs, IPC queues, EDI gateways), regulatory profile (FAA 14 CFR, ITAR/DFARS, NRC 10 CFR 50, OSHA PSM, SOX, GDPR), Fusion-side readiness (enterprise structures, ledgers, BUs, COA, asset categories), security (IFS Solution Manager OAuth credentials, Oracle DB Active Data Guard read access), and cutover logistics. Walking the ifs applications migration checklist in week three replaces six months of consultant-led discovery.
The full ifs applications migration checklist takes two weeks of focused effort: week one is automated discovery (Syntra ETL discovery engine walks the Logical Unit catalog, Custom Event registry, PL/SQL package list, IFS BI library and IFS Connect catalog, generating the inventory automatically), week two is human-in-the-loop classification (business owners for finance, MRO ops, projects, supply chain review the inventory, classify customizations retire/replace/rebuild, sign off the IFS BI rebuild scope, agree the integration cutover plan). At the end of two weeks every item on the ifs applications migration checklist has an owner, a decision and a target date — and the architecture phase can start on solid ground rather than mid-project surprises.
Scope items on the ifs applications migration checklist: IFS Applications version (7.5, 8, 9, 10) and last patch level; module footprint (Financials — GL/AP/AR/FA/Cash/Tax, Project Management, Manufacturing, Supply Chain, EAM/MRO, Service Management (IFS FSM), HCM, Document Management); regional deployments (single tenant or multi-country, common UAE+Europe pattern); history depth per domain (financial typically 7–10 years, MRO typically 20–30+ years for aerospace fleets, project typically lifecycle of active projects); transaction volume per domain (records per year for sizing); custom-developed satellite applications on the IFS Oracle DB; database size and infrastructure footprint (RAC nodes, Active Data Guard, total TB). Every scope item drives a downstream sizing decision.
Customization items on the ifs applications migration checklist: full Custom Event inventory from IFS Solution Manager (event name, LU triggered on, business purpose, last fired); full PL/SQL package list (customized vs vanilla, package purpose, dependencies); Custom Field catalog (which LU, data type, validation rules, usage in reports); Custom Object inventory (purpose, related LUs); custom IFS reports (RDF, Oracle Reports legacy); IFS Lobbies customizations; aurena client customizations; bespoke aurena pages or custom command-bar actions; IFS Background Job customizations; custom scheduled tasks; bespoke data-loading utilities; PL/SQL-based integrations not exposed through IFS Connect. The classification step decides retire/replace/rebuild per item — typically 30–50% retire under Fusion native.
Reporting items on the ifs applications migration checklist: IFS BI report inventory (every dashboard, KPI, scorecard); SSAS cube list (cube name, dimensions, measures, business owner, refresh frequency); SSRS report inventory (every standard and custom report, parameters, distribution list); Power BI dashboard inventory (workspace, dataset, distribution); IFS Information Sources catalog (the staged views over LU model that BI sits on); user-driven ad-hoc IFS BI queries from the past 6 months; statutory reporting templates per country (UK Companies House, German GoBD, UAE VAT filings, US SOX disclosures); regulatory reporting (FAA quarterly returns for aerospace, NRC reports for nuclear-adjacent, OSHA PSM documentation); customer-facing reports (invoices, statements, MRO certificates, shipping documents). Survivors map to OTBI/BI Publisher/Fusion Analytics Warehouse — 40–60% typically retire as duplicates.
Integration items on the ifs applications migration checklist: full IFS Connect endpoint catalog (REST and SOAP), per endpoint — direction (inbound/outbound), partner system, message format, business purpose, SLA, volume per day; IFS Background Job registry — every scheduled batch job, frequency, purpose; IPC (Inter-Process Communication) queue inventory; file-based EDI gateways — partner, document type (EDI 850, 856, 810, 940 etc), file location, transport protocol (SFTP, AS2); IFS Document Management integration endpoints; third-party integrations not routed through IFS Connect (bespoke PL/SQL packages calling external APIs); BI / data-warehouse extracts from the IFS Oracle DB; replication to other downstream systems. Each integration item gets a Fusion-equivalent target — OIC flow, Fusion REST, ESS scheduled job — and a cutover-window plan.
Regulatory items on the ifs applications migration checklist depend on industry. Aerospace MRO: FAA 14 CFR Part 121.380 life-of-aircraft retention, ITAR for military fleets, DFARS for US defense contracts, EASA Part-145 for European MRO organisations. Energy & utilities: NRC 10 CFR 50 for nuclear-adjacent assets, NERC CIP for grid operators, EU energy directives. Oil & gas: OSHA 29 CFR 1910.119 PSM process safety information, EPA RMP risk management, IOGP standards. All industries: SOX 7-year financial retention, GDPR for European personal data, UK Companies Act for UK statutory accounts, UAE VAT, US state-level sales tax. Each regulatory regime drives a retention-depth, an audit-chain-preservation requirement and an evidence-pack format. Syntra ETL's IFS Cloud Archive supports ITAR-ready deployments (AWS GovCloud, FedRAMP) where required.
Fusion-side readiness items on the ifs applications migration checklist: Fusion environment provisioning (test, dev, prod tenants); enterprise structures designed (Set of Books, BUs, Ledgers, Reporting Currency); COA defined with segments (typically Company-Cost Centre-Account-Product-Project plus intercompany); ledger setup with calendars, currencies, accounting methods; BU and inventory organization setup; asset categories for Fusion Maintenance; project types and templates for Fusion PPM; supplier and customer party setup; AMX approval workflows designed (replacing IFS Custom Events for approvals); Fusion roles and security designed; OIC connection setup for the IFS Connect bridge; FBDI/HDL load credentials and ESS job-submit roles; OTBI subject area subscriptions; BI Publisher report templates seeded; Fusion Analytics Warehouse subscription if required; Fusion Maintenance REST API access for asset loading. Each item has an owner and a target-ready date.
Book a 30-minute discovery call. We'll kick off the two-week ifs applications migration checklist walk-through with read-only IFS Solution Manager access and deliver the signed-off architecture kick-off pack by end of week three.