Powered by DataMove + DataVault + DataLens
Retire costly enterprise applications while retaining secure, searchable access to historical records.
Legacy Exit is a defined engagement, not a licence. It runs in four stages and ends with a specific, checkable outcome: the legacy application is switched off, and the records it held remain available to the people who need them.
Stage 1
Establishes what is actually there, which is almost never what the application inventory says. Discovery is a fixed-price engagement in its own right and produces the scope everything after it is priced against.
The applications, environments and non-production copies genuinely in the retirement estate, including the ones nobody has costed.
What holds real business data, including custom tables, flexfields and bespoke modules that no standard extract touches.
Attachment and scanned-document volumes, and where they are physically stored — usually the deciding constraint.
Interfaces, downstream reporting databases and warehouses that must be retired or repointed at the same time.
The reports and enquiries people actually run, as distinct from the catalogue nobody has opened in years.
The retention periods, legal holds and statutory obligations that apply to each class of record.
Who genuinely needs historical access, for what, and how often — which sets the access model.
Licence, hosting, infrastructure, backup, security and support cost, and the renewal date the business case runs to.
Deliverable
An inventory, a target archive architecture, a roadmap and an implementation estimate.
Stage 2
DataMove extracts the history and DataVault holds it, with the structure that makes it answerable rather than merely stored.
Transactions, balances, master data and the reference data historical records resolve against.
Scanned invoices, contracts and correspondence, archived against the record they belong to.
Change and approval history, without which an archived transaction loses its evidential value.
Content held in the application's own document store, or in an external content server it depends on.
Retention period, legal-hold status, source system, extraction lineage and load evidence, attached to every record.
An invoice with its supplier, purchase order, approvals and attachments — context, not isolated tables.
Stage 3
Reconciliation is what converts a retirement from a judgement call into a documented decision. Source counts, transformed counts, rejections and archived counts are taken on every cycle, with control totals where the data supports them, and every discrepancy is categorised rather than explained away.
Illustrative figures shown to explain how reconciliation evidence is presented. They are not drawn from a specific customer engagement.
Stage 4
DataLens gives the historical users what the legacy application was being kept alive to provide. Once that access is proven in use, decommissioning runs as a staged plan rather than as a switch-off date.
Legacy Exit work is delivered as fixed-scope packages rather than open-ended consultancy. Scope, data volumes and retention requirements are established in a Legacy Exit Discovery, and the implementation is then quoted against that scope. Projects typically start from £25K.
Start here
A short, fixed-price engagement that produces the evidence a business case needs before any implementation is committed.
Single system
A single system of modest volume with limited attachments and a standard archive and access model.
Complex estates
Complex ERP or HCM estates where attachments, record relationships and controlled access carry as much weight as the row counts.
Public sector
Adds the information-governance support that NHS bodies, councils and universities need to evidence a retirement decision.
Programme scale
For large multi-object ERP and HCM migration programmes running repeated cycles across many data objects and workstreams.
Commercial model
Public-sector buyers can contract through G-Cloud 15. Commercial buyers contract directly.
Indicative packaging only. Prices are confirmed against agreed scope following a Legacy Exit Discovery.
Published SyntraETL engagements on the same architecture. Every figure below comes from the referenced case study rather than from a marketing claim.
A multi-hospital health system archived 18 data areas of timekeeping history into DataVault with reconciliation evidence, then ran a ten-stage decommissioning.
Read the case study →Historical records retained in a searchable archive so the source environment could be reduced.
Read the case study →A government body migrated Oracle EBS financials to Oracle Fusion with a controlled, repeatable and reconciled migration process.
Read the case study →The assessment produces a Legacy Exit Scorecard: what is in the estate, what must be retained, what it costs today, the complexity of retiring it and the recommended architecture.