Unit4 Data Archival Built for UK & Nordic Compliance

Unit4 data archival is the process of moving closed-period transactional data, terminated employee records, completed projects, and historical payroll detail out of the operational Unit4 database (SQL Server for Business World/Agresso, cloud-tenant for ERPx) into a queryable long-term archive. Organizations archive Unit4 data for three reasons. Compliance retention — UK FOI 7-year minimum, HMRC 6-year (UK), HESA-aligned indefinite for higher-education student finance, NAO audit packs for public sector, GDPR-compliant retention for HCM. Database-size control — acrtransact and acrpayroll grow at 100M–300M rows per year in mid-size customers. Migration prep — a smaller production footprint is faster, cheaper, and less risky to migrate to Fusion. Syntra ETL's Unit4 data archival routes cold data to cloud object storage as Parquet and exposes a SQL/REST query interface so auditors and regulators can still read it on demand.

Retention varies by data domain and jurisdiction. UK organizations: HMRC requires 6 years for VAT/PAYE/Corporation Tax records, FOI public bodies typically 7 years minimum (often 10–25 years for permanent records), HESA returns and student finance kept under institutional FOI policy (often indefinite). Nordic public sector: 10-year minimum is common, with national archive transfer requirements for permanent records. Continental EU: GDPR drives an upper bound on personal data retention (HCM); statutory accounting retention runs 6–10 years depending on country. US healthcare customers under HIPAA: 6 years minimum for HCM data. Higher-ed Campus Solutions-equivalent: indefinite for student records is the norm. Syntra ETL's archival policies are configurable per domain so each data class meets its specific retention rule.

Yes. The Unit4 data archival path preserves the source table schema — column names, datatypes, the relation rules between coding-structure values, Flexi-Field definitions — in the archive. Archived data lives as Parquet with embedded schema, plus a JSON Schema sidecar for tooling. The archive query interface lets auditors run familiar SELECT statements against acrbatch, acrtransact, acrpayroll, customer, supplier, project, employee and so on, returning results that match what they would have seen in the live Unit4 database — including effective-dated history, full coding-structure context, Flexi-Field values, and WBS hierarchy. No translation, no schema flattening, no data shape changes that would invalidate auditor familiarity.

Customizations are preserved as inventory artifacts. Syntra ETL's discovery engine catalogs every Agresso Information Browser (AIB) report definition, every Excelerator template, every Browser Flow rule, and every Flexi-Field definition in the source Unit4 system. The catalog includes source/definition, version history, last-modified date, and where derivable the business purpose. This serves two needs: post-decommission audit evidence ('what did our Unit4 Business World system actually do?') and migration support ('what custom logic did we need to re-implement in Fusion?'). The customization catalog is signed, timestamped, and retained per the same retention rules as the data itself.

Yes, for organizations that have completed migration to Fusion and no longer need operational Unit4. The Syntra archive holds the complete data, the customization catalog (Flexi-Fields, AIB, Excelerator, Browser Flows), the security model snapshot, and the reporting library — everything an auditor would otherwise demand a live Unit4 instance for. Customers save 70–90% on Unit4 licensing or hosting, SQL Server support, infrastructure, and Unit4-skilled maintenance staff. The archive query interface satisfies UK FOI, HMRC, HESA-aligned, NAO, GDPR, and HIPAA access requirements for the full retention window, with sub-second query response and signed, timestamped evidence packs.

Access is role-based with mandatory audit logging. Every query against the archive is logged with user, timestamp, query text, rows returned, and data classification accessed. Archive data is encrypted at rest with KMS-managed keys and in transit with TLS 1.3. Sensitive HCM and payroll data (NI number, bank account, salary detail) is masked by default and requires explicit role permission to unmask. UK higher-education customers using the archive for HESA-aligned and student-finance records get separate role partitioning so registrar-level access doesn't bleed into general finance access. Public-sector customers get an FOI-officer role that surfaces full read access for legitimate FOI requests while preserving day-to-day masking.

Yes. The Syntra archive exposes a standard SQL interface (JDBC/ODBC), so any BI or audit tool that connects to a relational database — Power BI, Tableau, Qlik, Alteryx, ACL, IDEA, even Excel — works without modification. There's a REST API for programmatic access, and the underlying Parquet files can be queried directly from Athena, BigQuery, Snowflake, or Spark if your audit team prefers warehouse-native access. Standard Unit4 auditor extracts (GL detail by period, AP voucher detail with supplier, payroll register, project actuals by WBS, timesheet history per employee) ship as pre-built saved queries that auditors can run on first login.

Sub-second for typical auditor queries — a single GL period for a single ledger, an AP voucher lookup, a supplier history for a single vendor, a project actuals query for one project ID. Multi-period or multi-year aggregation queries against billion-row acrtransact history typically return in 5–30 seconds depending on partitioning. Archive data is stored in Parquet partitioned by fiscal year, period, business unit, ledger, and project where relevant; the query engine uses column pruning and partition pruning to minimize scan. For UK year-end audits and HESA-return windows, customers commonly pre-materialize an auditor-facing dataset (trial balance, AP aging, project actuals, payroll register snapshots) for instant access.