Infor Lawson ERP: S3, M3, Support Timeline & Migration Paths

Infor Lawson ERP

Lawson ERP is still running in hospitals, universities and public-sector finance departments across the US — and it is one of the most confusingly named legacy systems in the market. The product was bought by Infor in 2011, split across two very different code bases, and then renamed more than once. If you have inherited a Lawson ERP system and are trying to work out what you actually own, what Infor still supports, and what your options are, this page is an independent answer.

Updated July 2026

ERP Research is independent and vendor-neutral — no vendor pays for placement or ranking, including on this page.

Get Pricing Build Your Requirements

What Is Lawson ERP?

Lawson ERP is a family of enterprise resource planning systems originally built by Lawson Software and acquired by Infor in 2011. It covers financials, supply chain, human capital management and procurement, and is deployed most heavily in healthcare, higher education and the public sector. Today it is sold and maintained under Infor branding.

The name "Lawson" now refers to a lineage rather than a single product. Lawson Software was founded in 1975 in Minneapolis, Minnesota — moving its headquarters to St. Paul in 1999 — and grew into a leading ERP supplier for mid-sized and service-sector organisations — particularly hospitals, where it became a default choice for finance, supply chain and payroll. In 2006 Lawson merged with the Swedish vendor Intentia, absorbing Intentia's Movex manufacturing product. In 2011 Infor acquired the combined company, and since then the Lawson products have been folded into Infor's CloudSuite portfolio and renamed.

That history is why two organisations can both say "we run Lawson" and mean architecturally unrelated systems. Establishing which line you are on is the first step in any upgrade or replacement decision.

Lawson ERP at a Glance

Lawson S3 vs Lawson M3: Which One Do You Have?

The single most useful thing to establish about a Lawson ERP system is whether it is S3 or M3. They came from different companies, run on different technology, and have different successors.

Lawson S3 — the original Lawson product line, named for Staff, Source, Serve. It targets service organisations: healthcare, higher education, government, retail and financial services. Its strengths are financials, human capital management, payroll and supply chain, and it is the line most US hospitals mean when they say "Lawson."

Lawson M3 — originally Intentia's Movex, named for Make, Move, Maintain. It targets manufacturers and distributors, with particular depth in food and beverage, fashion, chemicals, distribution and equipment service management. It arrived through the 2006 Intentia merger rather than being built by Lawson.

If you are unsure which you run, the module naming is the quickest tell: S3 environments use short alphabetic system codes such as GL, AP and HR, and are usually accessed through Lawson Portal or, on newer deployments, Infor OS Portal (formerly Ming.le); M3 environments use alphanumeric program identifiers such as OIS100 or MMS001, and the M3 business engine.

Where Lawson Went: Infor FSM, M3 and the CloudSuite Rebrand

Neither Lawson line was discontinued at acquisition — both were re-platformed and renamed, which is the root of most of the confusion around the product today.

Lawson S3 became Infor Financials & Supply Management, usually shortened to Infor FSM, and is delivered as part of Infor CloudSuite Financials & Supply Management — a multi-tenant cloud application aimed at the same service industries S3 served. Infor also built out CloudSuite Financials and related modules such as CloudSuite EAM and CloudSuite CRM around it.

Lawson M3 became Infor M3 and Infor CloudSuite M3, retaining the M3 name and continuing as Infor's manufacturing and distribution ERP for process and discrete industries.

One split catches teams out repeatedly: S3's HR and payroll functionality does not go to FSM. It migrates separately to Infor Global Human Resources (GHR), which is why a single S3 estate typically becomes two CloudSuite projects rather than one — a scoping surprise that lands late if nobody flags it early.

Both migrations sit on the Infor technology stack — the Landmark application framework (originally Lawson's own, inherited by Infor), Infor OS, Infor OS Portal (formerly Ming.le, retired April 2024) for the user interface, and Infor Process Automation for workflow. On-premises estates have their own moving target here: Lawson V10 on-prem customers were required to move to the Infor Local Technology Runtime (LTR) by 31 March 2025. Moving from on-premises Lawson to the CloudSuite successor is a re-implementation with data migration and process redesign, not a version upgrade. Organisations that treat it as a patch consistently underestimate it. Our Infor LN to CloudSuite migration guide covers the same dynamic on Infor's other legacy line, and the Infor implementation cost breakdown sets out where the budget actually goes.

Lawson ERP Support: What "Still Supported" Actually Means

Infor has published an end-of-maintenance date for on-premises Lawson v10 of 31 December 2030, with extended maintenance available for roughly two years beyond that on qualifying deployments. Infor has revised its published lifecycle policies more than once, and what applies to you depends on your release, deployment model and contract terms.

The important distinction is between a product that is maintained and one that is invested in.

Lawson S3 and M3 on-premises releases receive regulatory and security maintenance under active support contracts, but Infor's roadmap investment goes into the CloudSuite successors. In practice that means new capability, and increasingly new integrations and partner tooling, land on CloudSuite rather than on the legacy releases.

Confirm your own dates directly. Do not plan a multi-year programme against a date you read on a third-party site — including this one. Ask your Infor account manager for the current lifecycle statement covering your exact release and deployment model, and get it in writing.

The practical planning point is that a full ERP replacement runs well beyond the implementation window vendors quote, because it also includes selection, data remediation and post-go-live stabilisation. With standard maintenance running to the end of 2030, that date is closer than it looks. Organisations that start scoping early keep control of the timeline and the budget; those that wait until support genuinely lapses migrate under pressure and pay for it.

Lawson ERP Modules

Module coverage differs by line. The S3 estate, being the more common in healthcare and the public sector, is set out below.

Financials

General Ledger, Accounts Payable, Accounts Receivable, Cash Management, Asset Management, Project Accounting, Grant Management, Budgeting and Currency Management.

Supply Chain Management

Inventory Control, Purchase Order, Requisitions, Contract Management, Requisition Self-Service and Supply Chain Analytics — the module set that made Lawson a fixture in hospital materials management.

Human Capital Management

Human Resources, Payroll, Benefits Administration, Absence Management, Personnel Administration, Talent Acquisition and Employee/Manager Self-Service.

Procurement

Strategic Sourcing, Contract Management, Supplier Order Management and Punchout catalogue integration.

Platform & Tooling

Lawson Portal, Infor OS Portal (formerly Infor Ming.le), Infor Process Automation (IPA), Lawson Security, Infor Spreadsheet Designer and the Landmark framework.

For manufacturers on M3, the equivalent depth sits in production planning, shop floor execution, distribution order management, equipment service management and food-and-beverage-specific traceability.

Pros & Cons of Lawson ERP

Pros

• Deep sector fit. Lawson S3's healthcare, higher education and public-sector functionality — grant accounting, position budgeting, hospital supply chain — reflects decades of vertical development that generic ERP does not match out of the box.
• Stable and well understood. Long-running Lawson estates are typically heavily tuned to local process, and they work. Stability is a genuine argument for not moving.
• Strong supply chain and HCM core. The materials management and payroll modules remain the reason many hospitals adopted it and the hardest parts to replace.
• Established consultant ecosystem. A mature third-party market exists for support, hosting and managed services independent of Infor.
• Defined successor path. Unlike some legacy ERP, there is a vendor-supported destination in Infor CloudSuite rather than a dead end.

Cons

• Innovation has moved on. Roadmap investment goes to the CloudSuite successors; the legacy on-premises releases are maintained, not advanced.
• Dated user experience. The interface and navigation predate modern cloud ERP, which affects adoption, training time and self-service uptake.
• Migration is a re-implementation. Moving to FSM or CloudSuite M3 means data migration and process redesign, not an upgrade — with cost and timeline to match.
• Customisation lock-in. Years of local modification and interfaces make estates expensive to move, and the depth of customisation drives migration cost more than the target platform does.
• Ageing skills pool. Lawson S3 and IBM i skills are increasingly sourced through third-party managed-service firms rather than hired directly, which raises support cost and delivery risk.
• Naming confusion. The S3/M3/FSM/CloudSuite naming makes it genuinely hard to buy support, hire, or scope work accurately.

Lawson ERP Alternatives and Migration Paths

There is no single successor to Lawson. Infor positions CloudSuite as the native next step, but for service-sector organisations the realistic shortlist usually widens — particularly in healthcare and higher education, where Workday and Oracle are the two names that most often appear on the shortlist against Infor, and are the most commonly documented destinations for Lawson estates that leave.

Ranges are typical implementation windows for mid-to-large Lawson estates and vary widely with customisation depth and scope; they exclude selection and post-go-live stabilisation.

Infor CloudSuite is the path of least surprise where the vertical functionality is the reason you are on Lawson in the first place; the Infor overview and CloudSuite pricing breakdown set out the shape of it, and Infor alternatives covers the wider market. Workday is the most common competitive displacement in healthcare and higher education, where a combined finance and HCM suite maps neatly onto what S3 was doing. Staying put and modernising — rehosting, improving integration, fixing reporting — is a legitimate interim answer for organisations that cannot fund a replacement yet, provided it is a deliberate decision with a review date rather than drift.

As with any legacy migration, cost is driven far more by how heavily your instance has been customised than by which platform you choose. Building a clean requirements baseline first, rather than replicating twenty years of accumulated Lawson customisation, is the single biggest lever on the final number. The same pattern plays out on other legacy estates — see our Oracle E-Business Suite and Microsoft Dynamics NAV guides.

How to Decide Whether to Stay on Lawson or Replace It

1. Identify exactly what you run. Confirm the line (S3 or M3), the release, the deployment model and the database and OS platform. Every downstream decision depends on this, and it is routinely recorded incorrectly in asset registers.
2. Get the lifecycle position in writing. Ask Infor for the current support statement covering your specific release and deployment, rather than relying on published summaries or third-party dates.
3. Measure your customisation debt. Inventory the modifications, interfaces and reports actually in use — not the ones that exist. This number, more than any vendor quote, predicts what a migration will cost.
4. Separate the business case from the support deadline. Decide whether the platform is limiting the organisation on its merits. "Support is ending" is a timing constraint, not a business case, and it produces poor system selections when treated as one.
5. Build a requirements baseline before you shortlist. Define what you need now, independent of what Lawson does today, so you evaluate against current process rather than replicating legacy behaviour.
6. Shortlist against your sector, not the general market. Healthcare, higher education and public-sector requirements — grant accounting, position control, hospital supply chain — eliminate a lot of otherwise-capable products very quickly.

---

Frequently Asked Questions

Is Lawson still used today?

Yes. Lawson remains in production at many hospitals, universities and public-sector bodies, particularly in the United States, and is still supported under Infor contracts. It is a mature legacy platform rather than a discontinued one, though Infor's development investment now goes into the CloudSuite successors.

Who owns Lawson software now?

Infor. Infor, backed by Golden Gate Capital, acquired Lawson Software in a deal valued at approximately $2 billion ($11.25 per share) that completed in July 2011. Lawson's products were subsequently rebranded and folded into Infor's portfolio — S3 became Infor Financials & Supply Management, and M3 continues as Infor M3 and CloudSuite M3.

What is the difference between Lawson S3 and M3?

S3 stands for Staff, Source, Serve and targets service organisations such as healthcare, education and government, with strengths in financials, HCM and supply chain. M3 stands for Make, Move, Maintain and targets manufacturers and distributors. M3 came from Intentia's Movex product via the 2006 merger, so the two lines are architecturally unrelated.

Is Lawson an ERP system?

Yes. Lawson is a full enterprise resource planning suite covering financials, supply chain, procurement and human capital management across integrated modules, rather than a single-function finance or HR application.

What replaced Lawson ERP?

Infor Financials & Supply Management (FSM), delivered through Infor CloudSuite, replaced Lawson S3's finance and supply chain modules, while its HR and payroll functionality moved to Infor Global Human Resources (GHR). Infor M3 and CloudSuite M3 succeeded Lawson M3. All are re-implementations rather than upgrades, so moving to them involves data migration and process redesign.

How much does it cost to migrate off Lawson?

Cost varies too widely to quote a single figure — it is driven mainly by the depth of customisation, the number of live integrations, data quality and how much process redesign is in scope, rather than by the target platform. Model your own case with the ERP TCO calculator and treat vendor licence cost as only one component of the total.

---

Related Resources

• Infor ERP overview
• Infor CloudSuite Financials module overview
• Infor CloudSuite EAM module overview
• Infor LN to CloudSuite migration guide
• Infor CloudSuite pricing breakdown
• Infor alternatives and competitors
• Infor implementation cost
• Oracle E-Business Suite: end of life and migration
• Microsoft Dynamics NAV overview
• ERP implementation checklist