Unit4 Legacy Data Access After Business World Retires

Unit4 legacy data access is the ability to read, query, and report against Unit4 data — Business World (Agresso), Unit4 ERPx, or Coda Financials — after the source system has been migrated, archived, or decommissioned. It matters because Unit4's value to finance leads, project accountants, faculty deans, auditors, regulators, and former employees doesn't end on cutover day. UK higher-education and public-sector retention typically runs 7+ years (FOI Act minimum), often 15+ years for student-finance and HESA-aligned records, and indefinite for some research-grant evidence (REF). Without a deliberate Unit4 legacy data access strategy, organisations either keep Agresso alive at £200K–£800K per year of SQL Server, .NET app tier, and Unit4 support contract, or they discover during an audit that no one remembers how to spin Business World back up — the Agresso admin retired in 2024 and the database backups have bit-rotted.

Through three interfaces sharing one underlying archive. SQL access: JDBC/ODBC endpoints exposing the archived Unit4 tables in their original schema — acrtransact, acrbatch, customer, supplier, project, wbs, employee, timesheet, expenseclaim, gltrans, apvoucher, ardocument — so any BI tool (Power BI, Tableau, Cognos, IBM Planning Analytics) connects without modification. REST access: programmatic queries for audit automation, faculty self-service portals, and integrations into successor systems. Direct Parquet access: warehouse engines (Snowflake external tables, BigQuery, Databricks, Synapse) query archive files directly for analytics. All three interfaces share the same security model, masking rules, and read-log — the choice depends on consumer preference, not on what the archive can serve. Most finance teams use the SQL interface with Excel via ODBC; faculty users tend to prefer the portal facade.

Yes. Unit4's flexible seven-series coding structure (Account, CostCentre, Department, Project, Activity, Funding source, and customer-defined codes) survives in the archive exactly as it lived in Business World — including the hierarchical relation rules from Agresso's reference tables (relacc, costcentre, project relations). Queries against acrtransact return the same coding-string context an Agresso user would see in the AIB browser. Customer-specific Flexi-Fields are preserved on supplier, customer, project, employee, and transactional records with their original names, data types, and validation rules. This matters enormously for higher-education customers whose Flexi-Fields encode faculty/school/department splits, research-grant identifiers, REF unit-of-assessment codes, or funding-council attribution — losing them at archive time would break every historical-reporting requirement.

Yes — and this is the most common Unit4 legacy data access use case after a Business World retirement. The Syntra archive ships with a curated set of pre-built saved queries covering the 90% of historical-lookup requests we see: trial balance per ledger per period, AP voucher detail by supplier, AR aging by customer, project actuals by WBS, project profitability by project manager, faculty cost-centre rollups, timesheet detail by employee per period, expense claims by project, funding-source attribution by grant. Finance leads run them from Excel via ODBC; project leads run them from the portal facade; faculty deans get a dashboard view in Power BI fed by the archive. None of them need to know the Agresso UI, AIB report builder, or Excelerator template syntax — the archive replaces the Unit4 skillset for read-only historical access.

Through an optional employee self-service portal facade authenticated against your IdP (SSO via SAML/OIDC). The portal returns the requested historical documents: payslips reconstructed from Unit4 payroll history (acrpayroll, payslip tables), UK P60s and P11Ds regenerated from year-end payroll snapshots, expense claims with attached receipts from expenseclaim/expenseline, timesheet history per project. For UK higher-education customers this is critical — former academic staff retain rights to historical payroll documentation for 6+ years under HMRC rules, and the cost of running Business World purely to serve these requests is prohibitive. Nordic public-sector customers have similar retention obligations under national tax law (Skatteverket in Sweden, Skatteetaten in Norway). The portal serves these requests in seconds at a fraction of the Business World operating cost.

Sub-second for indexed point queries — single voucher, single project, single employee, single supplier. 2–5 seconds for typical finance queries: GL detail for one period for one cost centre, AP detail for one supplier for one year, project actuals by WBS for one project. 10–30 seconds for multi-year cross-faculty or cross-project aggregations against the largest tables (full-history acrtransact scan, 20 years of project actuals). Archive data is stored in Parquet partitioned by fiscal year, period, business unit, and project; the query engine uses column pruning and partition pruning aggressively. For year-end audit and HESA-return seasons we pre-materialise commonly requested datasets — trial balance per period per ledger, faculty cost-centre rollups, REF cost-attribution snapshots, grant-by-grant project actuals — so they return instantly.

Yes. Access is role-based with mandatory audit logging. Every query is logged with user identity, timestamp, query text, rows returned, and data classification accessed — the audit log itself stored immutably and exported to the customer's SIEM. Sensitive fields (National Insurance numbers, bank account, salary detail, student identifiers, research-grant amounts where commercially sensitive) are masked by default with explicit role-based unmask and unmask-event logging. Data at rest is encrypted with KMS-managed keys (customer-managed keys available). Data in transit uses TLS 1.3. The archive supports UK FOI (read-log evidence and 7-year retention floor), GDPR (right-to-erasure via record-level redaction with audit trail), HESA-aligned higher-ed retention, NAO public-sector audit requirements, and Nordic public-sector retention regimes. Compliance documentation is shipped per deployment, not as a generic add-on.

Indefinitely, and very little. The archive is built on cloud object storage with no inherent time limit. Customers configure retention per data domain: typical UK higher-ed finance retention 7–15 years (often extended to 20 for HESA continuity), research-grant evidence often indefinite per REF/UKRI policy, payroll retention per HMRC 6-year rules, project history per services-firm contract obligations (often 7+ years per client). Storage cost is the main constraint, and after Parquet compression typical Unit4 archives land at 60–250 GB even for 20-year datasets — costing $15–$60 per month in cloud object storage, $200–$700 per year. Total annual cost of Unit4 legacy data access for a mid-size Business World instance: $5K–$15K. Compared to the £200K–£800K annual cost of keeping Agresso alive, the archive is essentially free over a 10-year retention window.