Infor XA (MAPICS) 9.2 end of maintenance: leaving IBM i for ERPNext as a mid-size manufacturer
Short answer
Several Infor partners report that Infor XA Release 9.2 has reached end of maintenance, with new defect fixes delivered only on Releases 10 and 11 and an upgrade to Release 10 as Infor’s recommended next step. Infor has not published a public notice we could find: its own XA service pack list (published Oct 14, 2026) still shows 9.2 under “currently supported releases” and points to an XA life cycle policy article that sits behind Infor’s customer sign-in (checked Nov 14, 2026). So confirm your status with Infor in writing before you plan around any date. If you are a mid-size discrete manufacturer on IBM i, the real decision is bigger than a support date. Upgrading to XA 10 keeps your processes and your platform, and is the lowest-risk move if you can still staff RPG and IBM i. Leaving IBM i for ERPNext makes sense when your RPG skills are retiring, your customisations are mostly reports and interfaces, and you want an open-source ERP with no licence fee (GPL-3.0). Infor XA pricing is quote-only, so we give no estimate.
Contents
- Who this guide is for
- What is actually known about XA 9.2
- The real decision: XA 10 on IBM i, or leave the platform
- Step one: the RPG customisation inventory
- Where ERPNext fits a mid-size discrete manufacturer
- Getting data off IBM i
- A phased plan for leaving XA
- Cost: what you can and cannot compare
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for CFOs, IT directors and operations leaders at discrete manufacturers, typically 100 to 1,000 people, who run Infor XA (still called MAPICS by many long-time users) on IBM i. XA has run your planning, shop floor, inventory and financials for years. The questions on the table now are whether to upgrade within XA, and whether you still want to be an IBM i shop in five years.
We implement ERPNext, which runs on Linux with MariaDB, so leaving IBM i is part of any move to us. We also think an XA upgrade is the right answer for many manufacturers, and this guide says where. Our aim is to give you a way to decide based on your customisations and your people, not on a sales deck.
It is part of our series on legacy ERP deadlines; see the legacy ERP end-of-support hub for every date we have confirmed (and the ones we could not). If you also run JD Edwards World on IBM i elsewhere in the group, read our JD Edwards World guide alongside this one.
Sources, checked on Nov 14, 2026: the Infor XA product page and the Infor XA SBCS Service Pack List and Migration Tool Information (PDF, Oct 14, 2026) (Infor-owned); the ISE (Infor partner) article on XA 9.2 (partner, not Infor); the Frappe Cloud pricing page, ERPNext repository on GitHub and the ERPNext documentation linked in each section.
What we do not do here
We do not state an Infor end-of-maintenance date, because the only dated statements we found are from partners. We do not estimate XA upgrade, Infor subscription, IBM i hardware or implementation costs: Infor XA is quote-only, and any number we gave would be invented.
What is actually known about XA 9.2
| Statement | Who says it | How much weight to give it |
|---|---|---|
| XA 9.2 has reached end of maintenance; new defect fixes only on Releases 10 and 11; Infor encourages an upgrade to Release 10 | Infor partners, for example ISE (Infor partner) article on XA 9.2 | Useful signal, but not an Infor document. Partners also sell upgrades |
| XA service pack list shows 10.0.x and 9.2.x under “Currently supported releases”; 9.1.x and earlier under “no longer supported” | Infor, Infor XA SBCS Service Pack List and Migration Tool Information (PDF, Oct 14, 2026) | Infor-owned, but it is a service pack list, not a support notice, and may lag policy changes |
| The XA life cycle and fix policy is in knowledge base article KB1465430 | Infor, same PDF | Behind Infor’s customer sign-in; ask your Infor contact for a copy |
| Migration tools exist from 9.x to Release 10 (PTF SH16226) and from 10.x to Release 11 (SH16296) | Infor, same PDF | Confirms the upgrade path Infor supports |
| The latest 9.2 service pack listed is 9.2.2.3, dated Nov 25, 2021; the latest Release 10 service pack listed is 10.0.1.4, dated May 28, 2026 | Infor, same PDF | Shows where Infor’s fix effort has gone |
So the honest status is: partners report end of maintenance for 9.2; Infor has not published a public notice we could find; and Infor’s own public material shows that new service packs have been going to Release 10 for some years. Before you plan around a date, ask Infor to confirm in writing what your maintenance agreement covers for 9.2 today, including defect fixes, security fixes and regulatory changes.
Infor’s product page describes XA as ERP for discrete manufacturers running on IBM Power, with deployment options that include mixed cloud and on-premises. Release 10 and Release 11 are where Infor is investing; XA itself is not being retired.
The real decision: XA 10 on IBM i, or leave the platform
An XA 9.2 to 10 upgrade is a same-vendor upgrade with an Infor migration tool. It keeps your data model, your processes and your IBM i platform. For a manufacturer with a healthy IBM i team, that is usually the cheapest safe path, and we would not argue otherwise.
The case for leaving rests on two questions that a support date does not answer:
1. Who will maintain your IBM i and RPG estate in five years?
Many XA sites depend on one or two people who know the RPG modifications, the CL job streams and the green-screen workarounds. Some are near retirement. We are not going to quote a statistic on IBM i skills, because we have not seen one we trust; you already know your own bench strength. Write down, by name, who can change an XA program today, and who could do it in 2030. If the second list is empty, an XA upgrade buys time but does not fix the risk.
2. How much of your XA is really XA?
Over decades, many XA sites accumulate modified programs, custom files and interfaces. Some of that is business-critical logic. Much of it is reports, extracts and integrations that any modern system can replace. You cannot decide sensibly until you know which is which. That is the customisation inventory below, and it is the single most useful piece of work you can do this quarter, whichever way you go.
| Your situation | Lean towards |
|---|---|
| Strong in-house IBM i and RPG team, few modifications, happy with XA processes | Upgrade to XA 10 (then plan Release 11) |
| Heavy modifications in planning or costing logic that only XA-skilled staff understand | Upgrade to XA 10 first; replace later with a full rebuild plan |
| Shrinking IBM i skills; modifications mostly reports, extracts and interfaces | Price ERPNext alongside the upgrade |
| Corporate push to retire IBM i hardware or move infrastructure to cloud | Price ERPNext alongside the upgrade |
Step one: the RPG customisation inventory
Do this before you speak to any vendor. It takes a small team two to four weeks and tells you what an XA upgrade will have to retest and what any replacement will have to rebuild.
What to list
Inventory checklist
- Every modified XA program and every custom program in your libraries, with the source member and the last change date.
- Usage: whether each object has been used recently. On IBM i, object descriptions (for example DSPOBJD with service detail) record a last-used date and a days-used count.
- Files and fields each custom program reads or updates (DSPPGMREF lists the files a program references).
- Custom database files and logical files, and what fills them.
- Batch job streams and CL programs, with their schedule and dependencies.
- Interfaces in and out: EDI, carriers, banks, payroll, shop-floor data collection, quality systems, spreadsheets that read XA data.
- Reports and queries: who reads each one, and how often.
How to classify each item
| Class | Typical examples | What happens in an XA upgrade | What happens in ERPNext |
|---|---|---|---|
| A. Unused | Programs not used for years, obsolete reports | Remove before upgrading | Not rebuilt |
| B. Reports and queries | Custom listings, management reports, query extracts | Retest | Rebuilt as ERPNext reports, query reports or print formats |
| C. Interfaces | EDI, bank, carrier, payroll, data collection | Retest; may need changes for Release 10 | Rebuilt on the REST API or integration tools |
| D. Process extensions | Extra validation, custom screens, additional fields | Retest and possibly refit | Configuration, custom fields, scripts or a custom app |
| E. Core logic changes | Modified planning, costing or allocation logic | Highest risk; needs XA-skilled staff | Highest risk; needs a design that may change the process |
A rough rule from our experience: if most of your list is A, B and C, a move to ERPNext is a manageable project. If you have a long list of E items, either budget seriously for redesign or upgrade XA first and revisit later. These are judgements, not statistics: count your own list.
Where ERPNext fits a mid-size discrete manufacturer
ERPNext is open source under GPL-3.0, with manufacturing, stock, buying, selling and accounting on one database. For a former MAPICS shop, these are the features that matter, from the ERPNext documentation:
| Typical XA area | ERPNext feature | Documentation |
|---|---|---|
| Item master | Item, with variants where you have options | ERPNext Item documentation, ERPNext Item Variants documentation |
| Product structures (bills of material) | Multi-level BOM with sub-assemblies and scrap | ERPNext Bill of Materials documentation |
| Routings and work centres | Routing and Workstation | ERPNext Routing documentation, ERPNext Workstation documentation |
| Master scheduling and material planning | Production Plan, which creates work orders for finished goods and sub-assemblies and material requests for raw materials | ERPNext Production Plan documentation, ERPNext Material Request documentation |
| Manufacturing orders and shop floor | Work Order and Job Card (operations, time, quantities) | ERPNext Work Order documentation, ERPNext Job Card documentation |
| Outside operations | Subcontracting | ERPNext subcontracting documentation |
| Inventory, lots and serials | Warehouses, Stock Entry, Batch and Serial No | ERPNext Warehouse documentation, ERPNext Stock Entry documentation, ERPNext Batch documentation, ERPNext Serial No documentation |
| Purchasing | Material Request and Purchase Order | ERPNext Purchase Order documentation |
| Customer orders | Sales Order, Pick List, Delivery Note | ERPNext Sales Order documentation, ERPNext Pick List documentation |
| Quality | Quality Inspection: incoming, in-process and outgoing | ERPNext Quality Inspection documentation |
| Financials and cost reporting | Chart of accounts, cost centers, accounting dimensions, multi-currency | ERPNext accounting dimensions documentation, ERPNext multi-currency accounting documentation |
Where XA may still be stronger
- Decades of tuning to your plant. Your XA configuration reflects years of decisions; ERPNext starts from a standard model, and that is both a benefit and a cost.
- High-volume, complex planning. If you run very large MRP regenerations across many plants with heavy capacity planning, test ERPNext’s Production Plan on your real volumes before deciding.
- Platform stability. IBM i is famously stable and low-maintenance once tuned. A Linux and MariaDB stack needs its own operations discipline, whether you self-host or use a managed host.
Getting data off IBM i
XA data lives in Db2 for i. Extraction is not the hard part: you can read the files over ODBC or JDBC with IBM’s client tools, or copy them to CSV on the system. The hard part is meaning. MAPICS-era files use packed decimals, date formats that vary by file, status codes and flags whose meaning lives in someone’s head, and custom files added over the years.
| Data | Approach in ERPNext | Notes |
|---|---|---|
| Items, customers, suppliers | Data Import templates (ERPNext Data Import documentation) | Clean and de-duplicate first; decide new item naming rules |
| Bills of material and routings | BOMs and routings loaded by import or script, then validated | Compare costed BOMs against XA for a sample of items |
| Open sales and purchase orders | Loaded as open orders at cutover | Agree a cut-off: close what you can before go-live |
| Open manufacturing orders | Usually finished in XA, or re-created as work orders | Avoid migrating half-complete work in progress if you can |
| Stock on hand | Stock Reconciliation per warehouse, with lots and serials (ERPNext Stock Reconciliation documentation) | Physical count at cutover is the safest basis |
| Open AR and AP, balances | Opening invoices and an opening journal (ERPNext opening balance documentation) | Reconcile to the penny |
| History | Keep XA read-only, or extract to a reporting database | Do not migrate years of transactions |
A phased plan for leaving XA
| Phase | Work | Done when |
|---|---|---|
| Inventory (2–4 weeks) | The RPG customisation inventory above, plus Infor’s written confirmation of your 9.2 support status | Classified list; a decision on whether to price ERPNext at all |
| Pilot (6–8 weeks) | One product family: items, BOMs, routings, a month of orders, a planning run, work orders and costing | Costed BOMs and planning results explainable against XA |
| Design (6–8 weeks) | Every class C, D and E item has a design; interfaces specified | Signed scope and an XA upgrade quote alongside |
| Build (4–8 months) | Configuration, reports, interfaces, custom apps, data scripts | User acceptance by planning, shop floor, purchasing and finance |
| Dress rehearsals (2–3) | Full trial migrations and a parallel planning run | Stock, open orders and balances agree with XA |
| Cutover (period end) | Physical count, final load, go live | First month closed in ERPNext |
These are planning ranges from projects of this size, not a quote. If your 9.2 support status is uncertain, consider the sequence many manufacturers use: secure a short, defined support position with Infor, run the inventory and pilot, and only then commit to either the XA upgrade or the move.
Cost: what you can and cannot compare
| Item | Upgrade to XA 10 or 11 | Move to ERPNext |
|---|---|---|
| Software | Quote-only (Infor does not publish XA prices) | No licence fee (GPL-3.0) |
| Platform | IBM i hardware and operating system, quote-only | Frappe Cloud sites from $5 / month, servers from $40 / month, or self-host on Linux |
| Upgrade or implementation | Infor or partner quote; retest of modifications | Partner quote; rebuild of classes B to E |
| Skills | IBM i and RPG staff or a partner | Python and Frappe developers, plus ERPNext functional consultants |
Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.78) and servers from $40 a month (about £30.22), checked on Nov 14, 2026. The GBP figures are indicative conversions, not Frappe prices.
Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3238 per £1 for 12 Nov 2026, the latest published figure when we checked on Nov 14, 2026. They are not official UK prices: the vendor does not publish a GBP list price for these items, and your invoice currency, rate and VAT treatment may differ.
We cannot put numbers on the left-hand column because Infor publishes none, and we will not estimate them. The fair comparison is two written proposals on the same scope, over five years, including the people you need to keep each platform running.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| Strong IBM i team, few modifications, processes still fit | XA 10 upgrade | Same vendor, Infor migration tool, lowest disruption |
| Many class E modifications in planning or costing | XA 10 upgrade first | Replacing core logic needs time and design |
| IBM i skills retiring, modifications mostly reports and interfaces | ERPNext (price both) | Rebuildable scope; no licence fee; mainstream skills |
| Company policy to exit IBM i hardware | ERPNext (price both) | Runs on standard Linux, self-hosted or managed |
| You need to act within months | XA 10 upgrade | A replacement needs a pilot and dress rehearsals |
Best for, and wrong choice when
ERPNext is best for
Mid-size discrete manufacturers on XA whose IBM i skills are thinning, whose customisations are mostly reports and interfaces, and who want to leave proprietary hardware for an open-source ERP on standard infrastructure.
An XA 10 upgrade is best for
Manufacturers with a capable IBM i team, few core modifications and processes that still fit, who want the lowest-risk way to stay on supported software.
ERPNext is the wrong choice when
Your competitive edge sits in heavily modified XA planning or costing logic, you cannot spare planners and engineers for a pilot, or you need a solution within a few months.
Frequently asked questions
Has Infor XA 9.2 reached end of maintenance?
Infor partners report that it has, with new defect fixes only on Releases 10 and 11. Infor has not published a public notice we could find, and its own service pack list (Oct 14, 2026) still lists 9.2 under currently supported releases. Confirm your status with Infor in writing (checked Nov 14, 2026).
What is Infor’s upgrade path from XA 9.2?
Infor’s service pack list documents migration tools from 9.x to Release 10 and from 10.x to Release 11. Partners report Infor recommends moving to Release 10 first.
Is Infor XA being discontinued?
We found no sign of that. Infor continues to publish service packs for Release 10 and documentation for Release 11.
Where is the XA life cycle policy?
Infor’s service pack list points to knowledge base article KB1465430 for the XA Life Cycle Policy and Fix Policy. It sits behind Infor’s customer sign-in, so ask your Infor contact for a copy.
Can ERPNext replace XA for a discrete manufacturer?
For many mid-size manufacturers, yes: ERPNext covers items, multi-level BOMs, routings, production planning, work orders, job cards, subcontracting, lots and serials, quality and accounting. Test it on one product family and your real planning volumes first.
How do we get data out of XA?
XA data is in Db2 for i and can be read over ODBC or JDBC or copied to CSV. The work is in understanding and cleaning the files, then loading items, BOMs, routings, open orders, stock and balances into ERPNext.
How much does an XA upgrade or ERPNext cost?
Infor XA pricing is quote-only, so we give no estimate. ERPNext has no licence fee under GPL-3.0; Frappe Cloud lists sites from $5 a month and servers from $40 a month (USD, checked Nov 14, 2026). Implementation is quoted per project.