Governed Infor LX (BPCS) decommissioning workflow. Final cloud-archive load with hash-signed evidence, IBM i Power LPAR shutdown, Infor LX support contract non-renewal, IBM Software Maintenance termination, RPG / AS/400 role transition, tamper-evident certificate of decommissioning for ISO 27001 / SOC 2 / SOX reviewers.
Most BPCS customers spend months designing the new-ERP go-live and weeks on the BPCS decommissioning. The cost gets paid later — in unrecovered IBM i contracts, lingering RPG staffing and audit-evidence gaps.
The economics of running a dormant BPCS instance are usually invisible until someone forces the spreadsheet. IBM Software Maintenance Agreement for the IBM i operating system, IBM Hardware Maintenance Agreement for the Power9 / Power10 server, Infor LX support / maintenance subscription, PowerVM virtualisation licence, DB2 for i included costs, colocation rack space, power and cooling, 0.5–2 FTE of AS/400 operator and RPG developer time to keep the lights on. For a typical mid-market customer the annual cost is $80K–$400K per IBM i LPAR — pure overhead with zero operational value once the live workload has moved.
And yet customers routinely defer Infor LX (BPCS) decommissioning for 12–36 months after the new-ERP go-live, paying that overhead for no business value, because the decommissioning workflow itself was never properly planned. The IBM i sits there because nobody has the time to do the final archive load, capture the audit-trail evidence, transition the RPG developer, terminate the Infor support contract, file the hardware disposal certificate and sign the certificate of decommissioning.
Syntra ETL packages all of that as a turnkey Infor LX (BPCS) decommissioning workflow. The final cloud archive load (with EBCDIC translation, COMP-3 unpacking, hash-signed audit evidence, BPCS audit-trail and IBM i journal capture). The IBM i Power LPAR shutdown sequence with operator-signed log. The Infor / IBM contract non-renewal coordination. The role transition for RPG / AS/400 staff. The certificate of decommissioning that satisfies ISO 27001 control A.8.10, SOC 2 confidentiality / processing-integrity, SOX 404 records management, and any industry-specific record-disposal regulation (FDA 21 CFR Part 11 for pharma, DFARS for defence).
The deliverables an internal audit or external assessor will ask for.
Written plan signed by IT, finance, compliance and the BPCS business owner. Lists every BPCS file in retention scope, every IBM i LPAR being decommissioned, every contract being terminated, every staff role being transitioned.
Hash-signed manifest of every Parquet file in the final cloud archive load, record counts and sum totals per partition, BPCS audit-trail capture confirmation, IBM i journal capture confirmation.
Operator-signed log of the IBM i Power LPAR shutdown sequence: backup taken, final journal capture, LPAR varied off, hardware powered down, console log preserved, dated and signed by the operator who performed it.
NIST 800-88 wipe certificate for on-prem hardware disposal, or transfer certificate for hardware redeployed to non-BPCS workload, or broker certificate for hardware sold to a used-IBM-i reseller.
Written confirmation from Infor and IBM that the LX support, Software Maintenance and Hardware Maintenance contracts have been terminated as of a specified date. Required for finance to recover the spend in the budget.
Master certificate signed by IT, finance, compliance and (where applicable) FDA Quality Assurance, attesting that the Infor LX (BPCS) decommissioning was performed per the plan, audit evidence preserved, and ready for ISO 27001 / SOC 2 / SOX review.
Repeatable, governed and reviewer-ready. Typical timeline: 12–14 weeks from kick-off to certificate of decommissioning.
Written plan documents every BPCS file in retention scope, every IBM i LPAR being decommissioned, every contract being terminated, every staff role being transitioned. Signed by IT, finance, compliance, BPCS business owner.
DB2 for i extractor pulls every BPCS file in retention scope to cloud archive with EBCDIC translation, COMP-3 unpacking, hash-signed manifests. BPCS audit-trail files and IBM i journals captured. Multi-TB extracts scheduled to off-peak.
Cloud archive validated against IBM i source for byte-level correctness. Sample queries run by finance, tax, audit users to confirm the historical-reporting use case is met. 90-day IBM i read-only stability window begins.
RPG developer / COBOL developer / AS/400 operator roles transitioned. Knowledge capture (customisation documentation, RPG source-code snapshot, operator runbooks) into the audit evidence pack. Staff move into replacement-ERP team, cloud-archive ops role, or HR-managed exit.
Final delta capture from IBM i journal. IBM i Power LPAR varied off and powered down per operator-signed log. Hardware disposal (NIST 800-88 wipe) or redeployment. Console log preserved in audit evidence.
Infor LX support, IBM Software Maintenance, IBM Hardware Maintenance contracts terminated as of effective date. Colocation cancelled. Certificate of decommissioning signed by IT, finance, compliance, FDA QA (if applicable).
The line items finance can recover in the budget once the Infor LX (BPCS) decommissioning completes.
Typically $20K–$80K per year per IBM i server for the operating system, DB2 for i and bundled products. Cancellable as of the LPAR shutdown date. Annual recurring saving.
Typically $10K–$40K per year per Power9 / Power10 server. Cancellable upon hardware decommissioning. Avoidance of the next hardware refresh cycle (typically $50K–$200K capex every 5 years) also material.
Infor LX maintenance / support subscription, typically $30K–$150K per year depending on user count and modules. Non-renewable at the end of the current term. Material recurring saving.
For on-prem / colocation AS/400 customers: rack space, power, cooling, network connectivity all cancellable. Typically $10K–$40K per year per server, plus sustainability-reporting positive.
AS/400 operator role (typically 0.5–1 FTE) and RPG developer engagement (0.5–2 FTE equivalent in retained-contractor terms) transitionable. Staff move into replacement-ERP team or HR-managed exit.
Typical mid-market customer: $80K–$400K per IBM i LPAR per year recurring saving once Infor LX (BPCS) decommissioning completes. Multi-LPAR / multi-site customers see proportional multiples.
Infor LX (BPCS) decommissioning is the planned, governed retirement of the BPCS application, the IBM i (AS/400) hardware that runs it and the related Infor / IBM contracts and staffing. It includes: (1) a final data archive to cloud object storage with audit-grade evidence preservation, (2) WORM-lockable retention configured to satisfy SOX, IRS and any industry-specific regulation (FDA 21 CFR Part 11 for pharma, defence DFARS, etc.), (3) IBM i Power LPAR shutdown and hardware disposal or repurpose, (4) Infor LX support contract non-renewal and IBM Software Maintenance contract termination, (5) RPG developer and AS/400 operator role transition, (6) network / firewall / Active Directory cleanup, and (7) a tamper-evident certificate of decommissioning that satisfies internal audit, ISO 27001 and SOC 2 record-disposal reviewers.
The decommissioning planning conversation should start the moment your replacement system (Oracle Fusion, NetSuite, SAP S/4HANA or whatever the chosen target is) hits steady-state operation — typically 3–6 months after the new system go-live. Earlier than that you risk forcing decommissioning before issues with the new system are discovered; later than that you start paying overlap costs (two ERPs live, two sets of licences, two operational teams) for no business value. Common Infor LX (BPCS) decommissioning triggers: the live operational workload has fully moved to the new ERP and BPCS gets <10 daily transactions, the IBM i Power hardware is due for a refresh and finance is questioning the spend, the Infor LX support contract is up for renewal, or M&A activity creates an orphan BPCS instance with no operational future.
Critically — this is the audit-grade core of any Infor LX (BPCS) decommissioning. Before the AS/400 is powered down, Syntra ETL captures: every BPCS audit-trail file (GLAT for GL, APAT for AP, RAAT for AR, IIAT for inventory, MHAT for manufacturing) in both original EBCDIC form and converted UTF-8 form, every IBM i database journal (QSQJRN) entry for the full retention period with user / terminal / timestamp preserved, the BPCS file metadata catalogue (field definitions, CCSID, packed-decimal precision), and optionally a snapshot of the RPG / COBOL source code for FDA 21 CFR Part 11 pharma customers who need batch-record forensic reconstruction capability decades later. The evidence pack is signed with a customer-controlled KMS key and lockable to WORM (S3 Object Lock / Azure Blob Immutability in compliance mode).
Material cost lines that can be cancelled or downgraded post-Infor LX (BPCS) decommissioning: IBM Software Maintenance Agreement (SWMA) for the IBM i operating system (typically $20K–$80K per year per server), IBM Power Hardware Maintenance Agreement (HWMA) for the Power9 / Power10 server ($10K–$40K per year), IBM PowerVM virtualisation licence, IBM DB2 for i included licence, plus any associated products (Backup Recovery and Media Services, Performance Tools, Application Runtime Expert). Infor side: Infor LX support / maintenance subscription ($30K–$150K per year), Infor LX module add-ons, any Infor ION middleware licences. Plus colocation / data-centre charges for on-prem AS/400 customers, power, cooling and rack-space. Typical aggregate annual saving: $80K–$400K per IBM i LPAR.
Multi-LPAR (separate IBM i partitions for prod, QA, dev) and multi-site (separate AS/400 servers at different physical sites) configurations are decommissioned in a phased sequence. Typical order: dev LPARs first (lowest risk, often months ahead of production), QA LPARs second (after the parallel-run validation has signed off), production LPARs last (after the final cutover and a minimum 90-day stability window on the replacement system). For multi-site customers (manufacturing plants with local AS/400s), each site is decommissioned independently following the same workflow — Syntra ETL's extractor runs against each LPAR in parallel so the cloud archive consolidates data across all sites into a unified historical-reporting view.
Role transition is one of the most underestimated parts of any Infor LX (BPCS) decommissioning. RPG IV / III developers, COBOL developers, CL programmers and AS/400 operators are typically long-tenured staff with deep institutional knowledge. The decommissioning workflow handles them in three ways: (1) deliberate knowledge capture during the archive load (RPG source-code snapshot, documentation walkthroughs, customisation inventory written down for the audit evidence pack), (2) staged role transition with sufficient overlap (typically 3–6 months) for the developer / operator to onboard the new ERP team and the cloud-archive operations role, (3) honest retention or redundancy planning with HR — some staff move into the replacement system roles, some retire, some take redundancy. Skipping this step risks losing tacit knowledge that auditors will eventually ask for.
ISO 27001 control A.8.10 (information deletion), SOC 2 confidentiality / processing-integrity criteria, and SOX 404 (records management) all require that record disposal be documented, governed and reversible only by exception. The Infor LX (BPCS) decommissioning workflow produces a tamper-evident certificate of decommissioning: timestamped record of every BPCS file captured to the cloud archive, hash signatures proving data integrity at capture, IAM and KMS access policy showing who can read the archive post-decommissioning, IBM i LPAR shutdown log signed by the operator who performed it, hardware disposal certificate (drive shred / NIST 800-88 wipe certificate for on-prem servers). Reviewer-ready for ISO 27001, SOC 2, SOX and any industry-specific record-disposal regulation.
Complete decommissioning is the goal — and is achievable when the cloud archive is constructed properly. The standard pattern: archive load and validation complete (12–14 weeks typical), 90-day stability window with the IBM i in read-only mode while the cloud archive is exercised by finance / tax / audit users, formal sign-off from finance / compliance / IT, then IBM i Power LPAR powered down. Hardware is either disposed (NIST 800-88 wipe certificate retained for audit evidence), redeployed for non-BPCS workload, or sold to a used-IBM-i broker (a small recovery sometimes worth pursuing). Customers who try to keep the IBM i 'around just in case' almost always end up with technical-debt creep — staff leave, the hardware ages, the IBM i licence costs continue. Cleaner to decommission once the archive is validated.
30-minute call. Walk through your IBM i landscape, contract renewal calendar, RPG / AS/400 staffing and audit-evidence requirements — leave with a concrete Infor LX (BPCS) decommissioning plan, a 12–14 week schedule and a quantified annual saving target.