Infor LX (BPCS) Migration Assessment — Before You Commit to a Target

An Infor LX (BPCS) migration assessment is a 2–4 week structured discovery exercise that inventories everything that has to move (or be retired) when you migrate BPCS off IBM i to a modern target — Oracle Fusion, Infor CloudSuite Industrial, SAP S/4HANA or a data-warehouse-only sunset. The assessment crawls your BPCS libraries (LXFILES, LXMODOBJ, custom libraries) on the AS/400, indexes every physical and logical file in use, every RPG IV / III and COBOL program, every CL command and DDS display file, every Query/400 report, every UDF added since 1995, every active interface, and every IBM i journal in retention. The output is a sized assessment with risk register, customisation classification, hardware-retirement plan, data-volume estimate, cutover-window proposal and a concrete budget — before you commit a single dollar to platform selection or a system integrator. Customers who skip the Infor LX (BPCS) migration assessment routinely discover six months in that 40% of their RPG customisations are still in active use and have no Fusion equivalent, blowing their go-live date by 6–9 months. Customers who do the assessment up-front hit go-live on the original date in 84% of cases.

Typically 2–4 weeks end to end. Week 1: IBM i user profile provisioning (read-only object authority on LXFILES, LXMODOBJ and any custom libraries), Syntra extractor deployment to your cloud environment, initial library crawl. Week 2: full inventory of BPCS files, RPG / COBOL / CL / DDS objects, Query/400 reports, UDFs and active interfaces. Week 3: classification (in-use vs orphaned, critical vs nice-to-have, native-Fusion vs needs-rebuild), data-volume sizing, IBM i hardware-retirement scoping. Week 4: stakeholder workshops with finance, manufacturing ops, supply chain, IT and compliance to validate findings, plus delivery of the sized assessment pack (risk register, sized timeline, sized budget, cutover-window proposal). Consultant-led BPCS assessments typically take 3–4 months and cost 4–6× more — most of which is the consultants learning your BPCS estate from scratch through interviews because they don't have automated AS/400 library discovery.

Everything that touches BPCS on the IBM i. BPCS file inventory: every physical and logical file in LXFILES / LXMODOBJ / custom libraries, sized by record count and disk footprint, classified by module (GL, AP, AR, Manufacturing, Inventory, Order Management, Procurement, Fixed Assets, audit-trail). Customisation inventory: every RPG IV / III program, every COBOL program, every CL command, every DDS display file and printer file, every Query/400 report — classified by last-execution date, by calling-chain and by business value. UDF inventory: every UDF added through the LX customisation framework, with reporting-materiality classification. Interface inventory: every active EDI / FTP / MQ / web-service integration touching BPCS. Journal inventory: every IBM i journal in retention with retention-policy classification. Hardware inventory: every LPAR, every Power-i model, every software licence (LX, MIMIX / RoboHA, BCS, IFM), every disk-arm consumed. Output is a single sized assessment pack with auditable inventory CSVs and Parquet exports.

Every RPG IV / III program, COBOL program, CL command and DDS display file in scope is classified along four axes. Usage: in active production use (called in the last 90 days from job logs), occasionally used (called in the last year), or orphaned (no recorded call in over a year). Business value: critical (revenue-affecting or compliance-mandated), important (operational efficiency), nice-to-have (cosmetic or one-off historical fix). Fusion replaceability: native Fusion functionality covers it, OTBI / BI Publisher report rebuild, Visual Builder extension, Smart View Excel template, or genuinely unique business logic needing custom redevelopment. Migration disposition: rebuild during migration, retire (orphaned), defer (occasionally used, rebuild later), or keep BPCS running for this module (hybrid pattern). The Infor LX (BPCS) migration assessment routinely finds 50–70% of legacy customisations are redundant under Fusion's native breadth — but the 30–50% that aren't have to be rebuilt for go-live, and finding them early is the difference between a 14-week and a 14-month project.

Yes. The Syntra Infor LX (BPCS) migration assessment includes a hardware-retirement scoping module that inventories every Power-i LPAR running BPCS or BPCS-adjacent workloads (MIMIX / RoboHA HA replicas, BCS / IFM / FACT / PMC subsystem servers, dev / QA / training partitions), every IBM software licence in play (LX, MIMIX, BCS, Infor add-ons, third-party tools), every disk-arm consumed and every annual maintenance contract. Output is a retirement timeline aligned to your migration cutover (which LPARs can power down at go-live, which need to stay live for read-only archive query, which need MIMIX replication for the parallel-run window) and a recurring-cost wind-down schedule (typically $300K–$2M per year saved depending on Power-i model and licence load) that goes straight into the migration business case.

Yes — the Syntra Infor LX (BPCS) migration assessment is target-agnostic. It produces a side-by-side decision framework comparing your specific BPCS estate (modules, customisation depth, manufacturing complexity, multi-company / multi-currency footprint, vertical — F&B, CPG, process manufacturing, pharma) against the realistic fit of each target: Oracle Fusion Cloud ERP (strongest for global multi-currency Financials and Manufacturing breadth), Infor CloudSuite Industrial Enterprise (Infor's official LX successor — smooth functional fidelity but you're staying inside Infor's roadmap and platform), SAP S/4HANA (heavyweight, typically only for >$2B-revenue customers), or stay on BPCS with a data-modernisation layer (where the IBM i estate is paid off and the platform risk is genuinely low). The decision framework feeds the platform-selection workshop — not the other way round. Most customers who do the assessment end up with a clear, defensible recommendation in week 4.

A standard Infor LX (BPCS) migration assessment is a fixed-fee 2–4 week engagement scaled to BPCS footprint. Small (single-pillar Financials-only, single-company, sub-100GB DB2 footprint): roughly $40–70K. Mid (Financials + Manufacturing, 2–5 companies, multi-warehouse, 100GB–1TB): $70–130K. Large (full BPCS footprint, 5+ companies, 5+ warehouses, multi-currency, 1TB+, customisation-heavy): $130–250K. The fee includes IBM i extractor deployment, full library crawl, customisation classification, hardware-retirement scoping, target-platform decision framework, sized timeline, sized migration budget, and stakeholder workshops. Customers routinely save 5–10× the assessment fee in avoided rework on the eventual migration — and the assessment fee credits against the migration project if Syntra ETL is selected as the migration platform.

Light touch from the customer side, which is the point. Required: one IBM i administrator (operator or security officer) to provision the read-only *USRPRF and confirm library access scope — typically 4–6 hours of effort across the 4 weeks. One BPCS functional lead per active module (Financials, Manufacturing, Inventory, Order Management) to validate customisation classification and confirm critical-vs-nice-to-have calls — typically a half-day workshop each in week 3. One compliance / internal-audit lead to validate retention-policy and audit-trail classification. Optional: an RPG developer if you have one in-house, to spot-check the more obscure customisation classifications (helpful but not required — Syntra's library crawler does the inventory automatically). No multi-month interview-driven discovery — the Syntra Infor LX (BPCS) migration assessment is built so customers without an RPG developer can still get an honest, complete picture of their BPCS estate.