Purpose-built platform for infor lawson to oracle fusion migration. Lawson S3 database extractors, LSF customization scanner, multi-hospital COA harmonization, Joint Commission-aware HCM conversion and a SOX/HIPAA-grade reconciliation pack — without the 24-month consultant programme.
Most Lawson-to-Fusion projects don't slip on the database side. They slip on 25 years of LSF customization sprawl, multi-hospital COA harmonization, payroll YTD reconciliation and a 600-flow Process Flow backlog nobody documented.
Infor Lawson S3 has been the dominant healthcare and public-sector ERP since the 1990s. A typical US hospital carries 20–25 years of GL postings, 9,000+ Lawson tables in active use, hundreds of custom Process Flows accumulated by successive PMO teams, LSF Java customizations nobody fully owns, custom DME (Deductions of Member Earnings) calcs in payroll for union contracts, GPO contract hierarchies four levels deep, and an HRHISTORY audit log recording every HR transaction back to the original go-live. Consultant-led infor lawson to oracle fusion migration projects spend the first 6 months just cataloguing what's there.
Syntra ETL inverts the sequence. Pre-built Lawson S3 database extractors with read-only stored procedures cover all 9,000+ tables on day one. An automated LSF + Process Flow scanner produces the customization catalog in days, not months. The infor lawson to oracle fusion migration conversation that used to consume two quarters now happens in week three with hard evidence on the table.
Whether you're a stand-alone community hospital moving Lawson Financials and Supply Chain to Fusion, an IDN consolidating 8 hospitals across two Lawson instances onto a single Fusion tenant, an academic medical center bringing grants and research accounting alongside the clinical Cerner footprint, or a state/county government retiring Lawson Public Sector to Fusion, the same engine handles the workflow — with the same reconciliation rigor and the same Joint Commission and HIPAA audit evidence pack.
And how the Syntra ETL platform addresses each one — before they consume your timeline or your CFO's patience.
An IDN with 8 hospitals on two Lawson instances usually has two different chart-of-account designs. Syntra crawls every accounting-unit hierarchy, drives the harmonization workshop, and produces a single unified Fusion COA before any cutover load runs.
Hundreds of customizations accumulated over 20+ years. Process Flow scripts, LSF Java customizations, Lawson 4GL personalizations, custom report-writer extracts. The Syntra discovery engine inventories all of it and proposes retire-or-replace decisions per object.
PL/SQL, 4GL and LSF expertise is retiring faster than universities produce replacements. The Syntra platform compresses the dependency window so projects don't stall on a single SME's calendar.
Nurse staffing ratios, license tracking, competency records, mandatory training history — Joint Commission demands continuous evidence. Syntra preserves the full chain through the Lawson-to-Fusion HCM cutover with signed reconciliation.
GPO contracts (Premier, Vizient, HealthTrust) carry tiered pricing, admin fee splits and tier-up commitments. Syntra preserves the full tier history so contract performance and rebate claims continue uninterrupted on the Fusion side.
Every load and every read is signed and timestamped. The GL line → AP invoice → PO → requisition → receipt chain stays intact and queryable for SOX 7-year and state healthcare retention (often 10–30 years).
A repeatable, governed workflow built for Lawson's particular complexity. Typical full-scope timeline: 9–14 months end-to-end.
Lawson S3 metadata crawl, Process Flow + LSF inventory, Crystal/LRW/Birst report catalog, multi-instance accounting-unit inventory, security/user export. Output: complete object inventory, customization heat map, integration backlog, sized assessment with risk register.
Multi-hospital chart-of-account harmonization workshops, BU/ledger design, supplier and customer dedupe crosswalks, item master harmonization, HCM organization and position crosswalks. Reviewed and signed off by CFO, CHRO and CIO.
Lawson S3 read-only extractors pull all in-scope data (Financials, Supply Chain, HCM, MHC where deployed). Output staged as Parquet plus original document attachments, partitioned by company and fiscal year with hash-signed manifests.
Crosswalks applied, custom field collapse, FBDI/HDL payloads generated, attachments linked. Validated against Fusion 26x schemas with row-level error diagnostics surfaced locally — not in 4-hour ESS jobs that fail on row 487,000.
FBDI/HDL ZIPs submitted to Fusion ESS, monitored to completion, reconciled at row/sum/hash level. In parallel, OIC integrations built to replace Process Flow / LSF integrations. Critical Epic/Cerner/GHX interfaces validated under parallel-run.
2 month-end cycles (and 2 payroll cycles) in parallel, deltas captured and replayed, reconciled to the cent, sign-off pack issued. Lawson moves to read-only archive mode; Fusion takes over as system of record.
No more bespoke Lawson stored procedures or custom Process Flow listeners. Just configure scope, run, reconcile.
GLAMOUNTS, GLCONTROL, APINVOICE, APDISTRIB, APPAYMENT, ARCUSTOMER, ARINVOICE, AMASSET, AMDEPRSCHED and 200+ supporting tables. Full accounting-unit hierarchy preserved with RW audit columns intact.
POHEADER, POLINE, ITEMMAST, ITEMLOC, PARLOCN, ORPICKLIST, CTRHEADER (contracts), CTRTIER (GPO tiers) plus rebate and admin-fee tables. UNSPSC/NDC/HCPCS coding preserved.
HRHISTORY (the audit log of every HR change), EMPLOYEE, DEPTCODE, JOBCODE, POSITION, PAEMPLOYEE, PAYHIST, DEDHIST, BENHIST. Joint Commission license and competency tracking preserved end-to-end.
Where MHC is deployed, patient accounting tables extracted with full revenue cycle history — preserved for compliance reference and revenue reconciliation post-cutover.
LSF security model, Process Flow definitions, IPA flows, Lawson 4GL personalizations — exported via Lawson metadata catalogs for the AMX/OIC migration plan and customization-retirement decisions.
Crystal Reports catalog, Lawson Report Writer definitions, Birst metadata, custom SQL extract logs — feeds the OTBI/BI Publisher/OAC rebuild plan without manual screenshots.
A typical infor lawson to oracle fusion migration for a US hospital or health system on Lawson S3 (Financials, Supply Chain, HCM/Payroll) runs 9–14 months end-to-end with Syntra ETL, versus 18–30 months for consultant-led programmes. Single-pillar migrations (Financials only, or HCM/Payroll only) close in 5–8 months. The acceleration comes from pre-built Lawson S3 extractors that already understand the 9,000+ tables (GLAMOUNTS, APINVOICE, HRHISTORY, PAYHIST, MHC patient-accounting tables), an LSF customization scanner that catalogs Lawson Process Flow and 4GL personalizations automatically, governed crosswalks between Lawson accounting units and Fusion COA segments, and Joint Commission-aware HCM cutover. Multi-instance health systems (post-M&A consolidations of three or four Lawson tenants) add 6–10 weeks for COA harmonization that has to happen before any infor lawson to oracle fusion migration cutover.
Lawson S3 has been the backbone ERP for US hospitals and public-sector organizations for 25+ years and it still works — but four pressures drive an infor lawson to oracle fusion migration now: (1) Oracle's 2022 Cerner acquisition makes a unified Oracle Health + Oracle Fusion ERP stack the strategic platform for healthcare CIOs, with shared analytics, embedded AI agents and a single vendor for clinical-plus-financial; (2) Lawson skills are aging out — the PL/SQL, 4GL and LSF expertise that ran Lawson for two decades is retiring faster than colleges produce replacements; (3) Infor's investment focus has shifted to CloudSuite and M3, leaving Lawson S3 on slow-pace maintenance with limited modern UX, AI or mobile capability; (4) consolidated TCO of Lawson licensing, LSF, MHC, Crystal Reports, Birst BI and the supporting infrastructure routinely exceeds an equivalent Fusion subscription. Migration consolidates the stack and removes a 25-year-old skills dependency.
Syntra ETL supports the full Lawson S3 footprint that US health systems and public-sector customers actually run. Financials: GL with accounting-unit hierarchies, AP (invoices, payments, holds, 1099), AR (customer invoices, receipts, adjustments), Fixed Assets with healthcare-equipment depreciation methods, Cash Management, grant accounting, project accounting. Supply Chain: Procurement (requisitions, POs, receipts), Inventory (item master, par locations, OR/cath lab kits), Contracts (GPO contracts with tier pricing, admin-fee splits, rebate accruals), Strategic Sourcing. HCM/Payroll: Workforce Management (clinical scheduling, time, attendance), US multi-state Payroll, Benefits, Absence, Talent, Position Control, Joint Commission license/competency tracking. Plus MHC (Mortgage / Patient Accounting where deployed), Lawson Process Flow inventory, and LSF customizations. All extracted through Lawson S3 database APIs into Fusion-ready FBDI and HDL output.
Lawson S3 sits on SQL Server, Oracle or DB2 underneath. Direct database extraction is the only practical way to pull the full 25+ years of history at scale — Lawson's published interfaces (AGS, IPA, Process Flow) are designed for transactional integration, not bulk history extraction. Syntra ETL's Lawson S3 extractor ships read-only stored procedures and table-aware extract scripts for all 9,000+ Lawson tables across Financials, Supply Chain, HCM, MHC and the operational meta-tables. It honors Lawson's natural keys (Company + Accounting Unit + Account + Subaccount for financials; Company + Employee for HCM), preserves Lawson's distinctive RW (Record-Write) audit columns, handles SQL Server / Oracle / DB2 collation differences automatically, and streams to Parquet partitioned by company and fiscal year with hash-signed manifests. Extraction runs throttled against a read-only replica so live Lawson operations are untouched.
Yes — this is the most common shape of an infor lawson to oracle fusion migration. A health system with 8 hospitals on two Lawson instances (plus a couple of acquired sites on Oracle EBS or Meditech-side Lawson) consolidates onto a single Fusion instance with separate Business Units, ledgers per legal entity and a unified COA. Syntra ETL's discovery layer crawls every Lawson instance, inventories accounting units, departments, positions and item master entries, then drives a harmonization workshop with finance, supply chain and HR. The crosswalk engine handles the merge: duplicate vendor records dedupe by tax-id and address fuzzy match, overlapping cost-center codes get re-coded to the unified COA, item master conflicts resolved with single master designation and site cross-references preserved. Output: one clean Fusion tenant carrying the full enterprise history with full audit traceability back to source-instance for HIPAA and SOX evidence.
Lawson Process Flow (and earlier IPA) is Infor's workflow engine — it carries customer-specific approval routing, automated GL posting rules, supply requisition auto-approval logic, payroll exception handling and dozens of other custom flows accumulated over 20+ years. LSF (Lawson System Foundation) hosts the security model, the application framework and Java-based customizations. Syntra ETL's discovery engine inventories every active Process Flow, exports the flow definitions (XML), documents trigger conditions and downstream actions, and produces Fusion-equivalent recommendations: Approvals Management (AMX) for approval flows, OIC orchestrations for integration flows, BI Publisher bursts for automated reporting flows. LSF security models migrate to Oracle IDCS. Java customizations get a port-or-retire decision per object during the assessment. 30–50% of accumulated Process Flows are typically retired as redundant under Fusion's native engines.
No. Payroll is the highest-stakes domain in any health system migration — nurses and physicians depend on it bi-weekly, and a missed cycle is a regulatory and PR disaster. Syntra ETL's HCM migration playbook sequences payroll cutover at a quarter boundary (typically Q1 or Q3 to align with W-2 / W-4 cycles), runs a 2-cycle parallel where Lawson and Fusion both calculate gross-to-net for every employee, and reconciles to the cent before declaring Fusion the system of record. PAYHIST, DEDHIST, BENHIST and the full Lawson HRHISTORY audit log migrate to HDL Balance Adjustment with cent-level reconciliation. YTD balances, garnishments, tax elections, direct-deposit allocations and benefits deductions all carry over. The Lawson payroll engine stays warm in read-only mode for 90 days post-cutover so any corrective on-cycle adjustments can be reversed against the prior system.
Lawson health system customers typically run a thick layer of analytics: Crystal Reports for operational reports, Lawson Report Writer (LRW) for finance, Infor Birst for executive dashboards, and custom SQL extracts feeding Tableau or Power BI. None of those carry over to Fusion directly. Syntra ETL's discovery engine crawls Crystal repository, LRW report definitions, Birst metadata and SQL extracts in scheduled-run logs, classifies by business value (executive financial dashboards, supply chain stock-out alerts, OR utilization, nurse staffing variance, GPO rebate reports), and proposes Fusion equivalents: OTBI for ad-hoc analytics, BI Publisher for pixel-perfect operational reports (regulatory filings, GPO rebate claims, payroll registers), Oracle Analytics Cloud for executive dashboards. Typically 35–50% of legacy reports are duplicates or low-value and get retired during the rebuild — finance and supply chain leadership routinely report a better analytical experience post-migration.
Book a 30-minute discovery call. We'll walk through your Lawson instances, COA harmonization landscape, Process Flow + LSF customization backlog, payroll YTD reconciliation profile and Joint Commission documentation requirements — and give you a concrete timeline and budget before the call ends.