Our supplier no longer supports our software
Your supplier stopped supporting your software. Here’s how to take back control.
The supplier was acquired, changed focus, went out of business or simply ended the contract. Your organisation still depends on the software. We help you establish what you own, what it takes to keep it running, and whether to maintain it or replace it.
Before anything else
Four things decide whether a takeover is possible
Ownership and licensing
Does your contract give you the right to the source code and to have someone else maintain it? Some suppliers license the software without handing over the code.Access
Can you get the source code, the hosting accounts, the database and the deployment setup? Who is the account holder for each?Technical condition
Is the software built on supported, up-to-date technology, or on versions that no longer receive security updates?Documentation and knowledge
Is there documentation, and will the supplier cooperate on a handover? Neither is required, but both make it faster.
Controlled handover
How we plan the transition
Map the architecture
What the system consists of, where each part runs, and how data moves through it.Establish ownership and access
A list of every account, licence and credential, and who holds each one. Gaps are closed before the supplier relationship fully ends.Review third-party dependencies
Libraries, frameworks, APIs and paid services the software relies on, and which of them are outdated, unsupported or tied to the supplier.Assess operational risk
Backups, security updates, monitoring and the single points of failure that could stop the business.Agree the handover
A step-by-step plan for moving hosting, code and responsibility, with a fallback at each step.Move into support
Once the handover is complete, the software is maintained under a support plan with agreed response times.About software support
The decision
Stabilise, maintain or rebuild?
Stabilise
The software does its job but carries urgent risks: outdated versions, no backups, security gaps. We fix those first, then reassess.Maintain
The software is in reasonable shape. We take over day-to-day maintenance and incident handling under a support plan.Software supportRebuild
Keeping the old system alive costs more than replacing it, or the technology has no future. We scope a new build at a fixed price, migrating your data.App development
Where to start
The first step is an assessment
Software assessment
You already run software and want to know what state it is in.
A written report on risks, maintainability and what it would take to support it safely.
- Price
- Fixed fee, quoted after a short intake call
- Turnaround
- Agreed before we start
- You get
- Written report + walkthrough session
Our work
Moving a platform without stopping the business
Dutch legal claims platform · Legal ServicesClaim deadlines that chase themselves
Staff no longer track medical follow-ups by hand: reminders schedule, resend and cancel themselves
Read the case
ESOMAR · Market Research & InsightsA public site and an operations dashboard on one platform
A modern, content-rich public site that conveys ESOMAR's value, thought leadership, resources and events
Read the case
FAQ
Questions we often hear
Our supplier will not hand over the source code. What now?
Check your contract first; we can help you identify what to ask for. If the code cannot be obtained, a rebuild may be the only route, and the assessment can then focus on documenting what the current system does so nothing is lost.
Can we keep using the software while you take over?
That is the aim. The handover plan is designed so the software keeps running, with a fallback at each step.
Is rebuilding always more expensive?
Not always. If the software runs on technology that is no longer supported, years of patching can cost more than a new build. The assessment compares the options so you can decide.