Infor Lawson Modernization — Decision, Path, Execution

Infor lawson modernization is the decision and the execution to move an ageing Lawson S3 estate (typically deployed in 2002–2010 in US hospitals and universities) to a modern target. Three primary options: (1) Lift-and-shift to Infor CloudSuite (Lawson on Infor's cloud) — preserves Lawson skills, defers structural change, but keeps the customisation footprint and the Mongoose/IPA dependency. (2) Re-platform to Oracle Fusion — full ERP replacement, retires Lawson skill dependency, replaces IPA with OIC, replaces Mongoose with VBCS, but requires the most change management. (3) Re-platform to Workday HCM / Financial Management — alternative cloud ERP, often chosen for higher-ed institutions, requires similar change management as Fusion. The infor lawson modernization decision drives every downstream decision — migration scope, timeline, budget, change management strategy.

Five forcing functions. (1) Infor end-of-life on Lawson S3 on-premise — Infor has signalled progressive end of mainstream support, pushing customers to CloudSuite or to alternative ERPs. (2) Skill shortage — Lawson developers, IPA developers and Mongoose developers are retiring; recruiting replacements is increasingly hard and expensive. (3) Integration accumulation — 20 years of IPA flows, Mongoose customisations, point-to-point integrations have created a maintenance burden that consumes increasing IT capacity. (4) Compliance evolution — newer HIPAA, CMS, FFATA and state-specific requirements need ERP capabilities Lawson lacks. (5) M&A integration — hospital networks and university systems consolidating need unified ERP that Lawson struggles to deliver. The infor lawson modernization conversation has shifted from 'why' to 'when and how'.

Lift-and-shift to Infor CloudSuite: lower change management cost (Lawson skills transfer, IPA continues, Mongoose continues), faster to land (typically 6–12 months), preserves the existing customisation investment. But: keeps the maintenance burden (every IPA flow, every Mongoose page still needs to be maintained), keeps the skill-shortage exposure, doesn't deliver the modern ERP capabilities (embedded AI, modern UX, Redwood design, advanced analytics). Re-platform to Fusion: higher change management cost (Lawson skills retire, IPA → OIC, Mongoose → VBCS), longer to land (typically 12–18 months for full programme), but retires the customisation maintenance burden, eliminates skill-shortage exposure, delivers modern ERP capabilities. Most hospitals and universities Syntra ETL works with choose re-platform as the strategic move.

Six decision criteria. (1) Strategic ERP direction: is the parent organisation standardising on a specific cloud ERP (Oracle Fusion, Workday, SAP S/4HANA)? (2) Skill availability: is internal Lawson skill sustainable for another 5–10 years? (3) Customisation maintenance cost: what does it cost annually to maintain the IPA + Mongoose + LBI estate? (4) Compliance readiness: do current Lawson capabilities meet the next 5 years of HIPAA, CMS, FFATA and state-specific requirements? (5) M&A integration: are there ongoing consolidations that need unified ERP? (6) Change management capacity: how much organisational change can be absorbed in parallel with clinical / academic operations? The infor lawson modernization business case is built around these six dimensions. Syntra ETL helps customers structure the analysis.

For a US hospital network running full-scope Lawson (Finance + Supply Management + HR + Payroll) with the typical 15–20 years of customisation accumulation: 12–18 months end-to-end (assessment + design + build + cutover + parallel-run). Phased migrations (Finance first, Supply Management second, HR third) typically run 12 months total with productline-level cutovers spaced 2–3 months apart. Big-bang migrations (all productlines cut over together) typically run 9–12 months but concentrate risk into a single cutover weekend. Higher-ed institutions often run 15–18 months because of academic calendar constraints (cutovers must align between semesters). Syntra ETL accelerates the data migration workstreams by 40–60% vs consultant-led baseline, allowing more of the timeline to be invested in change management and end-user readiness.

Change management is typically 20–35% of total programme effort and budget. End-user training: every Lawson user (finance, AP, AR, supply chain, HR, payroll, materials managers, AP approvers, hiring managers, payroll administrators) needs Fusion training tailored to their role. Communications: monthly programme updates, productline-specific go-live communications, post-cutover support communications. Process re-engineering: many Lawson processes are shaped by Lawson capability constraints; the modernization is an opportunity to redesign for Fusion native capability. Org change: roles change as IPA-developer and Mongoose-developer positions retire and Fusion configurator and OIC developer positions emerge. Sponsor engagement: CFO, CIO, HR Director, Supply Chain Director engaged throughout.

Phased is the norm and Syntra ETL strongly recommends it for hospital and higher-ed customers. Phase 1: Assessment + planning (2–3 months). Phase 2: Finance migration cutover (2–4 months). Phase 3: Supply Management migration cutover (2–4 months). Phase 4: HR migration cutover (2–4 months). Phase 5: Lawson decommissioning + long-term archival (1–2 months). Total programme: 12–18 months. Each phase has its own success criteria, its own cutover, its own go/no-go decision. Phased approach concentrates risk into discrete decision points rather than into one all-or-nothing cutover. Phased approach also allows organisational learning between phases — lessons from Finance cutover inform Supply Management planning.

Lawson decommissioning has two flavours. Full decommission: Lawson productlines moved to read-only, historical data migrated to Syntra cloud archive with full HIPAA + SOX + CMS evidence preservation, Lawson licenses cancelled, Lawson infrastructure (DB, application servers) shut down. Achieves maximum cost savings (Lawson licenses + infrastructure + skill costs eliminated). Hybrid decommission: Lawson productlines moved to read-only for historical query, kept running in minimum-cost mode (typically single-server DB instance, no active users), used for occasional audit queries until retention period expires. Lower cost savings but preserves direct query access to legacy data. Healthcare retention requirements (HIPAA 6 yr minimum, often 10 yr+ per state law) and higher-ed grant retention drive the decommissioning timing decision.