PeopleSoft Financials 9.1 or earlier: is ERPNext a realistic replacement for education and public sector finance?
Short answer
Oracle’s Lifetime Support Policy (effective Aug 7, 2026) shows PeopleSoft FMS/ESA/SCM 9.1 Premier Support ended Nov 2014 and Extended Support ended Jan 2018; 9.0 ended Sep 2011 and Jun 2015, and 8.9 Aug 2010 and Aug 2013. All are on indefinite Sustaining Support, which excludes new fixes, security alerts and new tax, legal and regulatory updates. PeopleSoft 9.2 is on Continuous Innovation, with Premier Support through at least Dec 2037. For most universities and large public bodies, the realistic paths are an upgrade to 9.2 or a move to Oracle’s cloud ERP. ERPNext (open source, GPL-3.0, no licence fee) is realistic only for finance and procurement in smaller colleges, mid-size public bodies, trading subsidiaries and foundations: general ledger, payables, receivables, purchasing with RFQs, budgets that warn or stop overspend, cost centres and accounting dimensions, fixed assets and approvals. It is not a replacement for Campus Solutions, HCM and payroll, full commitment control with encumbrance ledgers, or grants management.
Contents
- Who this guide is for
- What Oracle’s Lifetime Support Policy shows
- What Sustaining Support means for a public body
- Your three realistic paths
- Where ERPNext fits public sector finance
- The fit limits, stated plainly
- Where ERPNext genuinely fits
- What moves, and what is archived
- A decision plan for the next 90 days
- Questions to ask Oracle and your PeopleSoft partner
- Decision table
- Costs: what is published
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for finance directors, CFOs, IT directors and procurement leads at universities, colleges and mid-size public bodies in the UK and US that still run PeopleSoft Financials and Supply Chain Management (FSCM) on release 9.1 or earlier. In many of these organisations HR and student systems have moved on, while finance sits on an old release that nobody wants to touch.
We implement ERPNext, so read our view with that in mind. We will say up front what we say to every institution that asks: for most universities and large public bodies, ERPNext is not the answer for the whole PeopleSoft estate. It can be the answer for finance and procurement in a smaller institution, or for a subsidiary, trading company or foundation that needs its own books. This guide helps you work out which side of that line you are on.
It is part of our series on legacy ERP systems; the legacy ERP end-of-support hub lists every vendor date we have confirmed. Related guides on Oracle applications: Oracle EBS 12.1, Oracle EBS 11i and JD Edwards 9.1.
Sources, checked on Nov 22, 2026: Oracle Lifetime Support Policy for Applications (PDF, effective Aug 7, 2026), Oracle’s PeopleSoft applications page, Oracle PeopleTools 8.63 documentation, “Understanding Change Assistant for Upgrades”, the Frappe Cloud pricing page, the ERPNext repository on GitHub and the ERPNext documentation linked in each section.
What Oracle’s Lifetime Support Policy shows
All dates below come from Oracle’s Lifetime Support Policy for Applications, effective Aug 7, 2026. Oracle notes that each support stage runs through the last day of the month shown.
| Release | General availability | Premier Support ended | Extended Support ended | Sustaining Support |
|---|---|---|---|---|
| FMS/SCM 8.4 | Mar 2002 | Mar 2007 | Not available | Indefinite |
| FMS/ESA/SCM 8.8 | Dec 2003 | Dec 2008 | Dec 2011 | Indefinite |
| FMS/ESA/SCM 8.9 | Aug 2005 | Aug 2010 | Aug 2013 | Indefinite |
| FMS/ESA/SCM 9.0 | Sep 2006 | Sep 2011 | Jun 2015 | Indefinite |
| FMS/ESA/SCM 9.1 | Nov 2009 | Nov 2014 | Jan 2018 | Indefinite |
| FMS/ESA/SCM 9.2 (Continuous Innovation; latest update 57, GA Jul 2026) | — | Through at least Dec 2037 | Not applicable | Indefinite |
Two details matter for public bodies. First, the policy lists separate 9.1 localisations for Argentina and Brazil with Premier Support to Apr 2028; that does not apply to UK or US institutions. Second, Oracle states that PeopleSoft FMS, ESA and SCM “moved to a Continuous Innovation model with the initial delivery of the 9.2 release”, that new functionality is delivered as updates to the existing release, and that Oracle “currently has no plans to end Premier Support” on Continuous Innovation releases, while reserving the right not to extend the date.
So 9.1 is not going to be switched off. It has simply been eight years since it received anything new.
What Sustaining Support means for a public body
Oracle’s policy describes Sustaining Support as available “for as long as you license your Oracle products”. You keep technical support, My Oracle Support access, and fixes and upgrade scripts created during earlier stages. Sustaining Support does not include:
- New updates, fixes, security alerts, data fixes and critical patch updates
- New tax, legal and regulatory updates
- New upgrade scripts
- Certification with new third-party products or versions, or new Oracle products
- 24-hour response commitments for Severity 1 requests
For a university or public body, the second bullet is the one auditors care about. Any change to tax reporting, supplier payment rules or statutory reporting after Jan 2018 has had to be handled by your own team, a third-party support provider or a manual workaround. The fourth bullet matters for IT: every operating system, database and browser upgrade becomes a question of whether the old stack still runs.
List those workarounds before you choose a path. They are the strongest evidence for the business case, and they are also the first things a new system has to get right.
Your three realistic paths
| Path | What it involves | Best for |
|---|---|---|
| Upgrade to PeopleSoft 9.2 | Oracle’s PeopleTools documentation says application upgrade “only applies to upgrading an older application release to application release 9.2”; after that, PeopleSoft Update Manager applies maintenance and new features. The upgrade uses Change Assistant and a certified Upgrade Source Image as the new-release demo database. Customisations must be retrofitted | Institutions that are happy with PeopleSoft’s depth, have PeopleSoft skills, and run Campus Solutions or HCM on PeopleSoft too |
| Move to Oracle Fusion Cloud ERP | Oracle’s PeopleSoft page offers a route to “Move from PeopleSoft to Oracle Fusion Cloud ERP”. A re-implementation on SaaS | Large institutions that want to leave on-premises and stay with Oracle |
| Replace finance and procurement with ERPNext | A data migration and re-implementation of GL, AP, AR, purchasing, budgets and assets on an open-source ERP; other PeopleSoft pillars stay or move separately | Smaller colleges, mid-size public bodies, subsidiaries, trading companies and foundations with simpler budget control |
Other public-sector ERPs exist and belong on a full shortlist. We compare only the three paths above because this guide is about when ERPNext is, and is not, a credible option.
Where ERPNext fits public sector finance
ERPNext covers the core of what a smaller institution’s finance office does every day. Here is how PeopleSoft concepts land.
| PeopleSoft concept | ERPNext | Fit |
|---|---|---|
| Business units and ledgers | Companies, each with its own chart of accounts (ERPNext Chart of Accounts documentation); inter-company invoices between them (ERPNext inter-company invoices documentation) | Good for a handful of entities |
| ChartFields (department, fund, program, project) | Cost centres (ERPNext Cost Center documentation), projects (ERPNext Project documentation) and custom accounting dimensions on ledger entries (ERPNext accounting dimensions documentation) | Good; design the dimensions before you migrate |
| Payables and vouchers | Purchase Invoices (ERPNext Purchase Invoice documentation) and Payment Entries (ERPNext Payment Entry documentation); tax withholding categories where needed (ERPNext Tax Withholding Category documentation) | Good |
| Receivables and billing | Sales Invoices (ERPNext Sales Invoice documentation), payment terms (ERPNext Payment Terms documentation), dunning for overdue invoices (ERPNext Dunning documentation) | Good for commercial income; not student accounts |
| Requisitions and purchase orders | Material Requests (ERPNext Material Request documentation) and Purchase Orders (ERPNext Purchase Order documentation) | Good |
| Sourcing and quotes | Request for Quotation (ERPNext Request for Quotation documentation) and Supplier Quotation (ERPNext Supplier Quotation documentation); supplier scoring (ERPNext Supplier Scorecard documentation) | Good for routine tenders; not a full e-tendering portal |
| Approvals | Workflows with states and role-based transitions (ERPNext Workflows documentation); value-based authorisation rules (ERPNext Authorization Rule documentation) | Good |
| Budget checking | Budgets against a cost centre, project or accounting dimension that warn or stop when a material request, purchase order or posted expense exceeds the amount (ERPNext Budget documentation) | Partial; see the limits below |
| Asset Management | Assets with categories, locations, depreciation schedules and disposal (ERPNext Asset documentation) | Good for a typical fixed asset register |
| Period close | Period Closing Voucher (ERPNext Period Closing Voucher documentation), fiscal years (ERPNext Fiscal Year documentation) | Good |
| Bank reconciliation | Bank reconciliation tool (ERPNext bank reconciliation documentation) | Good |
ERPNext’s budget documentation describes a budget that compares the approved plan “with commitments and actual expenses” and can warn or stop a buyer at the material request, purchase order or posting stage. For many colleges and mid-size bodies, that is the control they actually use.
The fit limits, stated plainly
These are the reasons ERPNext is the wrong answer for many PeopleSoft sites. Check each one honestly.
| PeopleSoft capability | What we found for ERPNext | Consequence |
|---|---|---|
| Campus Solutions (student records, student financials) | Not in ERPNext’s scope | Out of scope. Your student system stays or moves separately; plan the integration for student income |
| HCM and payroll | Not covered in this guide | Out of scope. Keep payroll where it is and post journals to ERPNext |
| Commitment Control with budget journals, pre-encumbrance and encumbrance ledgers | We found budget checks (warn or stop) but no separate encumbrance ledgers or budget journal workflow in the documentation | If your auditors or funders rely on formal encumbrance accounting, ERPNext is not a like-for-like replacement |
| Grants and contracts (sponsor billing, indirect cost recovery) | We found no grants management module in the documentation | Projects and dimensions can track spend, but sponsor billing and indirect cost rules would be a build |
| Fund accounting with balanced funds | Funds can be an accounting dimension; we found no fund-balancing rules | Test your fund reports early; this is often decisive |
| Supplier portal, punch-out catalogues and e-tendering | RFQs and supplier quotations exist; we found no punch-out catalogue feature | Keep your e-tendering portal and integrate |
| Scale: thousands of requisitioners | ERPNext runs on servers you size | Performance-test with your real approval volumes before deciding |
Our rule of thumb
If three or more rows in this table are must-haves for you, upgrade to 9.2 or move to a cloud ERP built for your sector. ERPNext should not be forced into an institution that needs the full public sector stack.
Where ERPNext genuinely fits
In our experience the realistic ERPNext candidates among PeopleSoft sites look like this:
- Smaller colleges and specialist institutions where finance is a team of 5 to 25 people, budgets are controlled by department and project, and student finance already lives in a separate system.
- Mid-size public bodies and arm’s-length agencies with a few hundred suppliers, routine procurement and no grant sponsor billing.
- Trading subsidiaries, enterprise companies and foundations of a university that are on the group’s PeopleSoft instance only for convenience, and need commercial invoicing, stock or projects that PeopleSoft was never configured for.
- Finance carve-outs where HCM and student systems have already left PeopleSoft and the remaining FSCM 9.1 instance is the last reason to keep the PeopleSoft stack running.
In each case, ERPNext replaces finance and procurement and nothing else. That is a smaller, more predictable project, and it is the only one we would recommend.
What moves, and what is archived
| Data | Approach |
|---|---|
| Chart of accounts and ChartFields | Redesign into accounts, cost centres and accounting dimensions; do not copy every legacy value |
| Suppliers and customers | Import active records only (ERPNext Data Import documentation); clean duplicates first |
| Open purchase orders and open invoices | Migrate at cutover |
| GL balances | Opening balances at a year end (ERPNext opening balance documentation); budget for the new year loaded fresh |
| Fixed asset register | Migrate active assets with cost, accumulated depreciation and remaining life |
| Prior-year transactions | Archive: keep PeopleSoft read-only or extract to a reporting database for audit and freedom of information requests |
Public bodies have retention duties. Agree the archive design, who can query it and for how long, with your records manager and auditors before you switch PeopleSoft off. An archive that nobody can query is not an archive.
A decision plan for the next 90 days
Days 1 to 30: inventory
List every PeopleSoft FSCM module in use, every customisation, every Sustaining Support workaround since 2018, and every integration (payroll, student system, banks, e-tendering).
Days 31 to 60: fit test
Score the limits table above. If ERPNext is still a candidate, rebuild one department’s budget, one tender and one month of payables in ERPNext with real data.
Days 61 to 90: business case
Price the 9.2 upgrade (ask Oracle and your PeopleSoft partner), the cloud route and, if it survived the fit test, ERPNext for finance and procurement only. Take the comparison to your audit committee.
Questions to ask Oracle and your PeopleSoft partner
Get these answers in writing
- Which of our FSCM 9.1 modules have had no regulatory update since Jan 2018, and which workarounds does Oracle recognise?
- What does the 9.2 upgrade involve for our release, PeopleTools version and customisations, and how many customisations would Selective Adoption let us retire?
- Which Upgrade Source Image and PeopleTools release would our upgrade use, and what infrastructure changes come with it?
- What would our annual support be on 9.2 compared with today?
- If we moved finance and procurement off PeopleSoft but kept HCM or Campus Solutions, how would our licence and support change?
- How long can we keep a read-only 9.1 instance for audit and records requests, and on what terms?
The answers decide the business case more than any feature list. If Oracle and your partner can show a clean 9.2 path with a manageable customisation retrofit, upgrading is usually the lower-risk choice for an institution. If the answer is a long, expensive retrofit of code nobody understands any more, the case for a smaller, simpler finance system strengthens.
Decision table
| Your situation | Our recommendation |
|---|---|
| Campus Solutions or HCM still on PeopleSoft and staying | Upgrade FSCM to 9.2 with them |
| Commitment Control, grants or fund-balanced reporting are must-haves | Upgrade to 9.2 or choose a public sector cloud ERP |
| Large university leaving on-premises and staying with Oracle | Oracle Fusion Cloud ERP |
| Small college or mid-size public body; finance team under 25; budget checks by department and project | Fit-test ERPNext for finance and procurement |
| University subsidiary, trading company or foundation on the group’s PeopleSoft | ERPNext is a strong candidate |
| HCM and student systems already gone; FSCM 9.1 is the last PeopleSoft pillar | Price 9.2 against ERPNext honestly; both are real options |
Costs: what is published
| Item | USD (published) | GBP | Source |
|---|---|---|---|
| PeopleSoft licences and support | Quote only; no estimate given | Quote only | Oracle Lifetime Support Policy for Applications (PDF, effective Aug 7, 2026) |
| Oracle Fusion Cloud ERP | Quote only | Quote only | Oracle’s PeopleSoft applications page |
| ERPNext software | No licence fee (GPL-3.0) | No licence fee | ERPNext repository on GitHub |
| ERPNext on Frappe Cloud, site plans | From $5 per month | About £3.81 (indicative) | Frappe Cloud pricing page |
| ERPNext on Frappe Cloud, servers | From $40 per month | About £30.49 (indicative) | Frappe Cloud pricing 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 22, 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 22, 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.
For an institution, hosting is the smallest number on the page. Implementation, data migration, integration with payroll and student systems, and the archive will dominate any path. Public bodies will also need to follow their own procurement rules for the implementation partner.
Best for, and wrong choice when
ERPNext is best for
Smaller colleges, mid-size public bodies, university subsidiaries and foundations that need solid finance and procurement with budget checks, approvals and fixed assets, and want to stop paying for an ageing PeopleSoft stack.
Upgrading to PeopleSoft 9.2 is best for
Institutions that run Campus Solutions or HCM on PeopleSoft, depend on Commitment Control or grants, and have PeopleSoft skills in house or through a partner.
ERPNext is the wrong choice when
You need encumbrance ledgers, grants and sponsor billing, fund-balanced statements or punch-out e-procurement, or you are trying to replace the whole PeopleSoft estate in one move.
If you want a plain answer on whether finance and procurement could leave PeopleSoft, our ERP Engineering practice will run the limits table above with your team and tell you if the 9.2 upgrade is the better route.
Frequently asked questions
When did PeopleSoft Financials 9.1 support end?
Oracle’s Lifetime Support Policy shows FMS/ESA/SCM 9.1 Premier Support ended Nov 2014 and Extended Support ended Jan 2018. Sustaining Support is indefinite (checked Nov 22, 2026).
Is PeopleSoft 9.2 still supported?
Yes. Oracle lists FMS/ESA/SCM 9.2 on Continuous Innovation with Premier Support through at least Dec 2037, extendable in one-year increments at Oracle’s discretion.
What does Sustaining Support not include?
New fixes, security alerts and critical patch updates; new tax, legal and regulatory updates; new upgrade scripts; certification with new third-party or Oracle products; and 24-hour Severity 1 response commitments.
Can ERPNext replace PeopleSoft for a university?
Not for the whole estate. It can replace finance and procurement in smaller institutions, subsidiaries and foundations. It does not replace Campus Solutions, HCM and payroll, encumbrance accounting or grants management.
Does ERPNext have budget control?
Yes. Budgets against a cost centre, project or accounting dimension can warn or stop when a material request, purchase order or posted expense exceeds the amount.
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 22, 2026). Implementation is separate. Oracle is quote-only.