Lawson v10 End of Life: Timeline, Your Options, and What to Do Now

Infor has confirmed that Lawson v10 end-of-support is December 31, 2030. After that date, no new updates, patches, or fixes will be delivered for on-premise Lawson v10 applications. If you're one of the thousands of organizations still running Lawson v10 for HCM, Payroll, FSM, or WFM—this is your complete guide to understanding what's happening, what your options are, and when to act.

The Complete Lawson v10 End-of-Life Timeline

Here's what has already happened and what's coming:

What “End of Support” Actually Means for Your Organization

Let me be specific, because “end of support” means different things to different people:

• No security patches: New vulnerabilities discovered after 2030 will not be patched by Infor. Your Lawson v10 instance becomes an increasing security liability.
• No regulatory updates: Tax tables, ACA reporting changes, state-specific payroll requirements—Infor will stop updating these. For Lawson v10 Payroll customers, this is a critical issue.
• No bug fixes: Known bugs will not be resolved. You live with them or fix them yourself.
• No new features: All development investment goes to CloudSuite. Lawson v10 has been in maintenance mode for years; after 2030, even maintenance stops.
• Declining partner ecosystem: Consulting firms and third-party vendors will phase out Lawson v10 expertise as the customer base migrates. Finding experienced Lawson v10 consultants will become increasingly difficult and expensive.

Your Options: What I Tell Every Lawson v10 Customer

After 26 years in the Infor ecosystem, here are the paths I see organizations taking:

Option 1: Migrate to Infor CloudSuite (Recommended for Most)

This is Infor's intended path and the one I recommend for most organizations. CloudSuite is the actively developed platform with continuous updates, modern architecture, and Infor's full investment.

What migrates well:

• Lawson v10 HCM → CloudSuite HCM (with integrated Talent Management, WFM, and modern Employee Self-Service)
• Lawson v10 FSM → CloudSuite Financials & Supply Management (with enhanced analytics through Birst)
• Lawson v10 SCM → CloudSuite Supply Chain Management (with demand planning and optimization tools)
• Lawson v10 Payroll → CloudSuite Payroll (cloud-native, continuously updated for compliance)
• Lawson v10 WFM → CloudSuite Workforce Management (integrated with HCM for unified workforce data)

Timeline: Expect 12-18 months for a typical Lawson v10 to CloudSuite migration, depending on the number of modules and complexity of integrations. See my complete Lawson to CloudSuite migration guide for the detailed roadmap.

Option 2: Optimize and Stabilize Lawson v10 While Planning

If you're not ready to begin a full CloudSuite migration, the interim strategy is to optimize your current Lawson v10 environment while building your migration roadmap.

This means:

• Applying all available Lawson v10 patches and updates now, while Infor still delivers them
• Upgrading underlying infrastructure (Windows Server, database) to supported versions
• Documenting all customizations, integrations, and technical debt
• Beginning the business case development for CloudSuite migration
• Conducting a CloudSuite readiness assessment to understand scope and budget

Option 3: Module-by-Module Phased Migration

Some organizations choose to migrate specific modules first rather than doing a big-bang migration. A common approach:

1. Phase 1 – Payroll first: Because regulatory compliance makes this non-negotiable. Migrate Lawson v10 Payroll to CloudSuite Payroll.
2. Phase 2 – HCM and WFM: Move Human Capital Management and Workforce Management together, since they share employee data.
3. Phase 3 – FSM and SCM: Migrate Financials & Supply Management and Supply Chain Management as the final phase.

What's Different About CloudSuite vs. Lawson v10?

For a detailed comparison, see my article on CloudSuite vs. On-Premise Lawson. Here's the executive summary:

• Architecture: Multi-tenant cloud (AWS) vs. your on-premise servers
• Updates: Continuous delivery from Infor vs. periodic upgrade projects you manage
• UI: Modern Infor OS experience vs. Lawson Smart Office / Ming.le
• Analytics: Embedded Birst vs. Crystal Reports and third-party BI tools
• Integration: ION middleware vs. direct database integrations and stored procedures
• Customization: Extensibility framework vs. direct code modification
• AI & Automation: Access to Infor Velocity Suite for process mining and intelligent automation

The Cost Question: How to Budget for Lawson v10 Migration

Every CFO wants to know: what does this cost? Here's the honest framework:

Cost of Migrating

• CloudSuite licensing: Transition from perpetual license to SaaS subscription. Infor typically offers migration incentives for existing Lawson customers.
• Implementation services: Ranges widely based on module count and complexity. Budget $500K-$3M+ for a comprehensive migration.
• Data migration: Plan for 15-20% of your implementation budget for data cleansing and migration alone.
• Change management and training: Budget 10-15% of total project cost. See why change management matters.

Cost of Not Migrating

• Increasing infrastructure costs: Aging hardware, rising database licensing, harder-to-find Lawson v10 talent
• Security exposure: Unpatched vulnerabilities after 2030
• Compliance risk: Especially for Payroll and HR regulatory requirements
• Opportunity cost: Missing modern capabilities (mobile, analytics, AI, automation) that competitors are leveraging
• Emergency migration premium: Organizations that wait until the last minute pay significantly more for accelerated timelines

A Realistic Planning Roadmap for 2026-2030

Here's the timeline I recommend for Lawson v10 customers who haven't started yet:

Industry-Specific Considerations

Healthcare

Healthcare organizations on Lawson v10 face unique challenges: Epic/Cerner integration, HIPAA compliance, clinically integrated supply chain, and 24/7 operations that make cutover planning critical. See my healthcare-specific CloudSuite guide.

Higher Education

Universities running Lawson v10 for HR and Finance need to plan around academic year cycles and often have complex fund accounting requirements that need careful redesign in CloudSuite.

Public Sector

Government organizations face additional procurement and compliance requirements. Budget cycles may require multi-year funding approval, which means starting the planning process immediately.

The Bottom Line

Lawson v10 end of life is December 31, 2030. That's a hard deadline, and the clock is ticking. The organizations that start planning now—in 2026—will have the luxury of time to do the migration right. Those that wait will face compressed timelines, higher costs, and greater risk.

After 26 years working exclusively in the Infor ecosystem, I can tell you: every successful Lawson v10 migration I've been part of had one thing in common—early planning. The technology is solvable. The data migration is solvable. The change management is solvable. But none of it works if you don't give yourself enough time.