Infor System21 on IBM i: an ERPNext migration path for UK food and distribution firms

Short answer

There is no public end-of-support date for Infor System21, so this guide gives none. Infor’s own System21 page still sells the product, names System21 3.2 as current, and offers it on-premises on IBM i or as a cloud service. The pressure on older sites comes from elsewhere: an independent System21 support provider says customers on Aurora 2.4 or earlier were told they would lose mainstream support after Aurora 3.1 was released. Under Infor’s published lifecycle policy, life after mainstream means no new fixes or regulatory updates. If you are a UK food, drink or distribution business on an old Aurora release, your real choices are an upgrade to 3.2, staying put with third-party support, or leaving IBM i. ERPNext (open source, GPL-3.0, no licence fee) is a credible destination for distributors and simpler food producers, but be honest about the gaps: we found no EDI module, no catch-weight handling and no excise or bonded-warehouse features in its documentation. Infor is quote-only, so we give no Infor estimate.

Choosing a platform? Get a free 30-minute advisory call.

Who this guide is for

This guide is for finance directors, operations directors and IT managers at UK food, drink and distribution businesses that run Infor System21, often still called by its release names, JBA System 21 or Aurora, on IBM i. The typical site has run System21 for twenty years or more, trades with the big grocery retailers and wholesalers over EDI, tracks lots for recall, and depends on one or two people who know the IBM i and the RPG modifications built up over the years.

Infor’s Infor System21 product page describes the product’s reach: core ERP for manufacturing, distribution and service businesses, with industry functions for “food and alcoholic beverage production with supply and logistics, FMCG/CPG, discrete, automotive, process manufacturing, and pure distribution and equipment servicing businesses”, used in more than 50 countries.

We implement ERPNext, so read our view with that in mind. For many System21 sites, upgrading to 3.2 is the right answer, especially where the IBM i team is healthy and the business depends on System21’s food and logistics functions. This guide is for the sites where the release is old, the platform skills are thinning, and the board wants a real alternative priced before signing another long commitment.

It is part of our series on legacy ERP deadlines; the legacy ERP end-of-support hub lists every vendor date we have confirmed. Other IBM i guides in the series: Infor LX and BPCS, Infor XA (MAPICS) and JD Edwards World.

Sources, checked on Nov 21, 2026: the Infor System21 product page, the Infor General Product Lifecycle Policy (PDF on infor.com), the Total e Solutions System21 and Aurora support page (independent support provider), the Frappe Cloud pricing page and Frappe Cloud server plans page, the ERPNext repository on GitHub and the ERPNext documentation linked in each section.

What is actually known about System21 support

System21 dates get repeated in sales conversations without sources. Here is what we could actually find:

SourceWhat it saysHow much weight to give it
Infor System21 product pageSystem21 is “available either on-premises or as a cloud-based service”, with “identical functionality” in both. It is “based on the IBM i platform”. The page describes System21 3.2, released alongside Release 10 of the Infor Development Framework (IDF), and a browser interface, System i Workspace AnyWhere, written in HTML5Infor’s own page: high. The product is current and on sale
Infor General Product Lifecycle Policy (PDF on infor.com)Defines Mainstream, Extended and Sustaining Maintenance for Infor products. Product-specific lifecycle policies carry the dates, and Infor “will typically provide notice” of a mainstream end date one year in advanceInfor’s own policy: high, but it contains no System21 dates
Total e Solutions System21 and Aurora support page (independent support provider)An independent support provider writes: “If you have been informed that due to the release of Aurora version 3.1, you will no longer receive mainstream support, if your organisation is using Aurora 2.4 version or earlier, then look no further.” It offers legacy support for JBA System 21 and Aurora releasesPartner source: useful context, not confirmation. It also sells the alternative to upgrading

We could not find a public System21 product lifecycle policy on infor.com, so we give no end-of-maintenance date for any System21 or Aurora release. If you are an Infor customer, ask your Infor account manager for the current System21 lifecycle policy in writing, or look for it in the Infor support portal. That document, together with your maintenance contract, is what counts.

What we can say safely

System21 3.2 is Infor’s current release, sold on IBM i and in the cloud. If you run Aurora 2.4 or earlier, an independent support provider says Infor customers on those releases were told mainstream support would end once 3.1 was out. Confirm your exact status with Infor before you plan around it, and do not treat any date you hear without a document as fact.

Get a tailored shortlist and pricing review

Share your work email and we'll send you a replacement shortlist and cost review tailored to your user count and requirements. A member of our ERP team prepares it personally.

What life after mainstream maintenance means under Infor’s policy

Infor’s Infor General Product Lifecycle Policy (PDF on infor.com) sets out three stages that apply to every release:

StageWhat you getWhat you do not get
Mainstream MaintenancePriority 1 and 2 fixes, updates, and regulatory and statutory enhancements for released localisations; Infor Support Portal and support staff—
Extended Maintenance (when available, for an additional fee)Many of the benefits of Mainstream; fixes only as needed to resolve Severity 1 incidentsUpdates and most fixes
Sustaining MaintenanceAccess to pre-existing fixes, the knowledge base, the portal and support staff, for a period Infor determines; may carry an additional fee at Infor’s discretion“Any new updates and fixes”

For a UK business on an old Aurora release, the practical meaning is this: the system keeps running and you can still raise calls, but nothing new is being built for your release. That matters most for tax and statutory changes, for certification on newer IBM i operating system releases, and for fixes to defects found after your release moved out of mainstream.

Independent providers such as Total e Solutions System21 and Aurora support page (independent support provider) offer an alternative: monthly third-party support for older releases, including bespoke programs, EDI and IBM i operations. That can be a sensible bridge while you plan, but it does not change the underlying position. Your release will not get new statutory updates from Infor.

Your four options

OptionWhat it involvesBest when
Upgrade to System21 3.2 on IBM iStay on the platform; Infor or a System21 partner upgrades and retrofits modificationsYour IBM i team is healthy, the food and logistics functions are core, and modifications still earn their keep
Move System21 to Infor’s cloud serviceInfor says System21 is available as a cloud service with identical functionality; ask what that means for your modifications and interfacesYou want Infor to run the platform and keep the same application
Stay on your release with third-party supportKeep running; an independent provider supports the application and IBM iShort to medium term, while you plan a move
Leave IBM i for ERPNextOpen-source ERP on Linux with MariaDB; self-hosted or on Frappe CloudRPG skills are retiring, modifications are mostly reports and interfaces, and the fit tests below pass

Infor does not publish System21 licence, maintenance or cloud prices on the pages we checked, so we give no Infor estimate. Ask for written quotes for a 3.2 upgrade and for the cloud service, ask your third-party provider for its fee in writing, and compare all three with an ERPNext proposal over five years.

UK food and drink: the fit tests that matter

UK food and drink producers and wholesalers live by retailer requirements: EDI orders and invoices, lot traceability for recalls, shelf-life rules, quality checks on intake, and promotions agreed with each customer. These are the tests to run before anything else.

RequirementIn ERPNextFit
Lot (batch) control with expiry datesBatches carry expiry dates and show “Expired” after them; a batch number is required on every stock transaction for a batched item (ERPNext Batch documentation; ERPNext Serial and Batch Bundle documentation)Good
Pick the right lot for despatchPick Lists select warehouses on a first-in-first-out basis, with different handling for batched items (ERPNext Pick List documentation)Good; test against your retailers’ minimum-life rules
Intake and despatch quality checksQuality Inspection on purchase receipts and delivery notes; submission is blocked until the inspection is done when enabled on the item (ERPNext Quality Inspection documentation)Good for inspection; test your hold and release process
Non-conformance and corrective actionsNon Conformance records against a quality procedure, with corrective and preventive actions (ERPNext Non Conformance documentation)Basic; check it meets your BRCGS or customer audit needs
Recipes, yield and process lossBill of Materials with scrap percentages; a scrap item identical to the product is treated as process loss (ERPNext Bill of Materials documentation)Good for fixed recipes
Customer price agreements and promotionsPrice Lists, Item Prices and Pricing Rules (ERPNext Price Lists documentation; ERPNext Item Price documentation; ERPNext Pricing Rule documentation)Good; load your real retailer deals in the trial
Long-term supply agreementsBlanket Orders for agreed quantities and rates over a period (ERPNext Blanket Order documentation)Good
Retailer EDI (orders, ASNs, invoices)We found no EDI module in ERPNext’s documentationGap: plan an EDI provider and an integration
Catch weight (variable-weight items)UOM conversion factors are set up in advance (ERPNext UOM documentation); we found no catch-weight handlingGap for meat, fish, cheese and similar lines
Alcohol duty and bonded warehousesWe found no excise or duty-suspended warehouse handlingGap for drinks producers holding stock under bond

Do the gaps first

If EDI volume is high, catch weight is core, or you hold stock under bond, these are not small customisations. Price them as separate workstreams, or keep the specialist function in a dedicated tool, before you compare totals with a System21 upgrade.

Distribution and warehouse fit

Many System21 sites are distributors or food wholesalers rather than producers. For them the fit is usually stronger.

In System21In ERPNextNotes
Item master, depots and warehousesItems (ERPNext Item documentation) and Warehouses (ERPNext Warehouse documentation), including group warehousesDecide how depots map to warehouses or companies
Putaway by locationPutaway Rules assign incoming stock to warehouses per item (ERPNext Putaway Rule documentation)Bin-level directed putaway needs testing
Order captureQuotations and Sales Orders (ERPNext Quotation documentation; ERPNext Sales Order documentation)Test a telesales morning with real order volumes
ReplenishmentReorder levels that raise material requests automatically (ERPNext reorder level (auto material request) documentation)Load real reorder levels per warehouse
Purchasing and importsPurchase Orders, Purchase Receipts and Landed Cost Vouchers for freight and duty (ERPNext Purchase Order documentation; ERPNext Purchase Receipt documentation; ERPNext Landed Cost Voucher documentation)Good
Delivery routesDelivery Trips for multi-drop vehicle runs; Shipments for carrier tracking (ERPNext Delivery Trip documentation; ERPNext Shipment documentation)No route optimisation; keep your routing tool if you have one
Multi-company, multi-currency financeInter-company invoices, multi-currency accounting and accounting dimensions (ERPNext inter-company invoices documentation; ERPNext multi-currency accounting documentation; ERPNext accounting dimensions documentation)Infor highlights multiple companies and currencies in one database; ERPNext supports multiple companies in one site

If you run a separate warehouse management system on the IBM i, or Infor’s WMS, treat it as its own decision. ERPNext’s warehouse functions are solid for stock, lots and picking, but they are not a full WMS with labour management or wave planning.

The IBM i skills question

For most System21 sites the decision is less about software features and more about people and platform. Ask three questions honestly:

  • Who maintains the RPG and the IBM i today, and when do they plan to retire? If the answer is one or two people, that is a business continuity risk whichever option you choose.
  • What do your modifications actually do? List every modified program and sort it into reports and extracts, interfaces, screen changes, and real business logic. Reports and interfaces are easy to replace on any platform. Business logic is where the effort is.
  • What else runs on the IBM i? EDI translation, payroll, warehouse systems and custom applications on the same machine change the economics of leaving it.

System21 has its own customisation tools: Infor says 3.2 ships with Release 10 of the Infor Development Framework for enquiries and custom applications. If much of your bespoke work lives there, check whether it is still needed. Sites that have kept their modifications modest have a much easier decision in either direction.

Getting data off IBM i

System21 data lives in DB2 for i files. It can be read over ODBC or JDBC, or copied to CSV with standard IBM i tools, so extraction is rarely the hard part. The hard part is cleaning decades of item, customer and supplier records and deciding what not to move.

System21 dataERPNext targetHow
Items, units, customers, suppliersItems, UOM conversions, Customers (ERPNext Customer documentation), Suppliers (ERPNext Supplier documentation)Extract, clean, load with Data Import (ERPNext Data Import documentation)
Active recipes and BOMsBills of Materials (multi-level ones with the ERPNext BOM Creator documentation)Only products you will make again
Lot-controlled stock with expiryStock Reconciliation with batches (ERPNext Stock Reconciliation documentation)Count and verify lots and dates before go-live
Customer price agreementsPrice Lists, Item Prices, Pricing RulesLoad current agreements only
Open sales and purchase ordersSales Orders, Purchase OrdersFreeze during cut-over
Open AR and APOpening invoices (ERPNext opening balance documentation)Reconcile to aged debtor and creditor reports
GL balancesOpening trial balance on a new chart of accounts (ERPNext Chart of Accounts documentation)Keep System21 read-only for history

Keep a read-only copy of the System21 data available for lot traceability history, retailer audits and recall investigations. Agree the retention period with your technical manager before you start, because the people asking will be auditors and retailers, not your own staff.

Run a mock recall before go-live: pick one raw-material lot and trace it forward to every customer delivery in ERPNext using the ERPNext Stock Ledger documentation and batch records. If your team cannot do it quickly, fix the process before you switch.

A phased plan for leaving System21

PhaseWhat happensTypical output
1. DiscoveryConfirm your release and maintenance status with Infor in writing; list modifications, interfaces, EDI partners and everything else on the IBM iStatus letter, modification and interface inventory
2. Fit testsLots and expiry, quality checks, retailer pricing, EDI, catch weight and a month end in an ERPNext trialPass, configure or develop, per test
3. Quotes3.2 upgrade and cloud quotes from Infor; third-party support quote; ERPNext proposal with the same scopeFive-year comparison
4. BuildConfigure ERPNext, connect the EDI provider, rebuild the reports you kept, load test data twiceSigned-off test cycles, including a mock recall
5. Cut-overGo live at a period end, ideally outside your peak trading season; System21 read-onlyLive ERPNext, archived System21

For food businesses, avoid going live in the weeks before Christmas or any other peak. Retailers will not accept late or wrong EDI invoices because you changed systems.

Costs: what is published

ItemUSD (published)GBPSource
Infor System21 upgrade, maintenance, cloud serviceQuote only; no estimate givenQuote onlyInfor System21 product page
Third-party System21 supportQuote only (monthly fee)Quote onlyTotal e Solutions System21 and Aurora support page (independent support provider)
ERPNext softwareNo licence fee (GPL-3.0)No licence feeERPNext repository on GitHub
ERPNext on Frappe Cloud, site plansFrom $5 per monthAbout £3.81 (indicative)Frappe Cloud pricing page
ERPNext on Frappe Cloud, dedicated serversFrom $40 per monthAbout £30.49 (indicative)Frappe Cloud server plans page

Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.81) and servers from $40 a month (about £30.49), checked on Nov 21, 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.3119 per £1 for 19 Nov 2026, the latest published figure when we checked on Nov 21, 2026. They are not official UK prices: Frappe does not publish a GBP list price for these plans, and your invoice currency, rate and VAT treatment may differ.

Put IBM i hardware, operating system support, RPG staffing and any EDI service in the “stay” column, and implementation, the EDI integration, data work and retraining in the “move” column. Those lines usually outweigh software and hosting on both sides. A food producer with heavy catch weight or bonded stock should add the cost of closing those gaps before comparing.

Decision table

If this is true for youLean towardsWhy
Healthy IBM i team, deep food-specific modificationsSystem21 3.2 upgradeKeeps the investment and the skills working
Want Infor to run the platform, same applicationInfor’s System21 cloud serviceInfor says functionality is identical to on-premises
Need time, not a decisionThird-party support as a bridgeMonthly terms buy time to plan; no new Infor updates
Distributor or wholesaler, RPG skills retiringERPNext worth pricingStrong fit for stock, lots, pricing and finance
Catch weight, bonded stock or very high EDI volumes are coreSystem21, or ERPNext plus specialist toolsWe found no native ERPNext support for these

Best for, and wrong choice when

ERPNext is best for

UK distributors, food wholesalers and simpler food producers on old System21 or Aurora releases whose IBM i skills are retiring, whose modifications are mostly reports and interfaces, and who can connect an EDI provider.

A System21 3.2 upgrade is best for

Sites with a healthy IBM i team, heavy use of System21’s food and logistics functions, and modifications that still earn their keep.

ERPNext is the wrong choice when

Catch weight, duty-suspended stock or complex retailer EDI are central and untested, you need a go-live within a few months, or nobody can own the new system after the project.

Want a second opinion before you commit? Our ERP Engineering practice runs fit tests like the ones above on your own data, and we will tell you if a System21 upgrade is the better answer.

Frequently asked questions

When does Infor System21 support end?

We found no public Infor date for any System21 or Aurora release, so we give none. Infor still sells System21 3.2 on IBM i and as a cloud service. Ask Infor for the System21 lifecycle policy in writing (checked Nov 21, 2026).

Is Aurora 2.4 still supported?

An independent support provider says customers on Aurora 2.4 or earlier were told they would lose mainstream support after Aurora 3.1 was released. Under Infor’s general policy, that means no new fixes or regulatory updates. Confirm your status with Infor.

What is the latest System21 release?

Infor’s System21 page describes System21 3.2, released alongside Release 10 of the Infor Development Framework (checked Nov 21, 2026).

Can ERPNext handle UK food traceability?

For lots, expiry dates, quality inspections and recall tracing, yes. We found no EDI module, catch-weight handling or bonded-warehouse features in its documentation, so treat those as gaps to close.

How do we get data out of System21 on IBM i?

System21 data is in DB2 for i and can be read over ODBC or JDBC or exported to CSV. Clean it, then load masters and open items into ERPNext with Data Import.

What does ERPNext cost?

No licence fee (GPL-3.0). Frappe Cloud lists site plans from $5 a month and servers from $40 a month (about £3.81 and £30.49 at the Bank of England rate for Nov 19, 2026; checked Nov 21, 2026). Implementation is separate. Infor is quote-only.

Still running System21 or Aurora on IBM i?

We take a sample of your items, lots, customer price agreements and EDI orders off IBM i and rebuild them in ERPNext, so you can compare a working fit test with an upgrade quote.

We'll get back to you shortly. We use your details only to reply to this request.