On a retired Acumatica release: upgrade, or move 50 to 500 user distributors to ERPNext?
Short answer
Acumatica’s own Support Subscription Agreement (July 2026) says it supports versions “as set forth in the Product Support Lifecycle Policy published on the Acumatica Support Portal” and that “Retired versions are not supported”. Its Licensing Guide (April 2026) says Acumatica ships two upgrade releases a year and that, in most cases, each upgrade release is supported for 18 months and then retired. The exact retirement date for each release sits on the support portal, behind a login, so we do not list dates here; check yours with your partner. The people this affects are mostly Private Cloud and Flex customers who deferred upgrades, because SaaS customers on Always Current are upgraded automatically. For a 50 to 500 user distributor, the honest default is to upgrade: Acumatica’s guide says software updates and upgrades are included in SaaS and Private Cloud subscriptions, so you pay for partner time and retesting, not a new licence. ERPNext (open source, GPL-3.0, no licence fee) is worth pricing when heavy customisations make every upgrade a project, when you want to own and host the system without a subscription, or when the renewal no longer makes sense for the business. Acumatica pricing is quote-based, so we give no Acumatica estimate.
Contents
- Who this guide is for
- What Acumatica’s own documents say
- Who actually ends up on a retired release
- How Acumatica is licensed, and why there is no list price
- Why upgrading is usually the right answer
- When ERPNext is worth pricing
- How an Acumatica distribution setup maps to ERPNext
- Distribution fit tests
- Getting data out of Acumatica
- Costs: what is published
- A 60-day decision plan
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for finance directors, operations leads and IT managers at wholesale and distribution businesses with roughly 50 to 500 Acumatica users that are running a release Acumatica has retired, or one that is close to retirement. In our experience that usually means one of three situations: a Private Cloud deployment hosted by you or your partner where upgrades were postponed; a SaaS customer on the Flex Program who pushed an upgrade too far; or a site whose customisations or third-party add-ons made the last upgrade so painful that nobody wants to start the next one.
We implement ERPNext, so read our view with that in mind. Acumatica is a modern cloud ERP that is still actively developed, and for most distributors on an old release the right answer is to upgrade. This guide sets out why, and then covers the minority of cases where moving to ERPNext deserves a proper price comparison.
It is part of our series on legacy ERP deadlines; the legacy ERP end-of-support hub lists every vendor date we have confirmed. Distributors may also find our Prophet 21 on-premises guide useful, because the distribution fit tests are similar.
Sources, checked on Nov 18, 2026: the Acumatica Support Subscription Agreement (July 2026), the Acumatica Licensing Guide (April 2026), the Acumatica pricing page, 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 Acumatica’s own documents say
Acumatica does not publish a public page with every release and its retirement date; it points to a Product Support Lifecycle Policy on its customer support portal. What it does publish openly is enough to understand the rules:
| Document | What it says | Why it matters |
|---|---|---|
| Acumatica Support Subscription Agreement (July 2026) | Acumatica provides Support Services for supported versions “as set forth in the Product Support Lifecycle Policy published on the Acumatica Support Portal. Retired versions are not supported under this Agreement.” | On a retired release, your support subscription does not cover that version |
| Acumatica Licensing Guide (April 2026) | Acumatica “bundles enhancements into two upgrade releases per year” and “In most cases, each upgrade release is supported for 18 months and is then retired.” | A release you installed two years ago is very likely retired now |
| Acumatica Licensing Guide (April 2026) | “Private Cloud and Flex program customers may defer their upgrade so long as they upgrade by the retirement date of the given release.” | Deferral is allowed only up to retirement |
| Acumatica Licensing Guide (April 2026) | Patches (high-severity fixes) apply to 2025 R1 and later; Updates (monthly bug fixes) apply to releases before 2025 R1, “until the Upgrade reaches end-of-life”. | Once retired, no more fixes for your release |
| Acumatica Licensing Guide (April 2026) | “Software Updates and Upgrades … are included with PCS Subscriptions” and with SaaS subscriptions. | Upgrading does not need a new licence; you pay for services and retesting |
About dates
You will find retirement dates for individual releases quoted on community forums and partner sites. We do not repeat them here because they are not on a public Acumatica page we could check. Ask your partner for the current Product Support Lifecycle Policy from the support portal, or look it up yourself if you have portal access, and work from that.
Who actually ends up on a retired release
The Licensing Guide explains why this is mostly a Private Cloud and Flex problem:
| Deployment | Upgrade rhythm (from Acumatica’s Licensing Guide) | Risk of running a retired release |
|---|---|---|
| SaaS on Always Current | Upgraded every 6 or 12 months within 120 days of release, depending on product; Acumatica upgrades customers automatically if they have not upgraded by their Scheduled Upgrade Date | Low |
| SaaS on the Flex Program (Prime and Enterprise only) | Choose your own upgrade date, as long as it is before the end of life of your current version | Medium: deferral can run up to the retirement date |
| Private Cloud Subscription (on your servers, or hosted by your partner or a third party) | You or your partner schedule upgrades; deferral allowed up to the retirement date | Highest: nobody upgrades you automatically |
If your Acumatica runs in your own data centre or with a hosting partner, and nobody has scheduled an upgrade since the release you went live on, assume it is retired until your partner confirms otherwise.
How Acumatica is licensed, and why there is no list price
Acumatica markets itself on not charging per user. Its Acumatica pricing page says “Unlimited Users. One Transparent Price.” and that pricing is tailored on three factors: the applications you need, your expected usage and resource requirements, and your deployment preferences. The Licensing Guide adds the detail:
| Licensing element | What Acumatica’s Licensing Guide says |
|---|---|
| Products | Essentials (smaller organisations, five named users included, up to ten), Select (typically up to 50 employees), Prime (lower mid-market, up to 200 employees) and Enterprise (any size, reserved resource environment) |
| Industry editions | Distribution, Retail, Manufacturing, Construction, Professional Services and General Business |
| Transaction Tier Consumption Licensing | Based on monthly Commercial Transaction Volume: the single highest monthly volume of eight transaction types (sales orders, shipments, AR invoices, customer payments, purchase orders, purchase receipts, AP bills and AP payments). Tiers run from 1,000 a month upwards |
| Named User Licensing | Prime includes 10 named users and allows up to 100; Enterprise includes 35, with the maximum listed as unlimited |
| Recommended maximums | Prime’s recommended maximum is 100 users and 12,000 daily ERP transactions at its highest consumption tier; for Enterprise the user figure is “scalable” |
| Renewal price cap | Renewal prices for SaaS and Private Cloud subscriptions will not rise by more than 10% a year, subject to conditions; discounts on the order form do not carry into renewals |
For a distributor with 50 to 500 users, that usually puts you in Prime at the lower end and Enterprise above roughly 100 active users, but your partner will size it on transaction volumes and modules. Acumatica does not publish prices; the pricing page sends you to an industry calculator and a pricing review. So we give no Acumatica figure. Ask for a written renewal and upgrade quote that separates subscription, resources (such as SaaS Reserved Resources), partner services and any add-on modules.
Why upgrading is usually the right answer
- The licence is already paid for. Upgrades are included in your subscription, per Acumatica’s Licensing Guide. A move to any other ERP means new implementation spend on top.
- The product is current. Acumatica ships two releases a year. Moving from a retired release to a current one brings features you are already paying for.
- Your data stays put. An upgrade converts your database. A migration means extracting, cleaning and loading it again.
- Your partner knows it. A competent Acumatica partner can usually scope an upgrade quickly once customisations are listed.
The main reason upgrades stall is customisation. Acumatica customisation projects and third-party add-ons have to be retested, and sometimes rewritten, for each release. If that is your blocker, fix that first: ask your partner for a list of every customisation and add-on, with an effort estimate per item for the target release. Often, a handful of old customisations can be retired because the current release now does the job natively.
When ERPNext is worth pricing
- Every upgrade is a project. If your Acumatica carries so much custom code that each release takes months to retest, you are paying a recurring tax. ERPNext also needs care with customisations, but you control when you upgrade, and you own the code.
- You want ownership without a subscription. ERPNext is GPL-3.0. You can self-host it indefinitely or use Frappe Cloud; there is no subscription renewal to negotiate.
- The renewal no longer fits. If transaction growth has pushed you into higher tiers or reserved resources, run the numbers both ways over five years.
- You are reimplementing anyway. If the business has changed so much that the Acumatica configuration no longer fits, a fresh implementation is on the table either way.
Be honest about the trade
Moving from Acumatica to ERPNext is a full ERP migration: new screens, retraining every user, rebuilding integrations and reports. Do not do it to escape a single upgrade. Do it only if the five-year economics or ownership requirements genuinely favour it.
How an Acumatica distribution setup maps to ERPNext
| In Acumatica | In ERPNext | Notes |
|---|---|---|
| Stock items, item classes, warehouses and locations | Items (ERPNext Item documentation), Item Groups, Warehouses (ERPNext Warehouse documentation) | ERPNext warehouses can be nested to model locations |
| Sales prices, customer price classes, discounts | Price Lists (ERPNext Price Lists documentation), Item Prices (ERPNext Item Price documentation), Pricing Rules (ERPNext Pricing Rule documentation), Promotional Schemes (ERPNext Promotional Scheme documentation) | The biggest fit test for distributors |
| Sales orders and shipments | Sales Orders (ERPNext Sales Order documentation), Delivery Notes, Shipments (ERPNext Shipment documentation) | Map order types to naming series and workflows |
| Purchase orders, receipts, landed costs | Purchase Orders (ERPNext Purchase Order documentation), Purchase Receipts, Landed Cost Voucher (ERPNext Landed Cost Voucher documentation) | Landed costs are allocated against receipts |
| Warehouse management (picking, put-away) | Pick List (ERPNext Pick List documentation), Putaway Rule (ERPNext Putaway Rule documentation) | Test with barcode scanners you already own |
| Replenishment | Reorder levels with automatic Material Requests (ERPNext reorder level (auto material request) documentation) | Check seasonality handling with your buyers |
| Blanket orders | Blanket Order (ERPNext Blanket Order documentation) | Common in industrial distribution |
| Lot and serial tracking | Batch (ERPNext Batch documentation), Serial No (ERPNext Serial No documentation) | Batches support expiry dates |
| Intercompany accounting, multiple branches | Inter-company invoices (ERPNext inter-company invoices documentation), Accounting Dimensions (ERPNext accounting dimensions documentation) | Decide branch vs company structure early |
| Multi-currency | Multi-currency accounting (ERPNext multi-currency accounting documentation) | UK and US entities in one instance |
| Generic Inquiries and dashboards | Reports, report builder and dashboards | List the inquiries people actually use |
Distribution fit tests
Run these in an ERPNext trial with your own data
- Pricing. Load your most complex customer price arrangements and promotions. Raise 20 real orders; count the overrides.
- Pick, pack and ship. Process a real day of orders through Pick Lists and Delivery Notes on a scanner. Time it.
- Replenishment. Set reorder levels for your top 200 items and compare the suggested purchases with what your buyers actually ordered last month.
- Landed cost. Allocate freight and duty for one real import shipment and check item valuations.
- Integrations. List every connector (e-commerce, EDI, carriers, payments, tax). For each one, find the ERPNext route: built-in, a Frappe app, a third-party connector or custom work.
- Month end. Close a trial month with your finance team: stock valuation, reconciliation and aged reports.
Integrations are often the deciding factor. Acumatica’s Licensing Guide lists connectors for platforms such as Shopify, BigCommerce and Amazon as available options. If your business runs on those, price the equivalent ERPNext route explicitly before you decide.
Getting data out of Acumatica
Your partner can export masters and open transactions through Generic Inquiries, export scenarios or the web API. Acumatica’s Licensing Guide also describes an optional Backup Access Service that lets customers download their latest ten daily backups over secure FTP, which is useful for keeping a full copy of history. Plan the move like this:
| Acumatica data | ERPNext target | How |
|---|---|---|
| Items, customers, vendors, contacts | Items, Customers (ERPNext Customer documentation), Suppliers (ERPNext Supplier documentation) | Export, clean, load with Data Import (ERPNext Data Import documentation) |
| Price lists and customer pricing | Price Lists, Item Prices, Pricing Rules | Rebuild, then test against real orders |
| Open sales and purchase orders | Sales Orders, Purchase Orders | Freeze changes during cut-over |
| Stock by warehouse, location, lot and serial | Stock Reconciliation (ERPNext Stock Reconciliation documentation) | Count high-value stock |
| Open AR and AP | Opening invoices (ERPNext opening balance documentation) | Reconcile to aged reports |
| GL balances | Opening trial balance | Keep Acumatica history available read-only or archived |
Check your contract before you plan the timeline: data access after a subscription ends is governed by your agreement, so get the full export and backup done while the subscription is active.
Costs: what is published
| Item | USD (published) | GBP | Source |
|---|---|---|---|
| Acumatica subscription, renewal and upgrade services | Quote only; no estimate given | Quote only | Acumatica pricing 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.79 (indicative) | Frappe Cloud pricing page |
| ERPNext on Frappe Cloud, dedicated servers | From $40 per month | About £30.33 (indicative) | Frappe Cloud server plans page |
Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.79) and servers from $40 a month (about £30.33), checked on Nov 18, 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.3187 per £1 for 16 Nov 2026, the latest published figure when we checked on Nov 18, 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 50 to 500 user distributor, the hosting line is small on either side. Compare the five-year cost of Acumatica subscription plus upgrade services and customisation retesting with the five-year cost of ERPNext implementation, hosting, support and your own internal effort.
A 60-day decision plan
| Weeks | What to do | Output |
|---|---|---|
| 1 to 2 | Confirm your release and its retirement status with your partner from the support portal policy; list customisations, add-ons and integrations | Status and a customisation inventory |
| 3 to 4 | Get a written upgrade plan and renewal quote from your partner | Upgrade cost and timeline |
| 5 to 7 | Run the distribution fit tests in ERPNext | Pass, configure or develop, per test |
| 8 | Compare five-year costs, risk and effort; decide | Recommendation |
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| Light customisations, happy with Acumatica | Upgrade Acumatica | Included in the subscription; least disruption |
| Heavy custom code, every upgrade is a project | Price both seriously | Recurring retest cost vs one-off migration |
| Must own the code or avoid subscriptions | ERPNext | GPL-3.0, self-host or Frappe Cloud |
| Relies on Acumatica commerce connectors | Upgrade Acumatica, unless ERPNext routes are proven | Integrations decide the risk |
| Private Cloud with no upgrade in years | Upgrade plan now | Retired versions are not supported under the agreement |
Best for, and wrong choice when
ERPNext is best for
Distributors with 50 to 500 users who want to own and host their ERP, whose Acumatica customisations make every upgrade expensive, and who have the internal capacity to run a full ERP migration.
Upgrading Acumatica is best for
Most distributors on a retired release: the upgrade is included in the subscription, the product is current, and the data and partner stay in place.
ERPNext is the wrong choice when
The only problem is one overdue upgrade, your business depends on Acumatica-specific connectors you have not replaced, or you cannot spare people for fit testing, data cleaning and training.
Frequently asked questions
Are retired Acumatica versions supported?
No. Acumatica’s Support Subscription Agreement (July 2026) says retired versions are not supported under the agreement, and that supported versions are set out in the Product Support Lifecycle Policy on the Acumatica Support Portal.
How long is an Acumatica release supported?
Acumatica’s Licensing Guide (April 2026) says that in most cases each upgrade release is supported for 18 months and then retired. Exact dates are in the lifecycle policy on the support portal.
Do I have to pay for an Acumatica upgrade?
Acumatica’s Licensing Guide says software updates and upgrades are included with SaaS and Private Cloud subscriptions. You will usually pay a partner for upgrade services and for retesting customisations.
Is Acumatica priced per user?
Acumatica’s pricing page says “Unlimited Users” and prices on applications, usage and resources, and deployment. Its Licensing Guide also describes a Named User Licensing option. Prices are quote-based; we give no estimate.
Can ERPNext handle a 50 to 500 user distributor?
Often, for core distribution: items, warehouses, pricing rules, pick lists, put-away rules, landed costs, batches and multi-company accounting are standard. Test pricing, picking and integrations with your own data before deciding.
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.79 and £30.33 at the Bank of England rate for Nov 16, 2026; checked Nov 18, 2026). Implementation is separate.