Infor M3 on-premises and the Tech 2.0 upgrade: CloudSuite vs ERPNext
Short answer
We found no public Infor end-of-support date for M3 13.4 on-premises, so this guide gives none. What partners describe is a forced technical step: Infor partner Meridion says M3 13.4 on-premises customers must move to Tech 2.0 (Java 17, a new LifeCycle Manager and Grid, updated integration components) “to remain compatible and supported”, that older M3 versions are not compatible with Tech 2.0, and that some Tech 1.0 products must be replaced. Infor’s own documentation recommends Infor Local Technology Runtime (LTR) over on-premises Infor OS, which it lists as moving to sustaining maintenance. Infor’s M3 page points older and on-premises customers to the multi-tenant cloud edition through Infor Leap. So you have three real paths: Tech 2.0 on-premises, CloudSuite, or a different ERP. ERPNext (open source, GPL-3.0, no licence fee) suits mid-size distributors and simpler discrete or batch producers. Be honest about process manufacturing: we found no potency, catch-weight, dual-unit or tank-scheduling features in its documentation. Infor is quote-only, so we give no Infor estimate.
Contents
- Who this guide is for
- What is actually known about M3 13.4 on-premises
- What “sustaining maintenance” means under Infor’s policy
- Three paths compared: Tech 2.0, CloudSuite, ERPNext
- Process manufacturing fit, stated honestly
- Distribution and discrete fit
- Integrations and the M3 estate
- Data migration from M3
- A phased plan
- Costs: what is published
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for CIOs, IT managers and finance and operations directors at mid-size manufacturers and distributors running Infor M3 on their own infrastructure, usually on release 13.4, sometimes on something older. M3 started life as Movex at Intentia, became Lawson M3 and, after Infor acquired Lawson in 2011, Infor M3, according to Infor’s Infor M3 product page. Infor positions it for fashion, food and beverage, chemicals, distribution and equipment dealers, and industrial manufacturing.
We implement ERPNext, so read our view with that in mind. M3 is a deep, industry-specific system. For many M3 sites, especially chemical and food producers that rely on its process functions, staying with Infor, on-premises or in the cloud, is the right answer. This guide is for the sites where the on-premises technical upgrade has forced a decision anyway, and the board wants to know whether a smaller, open-source system is a realistic alternative.
It is part of our series on legacy ERP deadlines; the legacy ERP end-of-support hub lists every vendor date we have confirmed. For Infor’s other enterprise ERP, see Infor LN on-premises; for another process-heavy system, see QAD MFG/PRO and Standard Edition.
Sources, checked on Nov 21, 2026: the Infor M3 product page, the Infor M3 Documentation List, Tech 2.0 (docs.infor.com), the Infor documentation page “Infor OS or Infor Local Technology Runtime”, the Infor General Product Lifecycle Policy (PDF on infor.com), Meridion’s “M3 13.4 Tech 2.0” page (Infor partner), 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 M3 13.4 on-premises
| Source | What it says | How much weight to give it |
|---|---|---|
| Infor M3 product page | M3 runs on the Infor Industry Cloud Platform and is “built on AWS” as a multi-tenant cloud solution. “Existing Infor M3 customers on older or on-premise versions can move to the multi-tenant cloud edition through Infor Leap, a fixed-fee, fixed-timeline migration program.” Roadmaps and upgrade planning sit in Infor’s Customer Center | Infor’s own page: high |
| Infor M3 Documentation List, Tech 2.0 (docs.infor.com) | Infor publishes an “Infor M3 Documentation List (On-premises) Tech 2.0” for M3 13.4, covering the Business Engine, planning and scheduling workbenches, the Graphical Lot Tracker, integration and reporting | Infor’s own documentation: confirms Tech 2.0 is a real on-premises release; no dates |
| Infor documentation page “Infor OS or Infor Local Technology Runtime” | In Infor’s EPM documentation, Infor OS 12.0.40 or higher is listed as supported but “will be moved to sustaining maintenance with the 2024.12 release. We recommend you use Infor Local Technology Runtime.” | Infor’s own documentation, written for a different product; shows the direction for on-premises Infor OS |
| Meridion’s “M3 13.4 Tech 2.0” page (Infor partner) | M3 13.4 on-premises customers face “two parallel needs”: move from Infor OS to Infor LTR, and upgrade to Tech 2.0, which “is required for your solution to remain compatible and supported”. Tech 2.0 brings Java 17 and upgrades to LifeCycle Manager, Grid and integration components; it applies only to 13.4, and some Tech 1.0 products “must be replaced with alternative solutions” | Partner source: useful detail, not confirmation. It also sells the upgrade |
Infor’s M3 page sends customers to its Customer Center knowledge base for roadmaps and upgrade planning, and its Tech 2.0 documentation list says some links need a customer portal login. We could not read those pages, so we give no date for the end of support of M3 13.4 on Tech 1.0, and we do not repeat partner dates for Infor OS either. If you are an M3 customer, ask Infor for the Tech 2.0 announcement and the M3 lifecycle policy in writing.
What we can say safely
If you run M3 13.4 on-premises, plan for a technical upgrade to Tech 2.0 and a move from Infor OS to LTR if you intend to stay on-premises. If you run an M3 version older than 13.4, Tech 2.0 is not available to you without first reaching 13.4. Both steps cost time and money, which is why this is a natural moment to compare options.
What “sustaining maintenance” means under Infor’s policy
Infor’s Infor General Product Lifecycle Policy (PDF on infor.com) defines three stages. Mainstream Maintenance includes Priority 1 and 2 fixes, updates, and regulatory and statutory enhancements. Extended Maintenance, when available and for an additional fee, covers fixes only as needed for Severity 1 incidents. Sustaining Maintenance gives access to pre-existing fixes and Infor support, for a period Infor determines, but excludes “any new updates and fixes”.
For an M3 site this matters at two levels. The application release (13.4 and its Business Engine) and the technology underneath it (Infor OS, Grid, Java) each have their own status. A business can be on a supported M3 release and still be running technology components that are past their useful supported life. Tech 2.0 is Infor’s answer for on-premises customers; CloudSuite moves the whole problem to Infor.
Three paths compared: Tech 2.0, CloudSuite, ERPNext
| Tech 2.0 on-premises | M3 CloudSuite (Infor Leap) | ERPNext | |
|---|---|---|---|
| What changes | Technology stack (Java 17, LifeCycle Manager, Grid, integration components) and a move from Infor OS to LTR, per Meridion | Move to Infor’s multi-tenant cloud edition on AWS; standardise on Infor’s preconfigured industry processes | New system: open-source ERP on Linux with MariaDB, self-hosted or on Frappe Cloud |
| Customisations | Review; some Tech 1.0 products must be replaced, per Meridion | Infor says Leap maps customisations and standardises on preconfigured processes | Rebuild what you still need as configuration or apps |
| Process depth | Keeps everything M3 does today | Keeps M3 functions, plus Infor’s cloud platform services | Narrower: see the fit tests below |
| Who runs the platform | You | Infor | You or Frappe Cloud |
| Price | Quote only | Quote only (Infor describes Leap as fixed-fee) | No licence fee; hosting from $5 a month (site) or $40 a month (server) |
| Best when | You must stay on-premises and M3 fits | You want M3 without running it | M3 is more system than the business uses |
Infor publishes no M3 licence, subscription, Leap or upgrade prices on the pages we checked, so we give no Infor estimate. Ask for written quotes for both Infor paths, with the same scope, before you price ERPNext against them.
Process manufacturing fit, stated honestly
Infor’s M3 page highlights food and beverage (“variable raw materials, strict quality rules”) and chemicals (“planning, regulatory controls, traceability, tank scheduling”) as core markets. If you are a process manufacturer, run these tests first. This is where ERPNext is weakest relative to M3.
| Process requirement | In ERPNext | Fit |
|---|---|---|
| Fixed recipes with yield and process loss | Bill of Materials with scrap percentages; a scrap item identical to the product is treated as process loss (ERPNext Bill of Materials documentation) | Good |
| Lots with expiry dates and lot-tracked transactions | Batches with expiry; Serial and Batch Bundle on every stock transaction (ERPNext Batch documentation; ERPNext Serial and Batch Bundle documentation) | Good |
| Quality inspection on receipt and despatch | Quality Inspection on receipts and deliveries (ERPNext Quality Inspection documentation) | Good for inspection; test lot hold and release |
| Substitute ingredients | Item Alternatives for BOM raw materials (ERPNext Item Alternative documentation) | Good for simple substitution |
| Potency or strength-based formula adjustment | Not found in ERPNext’s documentation | Gap |
| Catch weight and dual units of measure | UOM conversion factors are set up in advance (ERPNext UOM documentation); no catch-weight or dual-unit tracking found | Gap for meat, cheese, chemicals sold by weight and volume |
| Tank and vessel scheduling | Workstation-based capacity planning only (ERPNext Capacity Planning documentation) | Gap |
| Co-products and by-products | Scrap or secondary items with a rate on the BOM | Test with your real co-product costing; check your ERPNext version, as v16 replaces the Scrap Items table with Secondary Items |
| Regulatory documents (SDS, labelling, allergen declarations) | Not found as standard features | Gap; keep a specialist tool |
Where we would say no
If potency-adjusted formulas, catch weight, tank scheduling or regulated chemical documentation are central to how you make money, ERPNext is the wrong replacement for M3 without significant custom development. Stay with Infor, or look at systems built for process manufacturing.
Distribution and discrete fit
Mid-size M3 distributors and equipment dealers, and simpler discrete producers, usually find a better fit:
| In M3 | In ERPNext | Notes |
|---|---|---|
| Item, warehouse and facility structure | Items (ERPNext Item documentation), Warehouses (ERPNext Warehouse documentation), Companies | Decide how M3 facilities map to companies or warehouses |
| Customer order flow and pricing | Quotations, Sales Orders, Price Lists and Pricing Rules (ERPNext Sales Order documentation; ERPNext Pricing Rule documentation) | Load your real price agreements and test a busy order day |
| Supplier agreements and rebates | Blanket Orders (ERPNext Blanket Order documentation); Pricing Rules | Supplier rebate settlement is not a standard ERPNext feature we found; M3 lists a Supplier Rebate module |
| Picking, putaway and deliveries | Pick Lists, Putaway Rules, Delivery Trips, Shipments (ERPNext Pick List documentation; ERPNext Putaway Rule documentation; ERPNext Delivery Trip documentation) | Not a full WMS |
| Replenishment and planning | Reorder levels and Production Plans (ERPNext reorder level (auto material request) documentation; ERPNext Production Plan documentation) | Test with a real month of demand |
| Discrete production | Work Orders, Routings, Job Cards (ERPNext Work Order documentation; ERPNext Routing documentation; ERPNext Job Card documentation) | Good for standard make-to-stock and make-to-order |
| Subcontracting | Subcontracting with material sent to the supplier (ERPNext Subcontracting documentation) | Good |
| Import costs | Landed Cost Vouchers (ERPNext Landed Cost Voucher documentation) | Good |
| Multi-company and multi-currency finance | Inter-company invoices, multi-currency accounting, accounting dimensions (ERPNext inter-company invoices documentation; ERPNext multi-currency accounting documentation; ERPNext accounting dimensions documentation) | Infor says M3 is available in 74 countries; check your localisation needs country by country |
Rentals, equipment service and lifecycle management, which Infor lists for M3 distribution and equipment dealers, are areas to test carefully; ERPNext has projects and timesheets, but not a dedicated rental counter.
Integrations and the M3 estate
M3 sites rarely run M3 alone. Infor’s Infor M3 Documentation List, Tech 2.0 (docs.infor.com) includes Enterprise Collaborator tools, M3 API tools, Business Engine BODs and business messages, which is how many sites connect M3 to warehouses, e-commerce, EDI and finance tools. Before you price anything, list every interface and its owner.
- Interfaces you would rebuild anyway. Meridion says Tech 2.0 updates integration components and that some Tech 1.0 products must be replaced. If much of that interface work is needed to stay on M3, the incremental cost of rebuilding the same interfaces against ERPNext’s REST API is smaller than it first looks.
- EDI. We found no EDI module in ERPNext’s documentation. Plan for an EDI provider and an integration.
- Reporting. M3 sites often have years of reports in Infor’s reporting tools. Decide which ones are used, and rebuild only those.
ERPNext lets you add fields and approval flows without code; see the ERPNext Custom Field documentation and ERPNext Workflows documentation.
Data migration from M3
| M3 data | ERPNext target | How |
|---|---|---|
| Items, units, customers, suppliers | Items, UOMs, Customers (ERPNext Customer documentation), Suppliers (ERPNext Supplier documentation) | Extract from the M3 database, clean, load with Data Import (ERPNext Data Import documentation) |
| Active product structures and recipes | Bills of Materials and Routings | Only products you will make again |
| Lot-controlled stock | Stock Reconciliation with batches (ERPNext Stock Reconciliation documentation) | Count and verify lots and dates before go-live |
| Open orders | Sales Orders, Purchase Orders, Work Orders | Finish open manufacturing orders in M3 where you can |
| Open AR and AP | Opening invoices (ERPNext opening balance documentation) | Reconcile to aged reports |
| GL balances | Opening trial balance on a new chart of accounts (ERPNext Chart of Accounts documentation) | Keep M3 read-only for history and lot traceability |
Keep a read-only copy of M3 data for lot genealogy and audit history. For food and chemical producers this is a regulatory question, so agree retention with your quality team before cut-over.
A phased plan
| Phase | What happens | Typical output |
|---|---|---|
| 1. Status | Ask Infor in writing for your M3 and Infor OS status, the Tech 2.0 announcement, and Leap terms | A clear picture of what staying costs |
| 2. Fit tests | Process tests above, a busy order day, planning and a month end in an ERPNext trial | Pass, configure, develop or stop, per test |
| 3. Quotes | Tech 2.0 upgrade quote, Leap quote, ERPNext proposal with the same scope | Five-year comparison |
| 4. Build | Configure ERPNext, rebuild interfaces and reports you kept, two full trial loads | Signed-off test cycles |
| 5. Cut-over | Go live at a period end; M3 read-only for history | Live ERPNext, archived M3 |
If the process fit tests fail in phase 2, stop there. The output is still useful: a clear reason to choose between Tech 2.0 and CloudSuite.
Costs: what is published
| Item | USD (published) | GBP | Source |
|---|---|---|---|
| Infor M3 Tech 2.0 upgrade, maintenance, CloudSuite, Infor Leap | Quote only; no estimate given | Quote only | Infor M3 product 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.
An M3 site of this size will usually want dedicated hosting and a support partner for ERPNext; price both. On the Infor side, include the Tech 2.0 project, LTR, infrastructure and in-house administration in the “stay on-premises” column.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| Potency, catch weight, tank scheduling or regulated chemical documents are core | Tech 2.0 or CloudSuite | We found no ERPNext support for these |
| Must stay on-premises and M3 fits well | Tech 2.0 with LTR | Keeps M3 supported on your infrastructure, per partners |
| Want M3 without running it | CloudSuite through Infor Leap | Infor’s stated path for older and on-premises customers |
| Mid-size distributor using a fraction of M3 | ERPNext worth pricing | Strong fit for stock, pricing, purchasing and finance |
| Older than 13.4 with heavy technical debt | Price all three | You face an upgrade before Tech 2.0 anyway |
Best for, and wrong choice when
ERPNext is best for
Mid-size distributors, equipment parts businesses and simpler discrete or batch producers on M3 on-premises who use a fraction of M3’s depth and want to own their system rather than fund a technical upgrade or a cloud move.
Staying with Infor is best for
Process manufacturers that rely on M3’s food, chemical or fashion functions, and multinational groups that depend on its localisations.
ERPNext is the wrong choice when
Process functions we could not find in ERPNext are central, you need many country localisations at once, or nobody can own the new system after go-live.
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 staying with Infor is the better answer.
Frequently asked questions
When does support for M3 13.4 on-premises end?
We found no public Infor date, so we give none. Infor partners say M3 13.4 on-premises must move to Tech 2.0 to stay supported. Ask Infor for the Tech 2.0 announcement and lifecycle policy in writing (checked Nov 21, 2026).
What is M3 Tech 2.0?
Per Infor partner Meridion, a technical upgrade of M3 13.4 on-premises: Java 17, upgraded LifeCycle Manager, Grid and integration components. Older M3 versions are not compatible, and some Tech 1.0 products must be replaced. Infor publishes a Tech 2.0 documentation list on docs.infor.com.
What is Infor Local Technology Runtime?
Infor’s on-premises technology runtime that Infor’s documentation recommends instead of on-premises Infor OS, which it lists as moving to sustaining maintenance.
Can I move from M3 on-premises to the cloud?
Infor says existing M3 customers on older or on-premises versions can move to the multi-tenant cloud edition through Infor Leap, a fixed-fee, fixed-timeline migration programme. Infor publishes no price.
Can ERPNext replace M3 for a process manufacturer?
Sometimes, for simpler recipes. ERPNext handles BOMs with process loss, batches with expiry and quality inspections. We found no potency, catch-weight, dual-unit or tank-scheduling features in its documentation, so test those first.
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.