Macola with no end-of-life date: moving US manufacturers to ERPNext on your own timeline
Short answer
There is no Macola end-of-life date, and you should be wary of anyone who gives you one. ERP Advisors Group, a third-party adviser, quotes ECI as saying that “all three Macola ERP systems—Macola Progression, Macola ES, and Macola 10—remain fully supported, with no end-of-life plans”, with Progression and ES focused mainly on platform updates and Macola 10 still getting new features. ECI’s own Macola page now reads as a resource for existing customers and points manufacturers to its other products: JobBOSS² for job shops, M1 for discrete and make-to-stock, and Deacom for batch and process. So treat any move as future-proofing, not a deadline. If you are a US small or mid-size manufacturer on Progression or ES, you are choosing between Macola 10, another ECI product, or a different ERP. ERPNext (open source, GPL-3.0, no licence fee) is a credible option when you want to own the system and your processes are standard discrete manufacturing and distribution. ECI is quote-only, so we give no ECI estimate.
Contents
- Who this guide is for
- What is actually known about Macola support
- Macola versions in one table
- Why plan a move without a deadline?
- Your options
- How Macola functions map to ERPNext
- Gaps to state up front
- Getting data out of Macola
- A phased plan, on your timeline
- Questions to ask ECI and your reseller
- Costs: what is published
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for owners, controllers and operations managers at US small and mid-size manufacturers and distributors running Macola, whether that is Macola Progression, Macola ES or Macola 10. ECI’s ECI’s Macola page says Macola “was created specifically for small to medium-sized manufacturers and distributors”. Many sites have run it for decades, through its ownership by Exact Software and, since 2018, by ECI.
We implement ERPNext, so read our view with that in mind. For many Macola sites, the honest answer is to stay put, or to upgrade to Macola 10, for now. Nothing is forcing a move. This guide is for owners who want to make the next ERP decision on their own timeline, with real options priced, rather than wait for a notice that may never come.
It is part of our series on legacy ERP systems; the legacy ERP end-of-support hub lists every vendor date we have confirmed, and Macola is in the section for systems with no published date. Related guides: QuickBooks Desktop to ERPNext for smaller US product businesses, and Epicor Vantage and Vista and Infor VISUAL for other long-running US manufacturing systems.
Sources, checked on Nov 21, 2026: ECI’s Macola page, ERP Advisors Group, “The Future of Macola ERP Support” (August 2025, third party), 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 Macola support
| Source | What it says | How much weight to give it |
|---|---|---|
| ECI’s Macola page | Macola is for small to medium-sized manufacturers and distributors. The page points “Macola Customers” to a new Customer Resource Center and the Support Portal, then lists JobBOSS² (job shops and make-to-order), M1 (discrete and make-to-stock) and Deacom (batch, process and continuous manufacturers) | ECI’s own page: high, but it contains no lifecycle statement |
| ERP Advisors Group, “The Future of Macola ERP Support” (August 2025, third party) | Quotes ECI: “All three Macola ERP systems—Macola Progression, Macola ES, and Macola 10—remain fully supported, with no end-of-life plans… While Progression and ES focus primarily on platform updates, Macola 10 continues to receive new features and integration enhancements.” Also says ECI offers JobBOSS², M1 and Deacom as upgrade options from Macola 10, “none of these migration paths are being forced” | Third-party source quoting ECI: useful, and consistent with ECI’s page; ask ECI to confirm in writing |
We found no Macola lifecycle policy or end-of-life notice on ECI’s site. The same adviser notes that Macola 10 is a client-server application that can be hosted by third parties, rather than multi-tenant cloud software. That is a fact about architecture, not a support risk.
What we can say safely
Macola has no announced end of life. ECI’s message, as quoted, is that all three versions are supported and that moving to another ECI product is optional. Progression and ES are getting platform updates rather than new features. Any move is a business decision about fit and future-proofing, not a compliance deadline.
Macola versions in one table
Macola’s long history explains why so many versions are still in use. From the ERP Advisors Group, “The Future of Macola ERP Support” (August 2025, third party) account:
| Version or event | When | What it means for you today |
|---|---|---|
| Macola Software founded in Ohio | Early 1970s | Some sites have decades of data and habits built around Macola |
| Macola ES released (financial functions added to Progression) | 1999 | ES and Progression are the “foundation” versions; as quoted, they get platform updates |
| Exact Software acquires Macola | 2001 | Many resellers and add-ons date from the Exact years |
| Macola 10 released | June 2014 | The newer platform; as quoted, still receiving new features |
| ECI acquires Macola | 2018 | ECI now also sells JobBOSS², M1 and Deacom to manufacturers |
| Macola 10.7: ECI announces the end of “version lock” with an extension layer | After 2018 | Customisations built on the extension layer should survive upgrades better |
| Macola 10.8: adds an AP Voucher Workbench | More recent | Evidence that Macola 10 is still developed |
If you are on Progression or ES with heavy customisation, the jump to Macola 10 is itself a project. That is the fair comparison point for an ERPNext move: not “stay as we are”, but “upgrade within Macola” versus “move”.
Why plan a move without a deadline?
“Supported with no end-of-life plans” is a good position to be in. It is still worth planning, for reasons that have nothing to do with a date:
- Direction of investment. On ECI’s own page, new manufacturing buyers are pointed to JobBOSS², M1 and Deacom. As quoted, Progression and ES get platform updates; new features go to Macola 10.
- People. Macola sites often depend on one long-serving administrator or a reseller who knows the customisations. When that person retires, the system becomes harder to change.
- Integrations and reporting. Older Macola versions can make e-commerce, EDI and reporting integrations harder than they need to be. If you are rebuilding those anyway, the system underneath is worth reconsidering.
- Timing you control. Moving when you choose, after a good year, with time for a proper fit test, is cheaper and calmer than moving because something broke.
None of this means you should leave. It means the decision deserves a fit test and real quotes, not an assumption.
Your options
| Option | What it involves | Best when |
|---|---|---|
| Stay on your current Macola version | Keep running under ECI support | Macola works, the team is stable, and there is no business trigger |
| Upgrade Progression or ES to Macola 10 | Same vendor, newer platform; the version still getting new features, as quoted | You like Macola and want the current version |
| Move to another ECI product | JobBOSS² for job shops, M1 for discrete and make-to-stock, Deacom for batch and process, per ECI’s page | You want to stay with ECI and one of those products fits better |
| Move to ERPNext | Open-source ERP on Linux with MariaDB; self-hosted or on Frappe Cloud | You want to own the system, avoid per-user licences, and your processes are standard |
ECI does not publish Macola, JobBOSS², M1 or Deacom prices on the pages we checked, so we give no ECI estimate. Ask for written quotes with the same user count and scope, and compare them with an ERPNext proposal over five years.
How Macola functions map to ERPNext
Every Macola site uses a different mix of functions. Map the ones you actually use:
| Macola area (as typically used) | ERPNext equivalent | Notes |
|---|---|---|
| General ledger, AP, AR, bank | Chart of Accounts, Payment Entry, bank reconciliation (ERPNext Chart of Accounts documentation; ERPNext Payment Entry documentation; ERPNext bank reconciliation documentation) | Rebuild the chart cleanly; do not copy decades of unused accounts |
| Inventory and warehouses | Items, Warehouses, Stock Entries (ERPNext Item documentation; ERPNext Warehouse documentation; ERPNext Stock Entry documentation) | Valuation by FIFO, LIFO or moving average (ERPNext Stock Settings documentation) |
| Lot and serial tracking | Batches with expiry and Serial Nos (ERPNext Batch documentation; ERPNext Serial No documentation) | Good |
| Order entry and pricing | Quotations, Sales Orders, Price Lists and Pricing Rules (ERPNext Quotation documentation; ERPNext Sales Order documentation; ERPNext Pricing Rule documentation) | Load your real customer price agreements |
| Purchasing and receiving | Purchase Orders, Purchase Receipts, Landed Cost Vouchers (ERPNext Purchase Order documentation; ERPNext Purchase Receipt documentation; ERPNext Landed Cost Voucher documentation) | Good |
| Bills of material and production | BOMs, Work Orders, Routings (ERPNext Bill of Materials documentation; ERPNext Work Order documentation; ERPNext Routing documentation) | Good for standard discrete make-to-stock and make-to-order |
| MRP | Production Plan and Material Requests (ERPNext Production Plan documentation; ERPNext Material Request documentation) | Test with a real month of demand |
| Shop floor reporting | Job Cards with time logs (ERPNext Job Card documentation) | Browser-based; test on the devices your floor uses |
| Outside processing | Subcontracting (ERPNext Subcontracting documentation) | Good |
| Multi-company | Inter-company invoices and accounting dimensions (ERPNext inter-company invoices documentation; ERPNext accounting dimensions documentation) | Good |
Process and batch manufacturers should be more careful. ECI itself points batch and process manufacturers to Deacom. ERPNext handles fixed recipes, batches and quality inspections, but we found no potency, catch-weight or dual-unit features in its documentation.
Gaps to state up front
| If you depend on | ERPNext position | What to do |
|---|---|---|
| EDI with large customers | No EDI module found in ERPNext’s documentation | Plan an EDI provider and an integration |
| Payroll | Not part of core ERPNext | Keep your payroll service |
| US sales tax across many states | Sales Taxes and Charges Templates on invoices (ERPNext Sales Invoice documentation) | Test your real nexus and exemption cases, or connect a tax service |
| Advanced finite scheduling | Capacity planning allocates jobs by workstation working hours (ERPNext Capacity Planning documentation) | Not a drag-and-drop finite scheduler; keep a scheduling tool if you rely on one |
| Shop-floor terminals and badge scanning | Job Cards and the Plant Floor view in the browser (ERPNext Plant Floor documentation) | We found no documented time-clock hardware support; test your devices |
None of these is unusual for an ERP replacement at this size, but each belongs in the plan and the budget from day one.
Getting data out of Macola
Ask your Macola reseller which database and version your installation uses, and how they recommend extracting data. Most data you need comes out as tables or reports that can be exported to CSV.
| Macola data | ERPNext target | How |
|---|---|---|
| Items, customers, vendors | Items, Customers (ERPNext Customer documentation), Suppliers (ERPNext Supplier documentation) | Extract, de-duplicate, load with Data Import (ERPNext Data Import documentation) |
| Active BOMs and routings | BOMs and Routings | Only products you will make again |
| On-hand stock by lot or serial | Stock Reconciliation (ERPNext Stock Reconciliation documentation) | Count before go-live |
| Open sales and purchase orders | Sales Orders, Purchase Orders | Freeze during cut-over |
| Open AR and AP | Opening invoices (ERPNext opening balance documentation) | Reconcile to aged reports |
| GL balances | Opening trial balance | Keep Macola read-only for history |
Keep Macola available read-only, or export closed history to a reporting database, for audits, warranty claims and the inevitable “what did we charge them in 2019?” questions.
A phased plan, on your timeline
| Phase | What happens | Typical output |
|---|---|---|
| 1. Inventory | Version, users, customisations, reports, integrations, and who maintains them | A one-page picture of your Macola estate |
| 2. Fit test | A month of real transactions and a month end in an ERPNext trial | Pass, configure or develop, per process |
| 3. Quotes | Macola 10 or other ECI product quote; ERPNext proposal with the same scope | Five-year comparison |
| 4. Decide | Stay, upgrade within ECI, or move | A decision with evidence behind it |
| 5. Build and cut over (if moving) | Configure, load test data twice, go live at a period end | Live ERPNext, archived Macola |
Pick a quiet month for cut-over, and avoid your fiscal year end unless your accountant prefers it. Because there is no deadline, you can afford to wait for the right window.
Questions to ask ECI and your reseller
Get these answered in writing
- Is our exact Macola version and service pack fully supported today, and what does “support” include for it: fixes, tax table updates, compatibility with new Windows and SQL Server releases?
- Which of our customisations would survive an upgrade to Macola 10, and which would need rework on the extension layer?
- If ECI recommends JobBOSS², M1 or Deacom for us instead, why, and what would the move involve?
- What would five years cost under each ECI path, with our user count, including maintenance, hosting and services?
- Who at the reseller knows our system, and what happens if they leave?
The answers give you the “stay with ECI” side of the comparison. The fit test gives you the ERPNext side. With both, the decision usually becomes obvious.
Costs: what is published
| Item | USD (published) | GBP | Source |
|---|---|---|---|
| Macola, JobBOSS², M1, Deacom licences, maintenance and upgrades | Quote only; no estimate given | Quote only | ECI’s Macola 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, dedicated servers | From $40 per month | About £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.
In the “stay” column, include your annual maintenance, hosting or server costs and reseller support. In the “move” column, include implementation, data work, any EDI or tax integration and retraining. Those usually matter more than software prices.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| Macola works and nothing is changing | Stay, and revisit in a year | There is no deadline |
| On Progression or ES and like Macola | Macola 10 | Same vendor; the version still getting new features, as quoted |
| Job shop or batch process manufacturer happy with ECI | JobBOSS² or Deacom | ECI’s own recommendation by segment |
| Want to own the system and avoid per-user licences | ERPNext | GPL-3.0; standard discrete and distribution processes fit well |
| Heavy EDI, process formulas or complex scheduling | Test carefully before ERPNext | These are the known gaps |
Best for, and wrong choice when
ERPNext is best for
US small and mid-size discrete manufacturers and distributors on Macola who want to own their next system, have standard processes, and can plan a move on their own timeline.
Staying with ECI is best for
Sites that like Macola and its reseller, and job shops or batch producers that fit JobBOSS², M1 or Deacom well.
ERPNext is the wrong choice when
Process formulas, heavy EDI or advanced scheduling are central and untested, or nobody in the business can own the new system after go-live.
Want a second opinion before you commit? Our ERP Engineering practice runs fit tests like the one above on your own data, and we will tell you if staying with ECI is the better answer.
Frequently asked questions
Is Macola being discontinued?
No end of life has been announced. A third-party adviser quotes ECI saying Macola Progression, Macola ES and Macola 10 remain fully supported with no end-of-life plans (checked Nov 21, 2026).
Is Macola still being developed?
As quoted by ERP Advisors Group, ECI says Progression and ES focus primarily on platform updates, while Macola 10 continues to receive new features and integration enhancements.
What does ECI recommend instead of Macola?
ECI’s Macola page lists JobBOSS² for job shops and make-to-order, M1 for discrete and make-to-stock, and Deacom for batch and process manufacturers.
Can ERPNext replace Macola?
For standard discrete manufacturing and distribution, usually yes: inventory, lots, BOMs, work orders, MRP and finance are core. Test EDI, US sales tax and scheduling needs first.
How long does a Macola to ERPNext move take?
It depends on scope. Run a fit test with a month of real transactions first; the plan should follow the results, not a calendar.
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. ECI is quote-only.