Infor Lawson Migration Cutover Strategy — Hospital + Higher-Ed Grade

An infor lawson migration cutover strategy is the orchestrated plan that moves your hospital, university or large public-sector organisation from running on Lawson S3 (Financials, Supply Chain Management, HR, Payroll) to running on Oracle Fusion — without losing a single AP invoice, payroll cycle, patient charge or PO receipt in the transition. It covers four interlocking dimensions: data cutover (final extract, transform, load, reconcile), integration cutover (IPA flows migrated to OIC, Smart Notifications replaced with Fusion Workflow, GHX/MMIS/ADP/Kronos endpoints repointed), business process cutover (period-end close timing, payroll cycle alignment, change-management readiness, Mongoose-replacement training), and rollback strategy (defined criteria, defined trigger, defined process — used 0 times in healthy projects but mandatory to define). Syntra ETL ships a hospital-grade and higher-ed-grade cutover playbook.

For a US hospital network running full-scope Lawson (Financials + SCM + HR + Payroll), the production cutover window is typically a long weekend: Friday 18:00 to Monday 06:00 — about 60 hours. For a higher-ed institution, often a long weekend timed between semesters when student employment payroll cycles are quiet. Within that window: Lawson moves to read-only at hour 0, final delta extract runs for 4–8 hours, full Fusion delta load + reconciliation runs for 18–24 hours, integration repointing runs in parallel for 12–18 hours, business process validation runs Sunday for 8–12 hours, go/no-go decision Monday 04:00, production users on Fusion at Monday 06:00. The infor lawson migration cutover strategy is sized to fit the institution's actual quiet window.

Hospitals can't stop. ED runs 24/7, OR schedules continue, inpatient billing accumulates. The cutover strategy explicitly avoids the 4 highest-risk windows: month-end close (typically last 5 days of month + first 3 days of next), end of fiscal year (extended close ~21 days), payroll cycle peaks (bi-weekly cycle days, semi-monthly cycle days), and major patient throughput events (Joint Commission survey, system-wide downtime planned for facility maintenance). Within the chosen window, supply chain receipts queue (GHX integration buffers), patient charges queue (Epic/Cerner/MEDITECH interface buffers), AP invoices queue (workflow inbox), payroll for the cycle is processed in Lawson before cutover, and Fusion takes over the next pay period. The strategy is hospital-DNA.

Higher ed has different quiet windows: between semesters (winter break late December - early January, summer break mid May - mid August), avoiding tuition billing cycles (start of term, financial aid disbursement windows), avoiding grant year-end (typically June 30 for federal grants, varies for state and private), and avoiding open-enrollment for staff benefits. Within the chosen window, student employment payroll is processed in Lawson before cutover, accounts payable is drained, sponsored research time-and-effort certifications are finalized, and Fusion takes over the next semester. Higher-ed-specific extensions (grants attribution, F&A indirect cost recovery, FFATA reporting) are validated to run correctly post-cutover before the go-live decision.

Five integration workstreams run in parallel within the cutover window. (1) IPA flows: existing Infor Process Automation flows that were re-platformed to OIC during the project are activated at cutover; Lawson IPA shuts down. (2) Smart Notifications: replaced by Fusion Workflow with the same subscriber list and routing rules; subscribers receive Fusion-sourced notifications from cutover forward. (3) GHX integration: supplier exchange repointed from Lawson Supply Chain to Fusion Procurement at the GHX gateway level. (4) Patient accounting interface: Lawson AR ↔ Epic/Cerner/MEDITECH replaced by Fusion AR ↔ same EHR with the same encounter-level interface contract. (5) Payroll integrations: ADP / Kronos / SilkRoad endpoints repointed from Lawson Payroll to Fusion HCM Payroll. Each integration has a tested rollback path.

Yes, and most healthcare and higher-ed organisations do — typically 4–8 weeks of parallel-run. During parallel-run, Lawson continues taking transactions (AP invoices, payroll, supply chain receipts, patient charges to AR) and Fusion processes the same transactions in parallel via delta extracts and replays. Per-period reconciliation per process level proves Fusion matches Lawson to the cent. CFO, HR Director, Supply Chain Director and Internal Audit review per-period sign-off packs. Once 1–2 full close cycles complete cleanly, the institution has hard evidence that Fusion is ready and the formal cutover is a low-risk event. Mongoose-replacement screens are validated by end-users during parallel-run, IPA-to-OIC flows are validated, GHX integration is validated.

Three rollback trigger categories with documented criteria. (1) Data variance: reconciliation pack shows trial balance variance > $50K per process level per period, AP aging variance > 5% per supplier, payroll gross variance > $1K per pay period — triggers rollback investigation, not automatic rollback. (2) System availability: Fusion ESS unavailable > 4 consecutive hours, Fusion HCM unavailable > 2 hours, OIC integrations failing > 10% of transactions for > 1 hour — triggers rollback assessment with Oracle support engagement. (3) Business process: end-user inability to perform critical workflows (AP invoice approval, payroll cycle processing, patient charge posting, PO receipt) for > 4 consecutive hours — triggers rollback decision. Rollback is technically possible up to 72 hours post-cutover (Lawson kept in read-only mode with delta capture enabled). In practice, rollback has been triggered 0 times in healthy projects.

Five gate criteria. (1) Data reconciliation: every reconciliation pack signed by CFO, HR Director, Supply Chain Director — variance threshold cleared. (2) Integration validation: every IPA-to-OIC flow tested in production-equivalent mode, every Smart Notification → Fusion Workflow tested, GHX/MMIS/ADP/Kronos/EHR repointing verified. (3) Business process readiness: end-user training completion > 95%, end-user dress-rehearsal pass rate > 90%, Mongoose-replacement screens accepted by user reps. (4) Operational readiness: Oracle support engaged, OIC monitoring active, ESS job queue clear, IT operations on standby. (5) Rollback readiness: Lawson read-only mode verified, delta capture active, rollback runbook reviewed. Go/no-go committee (CFO, CIO, HR Director, Internal Audit lead, project director) reviews all five gates and makes the call. No-go reverts to the next planned cutover window.