Infor CloudSuite Healthcare Migration Assessment — Sized in Weeks, Not Quarters

An infor cloudsuite healthcare migration assessment is a structured pre-project discovery engagement that produces a sized, risk-ranked, evidence-backed migration plan for moving from Infor CloudSuite Healthcare (Lawson S3) to Oracle Fusion. The assessment inventories every customization in the Lawson environment (LSF custom code, Process Flow scripts, Crystal Reports, custom DME calcs), catalogs every HCM module in active use (Workforce Management, Payroll, Benefits, Absence, Talent, Position Control), maps every GPO contract relationship (Premier, Vizient, HealthTrust, regional GPOs), and produces a multi-instance topology map for IDNs. Output: timeline, budget, risk register and recommended cutover sequence with executive sponsor sign-off.

Because Infor CloudSuite Healthcare is a 30-year-old codebase wrapped in cloud framework, and what looks like a standard configuration on the surface usually carries 5–15 years of accumulated customization that nobody has fully documented since the original go-live. Without an infor cloudsuite healthcare migration assessment, the migration project commits to a fixed timeline and budget based on assumptions that get falsified in week 8 when the discovery team finds 287 undocumented Lawson Process Flow scripts driving critical operational workflows. The assessment catches all of that upfront, before the contract is signed, so the timeline and budget are realistic.

Eight discovery streams. (1) Lawson customization inventory — LSF custom code, custom tables, Process Flow scripts, Lawson Add-Ins, Crystal Reports, Birst dashboards, custom DME calcs. (2) HCM modules in use — which of Workforce Management/Payroll/Benefits/Absence/Talent/Position Control are active, with usage metrics per module. (3) GPO contract portfolio — Premier/Vizient/HealthTrust contracts, tier structures, rebate accrual schedules. (4) Multi-instance topology — for IDNs, every Infor tenant inventoried with COA, vendor master, employee master overlap analysis. (5) ION integration backlog — every BOD flow inventoried per partner system. (6) Birst + reporting landscape — every dashboard + report cataloged. (7) Infrastructure footprint — Infor Cloud tenants, ION runtime, OS Portal, supporting infrastructure. (8) Compliance retention obligations — SOX/HIPAA/state/Joint Commission/AKS/Stark applicable rules.

By crawling the LSF custom code repository, custom Lawson tables, Process Flow script library, custom report writer extracts and scheduled-job logs. Every customization is classified: business-critical (e.g., custom DME payroll calculation, must be reproduced in Fusion before cutover), supporting (e.g., custom AP report, can be retired or rebuilt in BI Publisher post-cutover), or candidate for retirement (low-usage, redundant with standard functionality). For business-critical customizations, the assessment produces a Fusion-equivalent design (Fast Formula for payroll calc, OIC for integration, BI Publisher for report). For supporting customizations, the assessment produces a backlog with prioritization. For retirement candidates, the assessment recommends decommissioning.

By treating it as a first-class concern from day one. The assessment crawls every Infor tenant in scope, inventories accounting-unit hierarchies (often three different COA designs across three acquired tenants), runs supplier dedupe analysis by tax-id and address fuzzy match, runs employee dedupe analysis by SSN where staff have moved between facilities, runs item master conflict analysis (same SKU on three tenants with three different prices and three different UNSPSC codings). Output: multi-tenant consolidation plan with harmonization workshops sequenced, conflict resolution authorities identified, and unified Fusion target structure designed before the migration project starts execution.

By cataloging every GPO contract relationship across Premier, Vizient, HealthTrust and regional GPOs, with full 4-level hierarchy preserved (corporate → group → tier → admin-fee split). For each contract, the assessment captures: contract effective dates, tier-up commitment volumes, admin fee splits, rebate accrual schedules, item-level pricing tier eligibility, and historical rebate claim performance. Output: a complete GPO contract portfolio that drives Fusion Procurement Contract configuration, ensures rebate accruals continue uninterrupted across cutover, and identifies any contract structures that need renegotiation with the GPO before Fusion go-live (rare but important to catch early).

A signed multi-artifact pack delivered to executive sponsors at the end of the assessment engagement. Components: (1) Customization inventory with business-criticality classification per object; (2) HCM module usage map with per-module conversion complexity; (3) GPO contract portfolio with rebate accrual continuity plan; (4) Multi-instance consolidation topology with harmonization plan; (5) ION integration backlog with OIC-equivalent design; (6) Reporting landscape with OTBI/BI Publisher rebuild plan; (7) Timeline, budget, risk register; (8) Recommended cutover sequence (full vs phased); (9) Executive summary with go/no-go recommendation. Counter-signed by CFO, CIO, CHRO, Chief Compliance Officer.

Standard timeline 4–8 weeks depending on Infor footprint complexity. Single-instance community hospital: 4 weeks. Multi-instance IDN with 3–5 Infor tenants: 6–8 weeks. Academic medical center with grants accounting + Process Manufacturing: 7–8 weeks. The assessment runs in two phases. Phase 1 (weeks 1–3): automated discovery using Syntra ETL crawlers against Lawson metadata, ION admin API, OS Portal API; produces objective inventory data. Phase 2 (weeks 3–8): structured workshops with finance, supply chain, HR, IT, compliance to interpret the inventory data, apply business judgment, and produce the signed deliverable. Phase 2 is what consultant-led assessments stretch to 6+ months; Syntra ETL keeps it to 5–6 weeks because Phase 1 is automated.