Unsupported software.
The application, its database or its server no longer receives security updates.
Keep what works. Rebuild what’s underneath.
Keep the workflows people rely on while addressing unsupported software, ageing servers and fragile integrations. We assess the application, agree what must be preserved and plan the move to a supported stack in Azure or AWS.
Since the 1990s Experience across generations of applications and infrastructure.
Talk to an engineer Start with a scoped reviewReplace an unsupported membership database while preserving agreed record history, renewal rules and links to other systems. Reconcile the data and rehearse cut-over before staff move across. Explore this sector.
An application can remain useful long after its platform becomes difficult to support. These are common reasons to review the options.
The application, its database or its server no longer receives security updates.
The application depends on an ageing server that is difficult to maintain or replace.
The supplier has gone, the product is discontinued or continued support is no longer practical.
Essential knowledge sits with one person or is no longer available.
It cannot connect to Microsoft 365, other systems or AI, so people rekey data by hand.
Unsupported components or outdated controls leave gaps that need assessment and an agreed remediation plan.
Engineer-led and AI-assisted. AI helps with reading, testing and mapping. Engineers review the proposed changes against agreed behaviour and acceptance tests.
AI-assisted analysis of the code, database and screens to identify business rules that have not been documented.
Tests that capture the agreed workflows and important edge cases, so the new version can be held to them.
A supported stack with the workflows and screens agreed for preservation.
Data migrated into Azure or AWS against agreed reconciliation rules.
Agree security, backup and monitoring before go-live.
Add useful AI capabilities as the system evolves.
Agree who will operate the modernised system and what a future handover would require.
Hosted in Azure or AWS, in UK regions, and run by Toltec under a service agreement: monitored, patched and backed up.
Handed over in your own cloud tenancy, with the code, documentation, tests and runbooks your team needs to run it.
Our experience across generations of systems helps us understand their dependencies and the business rules that have accumulated around them. Explore our sector experience.
Departmental systems that outgrew the desktop.
Line-of-business software built years ago, still doing its job.
Customer systems the organisation depends on but the vendor no longer develops.
Databases on versions past the end of support.
Assess the available data and workflows, then agree what can be rebuilt as a system you own.
Critical workbook processes rebuilt as an application with defined rules, access and records of changes.
Start with a conversation about the application. We then agree a fixed-scope review of its behaviour, data and risks, with a practical plan you can use to decide what happens next.
Its modules, integrations and the business rules the code actually enforces.
Support status, security exposure, single points of knowledge and recoverability.
A target architecture in Azure or AWS, a staged plan and the behaviour tests needed to assess it.
We agree which workflows and screens to preserve, and record any necessary changes before implementation. Acceptance tests check the agreed behaviour.
We assess whether the system can be rebuilt from observable behaviour and accessible data. Agreed behaviour tests define what the replacement must preserve and where evidence is incomplete.
In UK regions of Azure or AWS, in your own cloud tenancy or ours, as you choose.
You always own your data. Ownership of the code is agreed at the start, and the handover option includes all of it.
Call 0345 257 4447 or send an outline. The first conversation is with an engineer. If an assessment would help, we agree its scope before starting.