Still on Epicor Vantage or Vista: migrating a small manufacturer to ERPNext
Short answer
Partner sources list Epicor Vantage and Vista 8.03.4 or earlier in Sustaining Support, with no end date (checked Nov 17, 2026). Epicor’s own Support Lifecycle Policy sits behind its EpicWeb customer login, so we could not confirm this on a public Epicor page and we give no date. The practical point is simpler: Vantage 8 is several product generations behind Epicor’s current Kinetic, and Epicor has said the final on-premises Kinetic release is 2028.1. Community accounts of the Vantage-to-Epicor-10 route describe a stepped upgrade through Epicor 9.05, a painful unit-of-measure conversion and the move from Progress to SQL Server, and some sites chose to re-implement instead. If you are re-implementing anyway, ERPNext (open source, GPL-3.0, no licence fee) is worth pricing for a small manufacturer. The two decisions that make or break the project are how you extract data from the Progress database and where you cut off history. Epicor is quote-only, so we give no Epicor estimate.
Contents
- Who this guide is for
- Support status: what is known, and from whom
- Why move now if it still works
- Your options
- Getting data out of the Progress database
- Where to cut off history
- How Vantage concepts map to ERPNext
- Cut-over plan for a small shop
- Costs: what is published
- Where an Epicor route is the better answer
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for owners, general managers, controllers and the one or two people who look after IT at small manufacturers, often 10 to 100 people, still running Epicor Vantage or Vista 8.03 or earlier. These systems have often run for 15 years or more. The server is old, the person who set it up may have left, and nobody wants to touch it because it still prints the travellers and the invoices.
We implement ERPNext, so read our view with that in mind. For some Vantage sites, moving to Epicor’s current product is the right call, and we say when below. For many small shops, though, the move is a reimplementation whichever product you choose, and that is the point where an open-source option deserves a fair look.
It is part of our series on legacy ERP deadlines; the legacy ERP end-of-support hub lists every vendor date we have confirmed. If you are on Epicor 9.05 or 10, read our Epicor 10 and 9 guide; if you are already on Kinetic, read our Kinetic on-premises guide.
Sources, checked on Nov 17, 2026: the ERP Advisors Group article on Epicor ERP support (third party), Epicor’s Epicor press release, Jan 6, 2026 and Epicor “Innovation Moves to the Cloud” page, the EpiUsers community thread on a Vantage 8.03 upgrade and the EpiUsers community thread on moving Vantage 8 data into SQL Server, 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 we could not confirm
Epicor says its Support Lifecycle Policy and FAQs are available through EpicWeb, its customer login. We found no public Epicor page stating the support level for Vantage or Vista. The status here comes from a partner source, and the upgrade experiences come from a user community, not from Epicor. Treat them as practitioner accounts, and confirm your own status with Epicor.
Support status: what is known, and from whom
| Claim | Status | Source |
|---|---|---|
| Vantage and Vista 8.03.4 or earlier are in Sustaining Support | Partner source; no date; not confirmed on a public Epicor page | ERP Advisors Group article on Epicor ERP support (third party) |
| Sustaining Support means essential support only, no new modules, limited support services | Partner source | ERP Advisors Group article on Epicor ERP support (third party) |
| Epicor 9 (2008) was a rebuild of Vantage on Epicor’s ICE framework | Partner source | ERP Advisors Group article on Epicor ERP support (third party) |
| Final on-premises Kinetic release is 2028.1, tentatively January 2028; Active Support to Dec 31, 2029 | Epicor | Epicor press release, Jan 6, 2026 |
| Lifecycle policy and FAQs are behind the EpicWeb login | Epicor | Epicor “Innovation Moves to the Cloud” page |
In plain terms: you can still run Vantage, and you may still be paying for support, but there is no product path forward on Vantage itself. Any move, to Epicor’s current product or to anything else, is a migration to a different generation of software.
Why move now if it still works
- Hardware and operating systems. Vantage servers are often old. When the hardware fails, getting a supported operating system that still runs your Vantage and Progress versions can be the real emergency.
- Security. Old servers and clients that cannot be patched are a risk your insurer and your customers increasingly ask about.
- Knowledge. Vantage administration, Progress database maintenance and custom reports often sit with one person.
- Growth. Under Sustaining Support, partner sources say you cannot buy new modules. If you need new capability, you need a new system.
None of these has a date. That is why small shops keep postponing. A better trigger is the server: if your Vantage server is out of warranty, start planning now, because migrating calmly is far cheaper than migrating after a failure.
Your options
| Option | What it involves | Best when |
|---|---|---|
| Move to Kinetic in the Epicor Cloud | Epicor-hosted current product; migration through Ascend with Epicor (fixed-fee program pricing per Epicor, quoted) | You want to stay with Epicor and are comfortable with SaaS |
| Stepped upgrade to on-premises Epicor | Community accounts describe Vantage 8.03 to 9.05 (on Progress), then to Epicor 10 (SQL Server), then on to Kinetic | Rarely the best route now; on-premises Kinetic’s final feature release is 2028.1 |
| Re-implement on Epicor with only master data | Fresh Epicor system; load customers, parts and open items; keep Vantage for history | You want Epicor and a clean start |
| Move to ERPNext | Fresh open-source ERP; load masters, open items and balances; keep Vantage for history | You want to own the system, avoid per-user licences, and your needs are those of a typical small make-to-order shop |
On the EpiUsers forum, an experienced Epicor consultant advised a Vantage 8 site that the jump to Epicor 10 is “big enough that it may be a great time to re-implement”, bringing in only master data such as customers and parts, not history. Another user who did the stepped upgrade reported that the hardest part was not Epicor 9 to 10 but Vantage 8 to 9, especially the unit-of-measure conversion. That is a practitioner account, not an Epicor statement, but it matches what we see: for a Vantage site, every route is a new implementation.
Getting data out of the Progress database
Vantage and Vista sites typically run on a Progress OpenEdge database. That matters, because most modern migration tooling expects SQL Server or flat files. You have four practical routes, and most projects use more than one:
| Route | What it is | Watch out for |
|---|---|---|
| Vantage screens and reports to Excel | Export lists from Vantage itself: parts, customers, suppliers, open orders | Quick and safe for masters; slow for large tables; check field truncation |
| Business Activity Queries or custom reports | Build queries for the joins you need, export to CSV | Needs someone who knows the Vantage schema |
| ODBC or SQL access to the Progress database | Query the database directly from a staging tool | Depends on your Progress licence and drivers; test on a copy, never on live |
| Progress dump and load, or OpenEdge DB to SQL Server tools | Dump tables, or use OpenEdge utilities to move the schema and data into SQL Server for staging | Community users report errors on some tables and very large decimal fields; plan time to fix them |
The EpiUsers community thread on moving Vantage 8 data into SQL Server describes exactly these issues: a site moving master files to Epicor 10 wanted Vantage history in SQL Server for reference, got most tables across with linked-server queries, and hit errors on others, including problems with Progress decimal fields. Another participant pointed to OpenEdge’s own dump-and-load and DB-to-SQL Server utilities. The lesson for any destination, ERPNext included: always work on a copy of the database, never the live one, and budget real time for extraction.
Extraction checklist
- Take a full, verified backup of the Progress database and restore it on a separate machine.
- List the tables you need: parts, methods, customers, suppliers, open orders, open jobs, stock, open AR and AP, GL balances.
- Extract masters first and count rows against Vantage screens.
- Extract open transactions last, at cut-over, after a freeze.
- Keep the extract scripts; you will run them more than once.
Where to cut off history
This is the decision small shops find hardest, and it is mostly a business decision, not a technical one. Three options:
| Approach | What moves to ERPNext | What stays behind | Best when |
|---|---|---|---|
| Clean cut | Masters, open orders, open jobs or their remaining work, stock, open AR/AP, GL opening balances | All closed transactions, in Vantage read-only or an archive database | Most small manufacturers |
| Clean cut plus summary history | As above, plus summarised sales by customer and item for recent years, loaded as reference data | Detail transactions | Sales teams want trend data in the new system |
| Full history | Everything | Nothing | Rarely worth it; high cost and risk |
We almost always recommend the clean cut. Agree three things up front: which date is the cut-off (usually a financial year or month end), how long the old data must remain available (ask your accountant and, if you have certifications, your quality lead), and where it will live once the Vantage server is switched off. A SQL Server or even a well-indexed set of CSV files with a simple query tool is often enough for repeat-order lookups and audits. The EpiUsers community thread on moving Vantage 8 data into SQL Server shows other sites taking the same approach: master files into the new system, history available for reference outside it.
How Vantage concepts map to ERPNext
| In Vantage or Vista | In ERPNext | Notes |
|---|---|---|
| Parts, part classes, UOMs | Items, item groups, UOM conversions (ERPNext Item documentation) | Fix unit-of-measure oddities during the move |
| Methods of manufacture | BOMs with operations, Routings (ERPNext Bill of Materials documentation; ERPNext Routing documentation) | Active parts only |
| Resource groups and resources | Workstations (ERPNext Workstation documentation) | Hours, holiday list, costs, capacity |
| Jobs, job travellers, labour entry | Work Orders and Job Cards (ERPNext Work Order documentation; ERPNext Job Card documentation) | Job Cards per operation, with time logs and completed quantity |
| Scheduling | Capacity planning against workstation hours (ERPNext Capacity Planning documentation) | No documented graphical finite scheduler; test with your real week |
| Quotes | Quotation (ERPNext Quotation documentation) | Define how estimators price from a BOM and routing |
| Purchasing and MRP suggestions | Material Requests, Purchase Orders, Production Plan (ERPNext Material Request documentation; ERPNext Purchase Order documentation; ERPNext Production Plan documentation) | Compare suggestions for the same demand |
| Inspection | Quality Inspection (ERPNext Quality Inspection documentation) | In-process inspection from a Job Card |
| Lot and serial tracking | Batch and Serial No (ERPNext Batch documentation; ERPNext Serial No documentation) | Decide what you must trace |
| Customer and supplier records | Customers and Suppliers (ERPNext Customer documentation; ERPNext Supplier documentation) | Load with Data Import (ERPNext Data Import documentation) |
Two ERPNext details small shops like. Routings can enforce operation order on the floor: ERPNext throws a validation error if someone completes an operation before its predecessors. And Plant Floor gives a simple visual view of machines, stock and Job Cards (ERPNext Plant Floor documentation).
Cut-over plan for a small shop
Weeks 1 to 3: copy and extract
Restore a copy of the Vantage database on a separate machine. Extract masters. List reports and forms you print daily: travellers, pick lists, packing slips, invoices.
Weeks 3 to 8: build and test
Load masters into an ERPNext trial. Rebuild methods for your 20 most common parts. Run two weeks of real jobs on paper alongside. Rebuild the printed forms.
Weeks 8 to 10: rehearse
Run the full extract and load twice on a test system, timing each step. Reconcile stock and balances against Vantage reports.
Cut-over weekend
Freeze Vantage at a month end. Extract open items, stock and balances. Load, reconcile, go live. Keep Vantage read-only for history.
Timelines depend on data quality and how many people can give time to testing. Do not plan cut-over for your busiest month or your year end.
Costs: what is published
| Item | USD (published) | GBP | Source |
|---|---|---|---|
| Epicor Kinetic, Epicor Cloud, Ascend with Epicor | Quote only; no estimate given | Quote only | Epicor “Innovation Moves to the Cloud” 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.78 (indicative) | Frappe Cloud pricing page |
| ERPNext on Frappe Cloud, dedicated servers | From $40 per month | About £30.25 (indicative) | Frappe Cloud server plans page |
Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.78) and servers from $40 a month (about £30.25), checked on Nov 17, 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.3222 per £1 for 13 Nov 2026, the latest published figure when we checked on Nov 17, 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 a small shop, the costs that matter are data extraction and cleansing, rebuilding methods for active parts, printed forms and reports, training and the time your own people spend testing. Ask any partner, ours included, to price those lines separately.
Where an Epicor route is the better answer
- You want to stay with Epicor and are comfortable with SaaS: Kinetic in the Epicor Cloud through Ascend keeps you in a familiar family.
- You rely on functions ERPNext does not document, such as a graphical finite scheduler or a rules-based product configurator.
- You have an Epicor partner you trust who knows your business and can run the re-implementation.
ERPNext is a better fit when you want to own the system, self-host or choose your hosting, avoid per-user subscriptions, and your shop runs on BOMs, routings, work orders, a dispatch list and straightforward costing.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| Server near end of life, no Epicor upgrade budgeted | Start planning now, either route | Migrating after a failure is far harder |
| Want to stay with Epicor and accept SaaS | Kinetic in the Epicor Cloud | Current product; Ascend migration program |
| Want to own the system and code, small make-to-order shop | ERPNext worth pricing | Open source; core manufacturing and accounting are standard |
| Finite scheduling or configurator is essential | Epicor route, or ERPNext plus a tool | ERPNext has no documented finite scheduler or rules-based configurator |
| Need full transaction history in the new system | Reconsider | A clean cut with an archive is cheaper and safer |
Best for, and wrong choice when
ERPNext is best for
Small manufacturers on Vantage or Vista 8.03 or earlier that are re-implementing anyway, want to own their ERP, run make-to-order work with moderate scheduling needs, and are willing to cut history cleanly.
Kinetic Cloud is best for
Vantage sites that want to stay with Epicor, accept vendor-hosted SaaS and want Epicor’s current scheduling and configuration capabilities.
ERPNext is the wrong choice when
Nobody internally can own the new system, you depend on a configurator or finite scheduler you will not replace, or you insist on moving all history into the new ERP.
Frequently asked questions
Is Epicor Vantage still supported?
Partner sources list Vantage and Vista 8.03.4 or earlier in Sustaining Support, with no end date (checked Nov 17, 2026). Epicor’s policy is behind the EpicWeb login, so confirm your status there.
What database does Vantage use?
Vantage 8 sites typically run on Progress OpenEdge. Community accounts describe the move to SQL Server happening at the Epicor 9.05 to 10 migration.
Can we upgrade Vantage straight to Kinetic?
Community accounts describe a stepped route through Epicor 9.05 and 10. Some sites re-implemented instead, loading master data only. Ask Epicor what its Ascend program offers for Vantage sites.
How do we get data out of Progress?
Use Vantage exports and queries for masters, and ODBC access or Progress dump-and-load or OpenEdge DB-to-SQL Server tools for larger extracts. Always work on a restored copy, not the live database.
Should we migrate our Vantage history to ERPNext?
Usually not. Move masters, open items, stock and balances, and keep history read-only in Vantage or an archive database.
Can ERPNext run a small manufacturer?
Yes, for most make-to-order shops: BOMs, routings, work orders, job cards, MRP, stock, purchasing, sales and accounting are standard. Test scheduling with a real week of jobs.
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.78 and £30.25 at the Bank of England rate for Nov 13, 2026; checked Nov 17, 2026). Implementation is separate.