ifs applications migration assessment delivered in 2–3 weeks with hard evidence. IFS version, module footprint, Custom PL/SQL inventory, Custom Event count, IFS Connect endpoint catalog, history depth per domain, regulatory exposure — and a sized timeline + cost backed by automated discovery.
Consultant-led IFS assessments take 8–12 weeks and produce soft estimates based on interview hours. Syntra's automated discovery runs against IFS Solution Manager directly and produces hard counts in 2–3 weeks.
The biggest single risk on an IFS to Fusion programme isn't the data load — it's getting the scope wrong upfront. A consultant-led assessment process traditionally spends 8–12 weeks interviewing IFS users, IT operations, finance, MRO ops, project teams and integration owners to build a manual inventory of customizations, integrations, history depth and regulatory exposure. The output is a slide deck with rough estimates and a sized SoW based on interview-hours-per-domain.
Syntra ETL's ifs applications migration assessment inverts this. The assessment engine deploys to the customer's cloud environment in week 1, authenticates read-only against the IFS Oracle Database backend and the IFS Connect Framework, walks IFS Solution Manager directly, and produces hard counts: every active Logical Unit, every Custom Field, every Custom Event, every Custom Object, every bespoke PL/SQL package, every IFS Connect endpoint, every IPC queue, every Background Job, every IFS BI report, plus row-count by fiscal year per domain. Week 2: workshops with domain owners validate the automated discovery output and the Fusion-routing classification per customization item. Week 3: signed assessment with sized timeline and cost.
The same engine handles every IFS version (7.5, 8, 9, 10) and every IFS module (Financials, EAM/MRO, Project, SCM, HCM, FSM) — with version-specific timeline buffers, module-specific scope adjustments and industry-specific compliance work (FAA, ITAR, NRC, OSHA PSM) accounted for. The output is concrete enough to base a SoW on, conservative enough to deliver to, and detailed enough that internal audit can review the assumptions.
Get these right and the rest of the migration runs to plan. Get these wrong and the migration slips by quarters.
7.5, 8, 9 or 10. Each version brings different tooling, OAuth patterns and LU catalog completeness. Version-specific timeline buffer drops out of the assessment automatically.
Every bespoke PL/SQL package in the IFS Solution Manager registry inventoried, classified by business purpose and call frequency. Fusion-routing recommendation per package.
Every Custom Event with execution log frequency. Classification by business purpose (validation, workflow, integration). 30–50% typically retire under Fusion native.
Every active REST/SOAP endpoint with direction, partner system, message format and invocation frequency. Fusion routing (REST, OIC, BI Publisher) per endpoint.
Row count per LU per fiscal year. GL/AP/AR/FA depth, MRO work-order history per fleet, project history per project, document archive volume per LU.
FAA 14 CFR Part 121.380, ITAR, DFARS, NRC 10 CFR 50, OSHA 29 CFR 1910.119 PSM, SOX, GDPR, EU MDR — flagged per IFS module per BU per region.
Credentials to signed assessment in 2–3 weeks. Hard evidence, sized timeline, sized cost — ready for SoW.
Oracle DB read-only credentials provisioned (with Active Data Guard standby preference). IFS Connect OAuth2 client credentials provisioned via IFS Solution Manager with scoped read access. Assessment engine deployed to customer cloud environment.
Engine runs against IFS Solution Manager (LU catalog, Custom Field/Event/Object/PL-SQL registry), IFS Connect Framework (endpoint catalog, IPC queues, Background Jobs), IFS Oracle DB backend (row counts per LU per fiscal year), IFS BI metadata (SSAS cubes, SSRS reports, Power BI datasets). Output: complete automated discovery report.
Workshops with finance, MRO ops, project ops, supply chain, integration owner, compliance, IT ops, IFS BI owner. Each domain owner validates the automated discovery output and the Fusion-routing classification for their domain. Risks surfaced and quantified.
Common risks (IFS 7.5 SOAP-only, 500+ Custom Events, multi-decade MRO history, FAA life-of-aircraft retention, ITAR USA-citizens-only custody, multi-site intercompany) quantified with mitigation, timeline impact and cost impact. Timeline sized per phase with risk-adjusted buffer.
Cost sized per phase, per module, per work stream (extract+load, customization rebuild, integration cutover, IFS BI rebuild, parallel run, audit pack). Cost backed by evidence — not interview-hour estimates.
Assessment document finalized: ten dimensions covered, risk register quantified, timeline sized, cost sized. Signed by Syntra delivery lead and customer programme manager. Forms basis of the SoW.
A complete, evidence-based picture of the migration scope — ready for SoW and steering committee approval.
Every Custom Field, Custom Event, Custom Object, bespoke PL/SQL package with usage frequency, business-purpose classification and Fusion-routing recommendation.
Every IFS Connect endpoint, IPC queue, Background Job with direction, partner system, invocation frequency and Fusion-routing recommendation (REST, OIC, BI Publisher, retire).
Row count per LU per fiscal year per BU. Retention policy mapped per domain — what goes to Fusion, what goes to IFS Cloud Archive, what retires.
Every SSAS cube, SSRS report, Power BI dataset classified by business value with OTBI/BI Publisher/Fusion Analytics Warehouse routing per item. 40–60% typically retired.
FAA Part 121.380, ITAR, DFARS, NRC 10 CFR 50, OSHA PSM, SOX, GDPR, EU MDR — flagged per module per BU per region with compliance-work timeline impact quantified.
Sized per phase with risk-adjusted buffer, sized per work stream, signed by Syntra delivery lead and customer programme manager. SoW-ready.
An ifs applications migration assessment is the structured discovery and readiness review that precedes any IFS Applications to Oracle Fusion migration. It catalogs every dimension of the current IFS tenant that affects scope, timeline and risk: IFS version (7.5, 8, 9 or 10 — each has different tooling, support and version-specific behaviors), module footprint (Financials, EAM/MRO, Project, SCM, HCM, FSM), customization depth (Custom Fields, Custom Events, Custom Objects, bespoke PL/SQL packages), integration count and topology (IFS Connect REST/SOAP endpoints, file-based EDI, scheduled batch jobs), history depth (financials typically 7–10 years, asset/MRO history often 20–30+ years), and regulatory exposure (FAA, ITAR, NRC, OSHA PSM, SOX, GDPR). Syntra ETL delivers the ifs applications migration assessment in 2–3 weeks with hard evidence — not consultant-led estimation.
IFS Applications versions 7.5, 8, 9 and 10 differ significantly in tooling availability, OAuth2 patterns, IFS Connect Framework maturity, IFS Solution Manager features and LU catalog completeness. IFS 7.5 (legacy aerospace deployments still in production at some major MRO customers) lacks modern OAuth2 and requires SOAP-only extraction patterns. IFS 8 and 9 (the workhorse on-prem releases) have IFS Connect with REST support. IFS 10 (the last on-prem release before IFS Cloud) has the richest customization registry. Each version has version-specific Custom Event execution log formats, version-specific Background Job behaviors and version-specific PL/SQL package layouts. The ifs applications migration assessment scopes the extractor configuration, the OAuth pattern and the timeline buffer per version detected — generic estimates that ignore IFS version get migration timelines wildly wrong.
By direct walk of the IFS Solution Manager customization registry. IFS Solution Manager exposes every Custom Event (with execution log frequency), every Custom Field (with reporting-materiality flag), every Custom Object (with table extension definition) and every bespoke PL/SQL package (with last-modified timestamp, dependencies and call-frequency metrics). The Syntra ETL assessment engine walks this registry, classifies each item by business purpose (validation rule, automated workflow, custom calculation, integration hook, statutory requirement), and produces a Fusion-routing recommendation per item: AMX flow, BI Publisher report, Application Composer extension, OIC integration, or retire (because Fusion-native already covers it). The output: a complete customization inventory typically showing 30–50% retire-able under Fusion's native capabilities. This is the most expensive piece to misjudge — and Syntra's evidence-based count is what stops a consultant from selling 6 months of bespoke development that wasn't needed.
By direct walk of the IFS Connect endpoint catalog. IFS Connect exposes every active REST endpoint, every SOAP service, every file-based EDI gateway, every IPC message queue and every Background Job — with direction (inbound/outbound), partner system identifier, message format, last-invocation timestamp and invocation frequency. The Syntra ETL assessment engine walks this catalog and produces a complete integration inventory: which endpoints carry mission-critical traffic, which are dormant, which can retire, which need Fusion REST equivalents, which need OIC integration flows, which need BI Publisher bursting. The integration count is the second highest leverage piece of the ifs applications migration assessment after Custom PL/SQL count — and Syntra's evidence-based inventory replaces a typical multi-week consultant interview process with a 48-hour automated discovery run.
By direct count against the IFS Oracle Database backend. The Syntra ETL assessment engine runs row-count queries per LU per fiscal year going back to the earliest active partition — and produces a history-depth profile per domain: GL/AP/AR/FA typically 7–15 years per BU, FA history per asset class, work-order history per fleet (life-of-aircraft for aerospace MRO customers carries 30+ years), project history per project (multi-year capital projects in construction and aerospace), inventory transaction history per item per organization, document attachment count and byte-total per LU. The history-depth profile drives two critical decisions: which history goes to Fusion (typically the last 7–10 years for active reporting) and which history goes to the long-term IFS Cloud Archive (anything older, plus regulated retention requirements like FAA 14 CFR life-of-aircraft + 5 years).
A structured assessment document covering ten dimensions. IFS version and edition. Module footprint with active LU inventory per module. Customization inventory: Custom Fields, Custom Events, Custom Objects, bespoke PL/SQL packages with Fusion-routing recommendation per item. Integration inventory: IFS Connect endpoints, IPC queues, Background Jobs with Fusion-routing recommendation per item. IFS BI report inventory: SSAS cubes, SSRS reports, Power BI datasets with OTBI/BI Publisher/Fusion Analytics Warehouse routing per item. History depth per domain with retention policy mapping. Document attachment volume per LU. Regulatory exposure (FAA, ITAR, NRC, OSHA PSM, SOX, GDPR, EU MDR). Sized timeline estimate per phase with risk register. Sized cost estimate. Signed by Syntra delivery lead and customer programme manager as the basis for the SoW.
Typically 2–3 weeks from credential provisioning to signed assessment. Week 1: credentials provisioned (Oracle DB read-only, IFS Connect OAuth2 scoped read), Syntra ETL assessment engine deployed to customer cloud environment, automated discovery runs against IFS Solution Manager + IFS Connect + IFS Oracle DB backend. Week 2: assessment engine output reviewed in workshops with finance, MRO ops, project ops, supply chain, integration owner and compliance leads — each domain owner validates the customization classification and routing recommendation for their domain. Week 3: assessment document finalized, sized timeline and cost produced, signed by Syntra delivery lead and customer programme manager. This compares to typical consultant-led assessment cycles of 8–12 weeks producing softer estimates.
The risk register is the heart of the ifs applications migration assessment deliverable. Common risks surfaced: IFS 7.5 customers with SOAP-only extraction requirements add 2–4 weeks. Customers with 500+ Custom Events add Custom Event classification time. Customers with multi-decade MRO history add document archive extract time. Aerospace customers carrying FAA 14 CFR life-of-aircraft retention add 6–8 weeks of evidence-pack work. Defense customers under ITAR add USA-citizens-only custody constraints. Multi-site UAE customers with 5–15 IFS sites add intercompany reconciliation complexity. Heavy IFS BI rebuild adds OTBI/BI Publisher/Fusion Analytics Warehouse work. Each risk is quantified with mitigation, timeline impact and cost impact — so the customer makes go/no-go decisions on hard evidence rather than gut feel.
30-minute scoping call. We'll confirm credential provisioning approach, scope domain owner workshops, and have a signed assessment ready in 2–3 weeks. Evidence-based timeline and cost — not interview-hour estimates.