Infor Lawson Cloud Archive — Retire Lawson, Keep the History

An infor lawson cloud archive is a cloud-hosted, immutable repository of your full Lawson S3 history — Financials (GL, AP, AR, Fixed Assets), Supply Chain (POs, item master, GPO contracts), HCM/Payroll (employees, paystubs, benefits, licenses), MHC patient accounting where deployed, and supporting documents (invoices, contracts, attachments) — purpose-built for SOX 7-year, HIPAA 6-year and state-specific healthcare retention (often 7–30 years) after the live Lawson system is retired. Unlike a database backup, the infor lawson cloud archive is queryable through a self-serve web UI and REST APIs, indexed for fast historical lookups by department, employee, supplier, fiscal period and account, and produces audit-ready evidence packs for SOX, HIPAA, state surveys and Joint Commission requests.

A read-only Lawson S3 tenant continues to cost full Lawson licensing, LSF subscriptions, MHC where applicable, Birst BI / Crystal Reports licensing, and the supporting SQL Server / Oracle / DB2 infrastructure — often $500K–$1.6M annually for a mid-sized health system. After Fusion go-live, no one logs in often enough to justify that. An infor lawson cloud archive replaces the entire stack with cloud object storage plus a thin query layer at typically 4–10% of the original Lawson TCO. Retention scales linearly with storage cost (essentially free at object-storage prices), the archive is HIPAA-compliant out of the box with full read-access logging, and the legacy Lawson licensing contract terminates at the next renewal cycle. The break-even on archive cost vs continued Lawson read-only mode is typically under 8 months.

Full data model. The infor lawson cloud archive contains every Lawson S3 table at row-level: GLAMOUNTS, APINVOICE, APDISTRIB, ARCUSTOMER, AMASSET, POHEADER, POLINE, ITEMMAST, CTRHEADER, CTRTIER, EMPLOYEE, HRHISTORY (the full audit log), PAYHIST, DEDHIST, BENHIST — plus all attachments and document binaries from Lawson's BLOB columns, file shares or external repositories. Summarization would defeat audit defensibility; if a CMS auditor asks for the original PO with delivery receipts from a charge audit four years ago, the archive returns the same data Lawson would have returned. The query layer indexes the underlying Parquet for sub-second lookups, but the data fidelity is full source-of-record.

Yes. The infor lawson cloud archive runs on AWS or Azure infrastructure under signed Business Associate Agreements, with HIPAA-aligned controls: encryption at rest (AES-256 with customer-managed keys), encryption in transit (TLS 1.3), row-level access controls aligned to LSF role inheritance, full read-access audit logging (who, what, when, why), and 7-year audit-log retention by default. The platform holds SOC 2 Type II attestation and aligns with HITRUST CSF controls. Customers in California (CCPA), Texas (TMRPA) and EU jurisdictions (GDPR) get geo-pinned storage so PHI never leaves the legally-required region.

Sub-second for typical operational queries (look up an AP invoice by vendor + invoice number, look up an employee's payroll history for a year, look up a PO with line items and receipts). Sub-five-seconds for analytical queries spanning multiple departments and several fiscal periods. The archive uses Apache Parquet in cloud object storage with partition pruning by company and fiscal year, plus columnar indexes on the high-cardinality lookup fields (employee_id, supplier_id, invoice_number, PO_number, accounting_unit). Compare with a Lawson Crystal Report that historically took 15–45 minutes to return the same data.

Yes — and this is one of the primary value drivers. Finance, accounts payable, supply chain, HR, payroll, internal audit, external audit, compliance and Joint Commission survey teams all get scoped self-serve access through the same web UI and REST APIs. Role-based access aligns to the original LSF role structure (preserved during migration), so an AP clerk sees AP-scope data, an HR business partner sees HR-scope data, an internal auditor sees full-system read-only data. No ticketing the IT team to spin up a Lawson environment for a one-off question. Typical health systems see 200–600 monthly archive users post-Fusion-cutover.

Configurable per data domain — the default for healthcare customers is SOX 7-year for financial records, HIPAA 6-year minimum (extended to state requirements: California 7yr post-discharge, Texas 10yr, New York 6yr after discharge for adults / 6yr after age of majority for minors, Maryland 5yr or until age 21 for minors), IRS 4–7yr depending on record type, Joint Commission expectations (varies by document type) and OIG/CMS compliance documentation per the relevant statute of limitations. Public-sector customers (state/county/municipal Lawson deployments) configure to state public-records statutes — often 7–25 years. The archive supports tiered storage: hot data in standard S3/Blob; warm data in IA tiers; cold data in Glacier/Archive tiers — which keeps the 30-year retention cost down to a few thousand dollars annually.

Standard timeline is 10–16 weeks for the full Lawson footprint: 2–3 weeks for connectivity, scope and discovery; 4–7 weeks for the full historical extract (Financials, Supply Chain, HCM); 2–3 weeks for the query layer setup, security configuration and role mapping; 1–2 weeks for user training and parallel-validation. Multi-instance health systems (post-M&A consolidation) add 3–6 weeks for the multi-source merge and cross-instance dedupe. The archive can be stood up either before or after Fusion go-live — many customers do it in parallel with the migration so day-one post-cutover the legacy data has a home and the legacy Lawson system can move straight to decommissioning.