Retire Unit4 Business World, ERPx, or Coda Financials cleanly after Oracle Fusion go-live. Full data archive, customization catalog, security snapshot, parity validation. UK FOI/HESA/HMRC compliance preserved. £300K–£900K/year TCO unlocked.
Customers spend 12–18 months getting Oracle Fusion live, then leave Unit4 Business World running 'for compliance' for years — bleeding £400K–£1M/year in unnecessary cost.
Most Unit4 to Oracle Fusion migration projects stop at Fusion go-live. Open transactions migrated. Current-period balances loaded. Two close cycles in parallel. Auditor signed off. Project team disbands. And then Unit4 Business World keeps running — 'just for compliance', 'just for audit', 'just for the FOI requests that come once a year'. Three years later, the legacy Unit4 instance is still consuming SQL Server Enterprise licensing, Unit4 support contracts, infrastructure costs, and Agresso-skilled administrator time. The 'just in case' line item has compounded into £1M–£2M of avoidable spend.
Unit4 decommissioning is the structured, low-risk way out. Syntra ETL extracts the complete Unit4 dataset to a cloud archive — every acrtransact row, every acrpayroll record, every project, every customer, every supplier, every Flexi-Field — and stands up a SQL/REST query interface that auditors, FOI officers, and HESA-return preparers find more responsive than the original Unit4 database. Customizations are catalogued as audit artifacts. Security state is snapshotted. Parity is validated. Then — and only then — Unit4 infrastructure retires and license fees terminate.
The result: full UK FOI, HMRC, HESA, NAO, GDPR retention compliance preserved through the entire 7–25 year retention window, at 70–90% lower TCO than keeping Unit4 alive. Internal audit signs off; finance reclaims the line item; the security and skills risk associated with a legacy Unit4 estate disappears.
What customers pay every year a legacy Unit4 instance stays alive 'for compliance' — when archival would satisfy the same requirement at a fraction of the cost.
18–22% of original license fee for Business World — £60K–£300K/year for mid-to-large customers. ERPx subscription continues at full rate. Coda Financials support fees continue.
Business World runs on SQL Server Enterprise Edition with Software Assurance — £30K–£150K/year. CALs continue scaling with users even in read-only mode.
App tier, DB tier, web tier, reporting tier, dev/test environments — typically £80K–£400K/year. Backup/DR/HA infrastructure continues regardless of low utilization.
Even 'lights-on' Unit4 instance needs part-time SQL DBA, Agresso admin, security admin — £180K–£450K/year fully loaded. Agresso talent pool shrinks; salaries rise.
Unit4 service packs and SQL Server cumulative updates still need to be applied — typically 3–6 person-weeks/year. Without patches, security and support compliance lapse.
Attack surface grows as Unit4 patches lag. Skill risk grows as Agresso practitioners retire. Vendor risk grows as Unit4's roadmap moves to ERPx-only. Decommissioning removes all three.
A repeatable, governed Unit4 decommissioning workflow that preserves compliance without preserving cost.
Inventory Unit4 modules in use (Business World, ERPx, or Coda), classify data domains (Financials, HCM, Payroll, Projects, T&E), map each domain to applicable retention regime (UK FOI, HMRC, HESA, NAO, GDPR, HIPAA). Output: signed per-domain retention policy and decommissioning gate criteria.
Pre-built Unit4 extractors pull every in-scope acr* and other Agresso/ERPx table — full history, every period, every business unit, every project. Output to cloud Parquet archive, partitioned by fiscal year, period, BU, project, hash-signed at row level.
Discovery engine catalogs Flexi-Field definitions, AIB report definitions, Excelerator templates, Browser Flow rules, BIP report templates. Security snapshot captures role, permission, dataset-security state at decommission date as immutable audit artifact.
SQL (JDBC/ODBC) and REST endpoints provisioned. Role-based access configured (auditor, FOI officer, HR auditor, BI user). Pre-built UK regulatory templates loaded. Year-end and FOI-window auditor datasets pre-materialized for instant access.
Sample auditor queries run against archive vs live Unit4 — trial balance, AP aging, project actuals, payroll register reconciled to the cent. Sign-off pack issued to compliance, finance, HR, FOI officer, internal audit. Archive becomes system of record for retention.
Integration points confirmed disconnected (zero active traffic in/out of Unit4 for 30+ days). Unit4 application stops, SQL Server databases backed up and retired, hosting contracts cancelled, Unit4 support terminated, dev/test environments shut down, internal staff redeployed.
What auditors, FOI officers, and HESA-return preparers actually do with the archive, day to day, after Unit4 decommissioning.
Internal audit runs trial balance, AP aging, project actuals queries against the archive each quarter — sub-second response, drill from summary to acrtransact row. Same workflow as live Unit4 ever was.
Year-end auditor extracts (P60/P11D, year-end TB, asset register, payroll register) pre-materialized for instant access. UK external auditor signs off in less time than they did against live Unit4.
FOI officer logs in with FOI-officer role, runs pre-built FOI-response template for the requested period and topic, exports the result with signed evidence. Days, not weeks.
Higher-ed customers run HESA finance-return extract, REF cost-capture extract, OfS data-template export from the archive each year. Pre-built templates use original coding-structure context.
When legal needs to reconstruct a historical contract, project, or supplier relationship, the archive surfaces the complete record — every transaction, every Flexi-Field, every change in effective-dated history.
Finance uses Power BI / Tableau against the archive for multi-year trend analysis — supplier-spend trajectories, customer-revenue trajectories, project-margin evolution — alongside Fusion current-period data.
Unit4 decommissioning is the orderly retirement of a legacy Unit4 system (Business World/Agresso, ERPx, or Coda Financials) after operations have moved to a new platform — typically Oracle Fusion, sometimes SAP S/4HANA or Dynamics 365. Customers plan Unit4 decommissioning 6–12 months after Fusion go-live, once two full close cycles have run in parallel, audit has signed off on the new system, and any latent data-quality issues have surfaced. Decommissioning is not 'turn the server off' — it's a structured process: archive the complete dataset, capture customizations and reports, snapshot security, validate parity with the live system, transition compliance retention to the archive, retire infrastructure, and terminate vendor licenses. Done correctly, Unit4 decommissioning unlocks £300K–£900K/year in TCO and removes a meaningful audit and security surface.
Running Unit4 as 'read-only for compliance' looks cheap on paper but compounds quickly. SQL Server Enterprise Edition licensing continues. Unit4 support fees continue (typically 18–22% of original license annually). Infrastructure costs continue. Periodic patching and SQL Server cumulative update work continues. Skilled Agresso administrators are still required — and as the Agresso talent pool shrinks, those skills cost more each year. After 3 years, a 'read-only for compliance' approach typically costs 60–75% of what live Unit4 operations cost — for an instance that's queried once a quarter. Unit4 decommissioning to a Syntra cloud archive costs a fraction (pennies per GB-month) and still satisfies the underlying compliance retention need. The economic case is decisive.
Six stages over 8–12 weeks typical. (1) Scope and retention design — inventory Unit4 modules, classify data domains, map to retention regimes (UK FOI, HMRC, HESA, NAO, GDPR, HIPAA). (2) Full data extract and stage — every acr* table to cloud Parquet archive, hash-signed, partition-manifested. (3) Customization and report catalog — every Flexi-Field, AIB report, Excelerator template, Browser Flow inventoried with source and business purpose. (4) Security snapshot — role, permission, dataset-security state captured as audit artifact. (5) Archive parity validation — auditor queries run against archive vs live, matched to the cent. (6) Infrastructure retirement and license termination — Unit4 servers shut down, hosting contracts cancelled, Unit4 support terminated, internal staff redeployed.
Through the Syntra ETL cloud archive's SQL/REST query interface. The archive preserves the original Unit4 schema — column names, datatypes, coding-structure context, Flexi-Field definitions — so auditors run familiar queries against acrtransact, acrpayroll, project, customer, supplier. Pre-built audit and FOI templates cover the standard requests: trial balance by period, AP voucher detail, AR invoice history, project actuals by WBS, payroll register, FOI-response query bundles. UK higher-education customers get HESA finance-return, REF cost-capture, OfS data-template extracts. Public-sector customers get NAO audit packs. Sub-second response for typical drill-down queries, 5–30 seconds for multi-year aggregations. Every query logged for evidence.
Customizations are preserved as catalog artifacts in the archive — not as functional code, but as evidence of what the live Unit4 system did. Syntra ETL's discovery engine inventories every Flexi-Field definition (with validation rules), every Agresso Information Browser report definition, every Excelerator template, every Browser Flow workflow rule, and any BIP-style report templates. Each artifact is retained alongside the data with the same retention policy. The catalog answers two questions a future auditor or successor IT team will ask: 'what custom logic did our Unit4 Business World system actually run?' and 'what reports were used to sign off historical periods?' The answer is in the catalog, indexed and searchable.
No. Syntra ETL's extractors run as a read-only SQL Server user (db_datareader plus SELECT on Unit4 schemas) — no Unit4 application changes, no AIB modifications, no Excelerator template edits, no Browser Flow updates, no vendor-supplied tooling. The Unit4 decommissioning workflow uses only SQL access to the underlying SQL Server database. This is important because some Unit4 customers' relationship with Unit4 has soured by the time decommissioning is on the table (often the trigger for migration in the first place). The vendor-independent path means decommissioning can proceed even if Unit4 support is unresponsive, expensive, or being actively terminated.
8–12 weeks for a typical Unit4 Business World or ERPx instance with 10–20 years of history. Longer for very large customers (UK universities or county councils with 25+ years of Agresso data, multi-entity public-sector groups, large professional-services firms with 100,000+ active projects). The critical path is full data extraction (typically 2–4 weeks parallelised across acrtransact, acrpayroll, project history) and parity validation (typically 2 weeks of sampled auditor queries against archive vs live Unit4). Customization inventory and security snapshot run in parallel and rarely drive the critical path. Infrastructure retirement and license termination are the final 1–2 weeks once the archive is signed off.
Integration points (bank feeds, expense-management tools, payroll bureau integrations, student-system integrations, government-reporting submissions) need to be rewired before Unit4 decommissioning. If migration is to Oracle Fusion, the rewire typically happens during Fusion go-live — integrations point to Fusion via OIC, REST, or file feeds. By the time decommissioning runs, integrations have already been disconnected from Unit4 for 6–12 months. The decommissioning checklist confirms zero active integration traffic into or out of Unit4 before shutdown. Edge-case batch jobs (annual government submissions, year-end finance returns) that were missed during cutover need to either run from Fusion or be re-implemented against the Syntra archive.
30-minute discovery call. We'll walk through your Unit4 instance, UK/Nordic compliance obligations, current cost baseline, and post-Fusion-go-live timeline — and quantify the TCO unlock you'd see in year one of decommissioning.