Infor Lawson v10 End of Support: What It Means and What Your Options Are

If you run Infor Lawson S3 on-premises, you’ve probably seen a date. Infor’s published lifecycle currently lists end of maintenance for on-premises Lawson v10 at December 31, 2030, with extended maintenance available for a period after that. Infor has revised lifecycle dates before, so treat that as “confirm with your account manager in writing,” not gospel. But the direction isn’t in doubt: Lawson S3 on-prem is a product Infor is retiring in favor of CloudSuite, and the clock is running.

Here’s what the date actually means for the person responsible for the environment, and the three realistic paths.

What stops, and what doesn’t

What stops at end of maintenance: new patches and fixes, regulatory updates (year-end tax tables, W-2/1095 changes), certified compatibility with new OS and database versions, and standard support cases.

What doesn’t stop: the software. Lawson will keep running after 2030 exactly as it did before. Plenty of organizations still run Lawson 9 today. The risk isn’t that it turns off; it’s that it becomes unsupportable — an unpatched WebSphere on an unsupported Windows Server against an out-of-support database, holding every employee’s data.

What’s already stopped: Infor OS and Infor OS Lite support for on-prem v10 ended in March 2025, which is why so many environments are already on a middleware stack nobody will patch.

The real risks, in order

1. Regulatory updates. If you run payroll in Lawson past end of support, you own the tax tables. That alone ends most organizations’ Lawson payroll before 2030.
2. An unsupported ERP holding SSNs and bank accounts is the softest target on your network. Cyber insurance questionnaires increasingly ask about it by name.
3. The administrators who know Lawson are retiring. The ones who know Lawson 9’s lawappinstall quirks are already gone.
4. Extended maintenance is priced to move you off the product. Hosting and DB licensing continue regardless.

Three paths

Path 1: Move to Infor CloudSuite (or another ERP), and archive Lawson. The most common path. The new system takes open items and a few years of balances; the Lawson history — twenty years of it, typically — goes to an archive, and the Lawson environment is decommissioned. This is the path Boston Medical Center, Broward Health, The Christ Hospital, and many others have taken.

Path 2: Stay on Lawson, but only as history. You’ve already moved transactions elsewhere; Lawson is read-only. This is where most organizations actually are, and it’s the most expensive place to stay: you’re paying hosting, database licensing, and an administrator’s time to keep a read-only database alive. Our post on the real cost of a read-only legacy ERP puts numbers on it. The fix is the same as Path 1 — archive and decommission — without the ERP project.

Path 3: Stay on Lawson, live, past end of support. Legitimate for a while if you’re mid-migration or have a hard reason. Plan for extended maintenance costs, a self-managed regulatory-update process, and a security exception you’ll have to defend at every audit.

What “archive Lawson” has to mean

Not a database backup. Not a table export. The Lawson application, in a form your AP, payroll, HR, and finance users can search without help:

• Every table, every year, including the *HIST tables and attachments.
• Lawson’s security model — process levels, companies, accounting units — reproduced as roles.
• The standard inquiries: vendor payment history, employee pay and job history, GL account detail, PO history.
• Sign-on through your identity provider.
• Proof of completeness: row counts and checksums per table.

APIX does this specifically for Lawson — it started there, and the company behind it has been supporting Lawson environments since 2003. The archive deploys into your own AWS account, and the load from a typical Lawson environment to a decommissionable source runs about 30 days.

What to do this quarter

• Get your lifecycle dates from Infor in writing.
• List what still transacts in Lawson (payroll especially) and when it stops.
• Price what the Lawson environment costs to keep for another five years.
• Decide whether you’re archiving now (Path 2) or after the new ERP goes live (Path 1). Either way the archive is the same project; the only question is when the Lawson bill stops.

If you’d like to work through your specific environment and timeline, book a discovery session.