Who can still touch this system now that the people who built it are gone?
If the vendor who built the system has left, or the one developer who understood it has resigned, you will be the one asked at the next outage, even though you did not build it. First we audit the system in a fixed-price Handover Audit and recommend, with numbers, whether to keep, stabilise, modernise or replace it. If you decide to hand it over, we take it on, stabilise it and run it with a committed response time.
Handover audit · handover and stabilisation · operations for a monthly fee · ISO 27001, ISO 9001 and ISO 14001
“When it goes down, I’m the one held to account, even though I didn’t build it.”
Head of IT, mid-sized company
“If the next audit finding is about this, I’m the one they will ask.”
CIO, large enterprise
“Whether it works should not depend on someone who has already left.”
Head of IT, mid-sized company
“Let’s not swap one vendor dependency for another.”
CIO, large enterprise
“We don’t know what gaps there are in a system nobody understands.”
CIO, large enterprise
“I should be able to tell them, with numbers, how long it will hold out.”
Head of IT, mid-sized company
Our expert will tell you whether it fits your situation.
Over 2-4 weeks we map the dependencies, integrations, database objects, outdated components and security gaps with AI-assisted code analysis, and we interview the key people.
The report gives you a system map, a risk list and a handover plan, plus a decision proposal backed by numbers: keep, stabilise, modernise or replace. You can use the report with another vendor as well.
If you decide to hand the system over, the knowledge transfer starts with a parallel period. After that we introduce ticket handling and monitoring, and fix the most urgent defects. This takes 4-8 weeks.
We set the committed response time and the boundary between the application and the infrastructure in an agreement, and we then keep the system running as part of our Operations and Support service.
When management or the auditor asks, you can answer with numbers how long the system can be kept running, and when it goes down, yours is not the only phone that rings.
Who it is for: Heads of IT and CIOs whose system was built by another vendor or a former in-house team and has since been left without an owner. If a half-finished development needs completing, Custom Development and UX/UI is the right fit. If the system was built by us and needs operating, Operations and Support is the right fit.
Legally accessible source code, access to the environments and the database, a named contact and key user, and, if possible, the previous vendor’s cooperation.
The Handover Audit takes 2-4 weeks. We give you a fixed price up front, based on the size of the system. Handover and stabilisation take 4-8 weeks, and we give you a fixed price for them after the audit. The monthly fee for operations depends on the committed response time and the number of hours included.
More than 25 years of Oracle experience and long-term work with large organisations (NAV, MBH, MVM, MÁV, SZKHT). We also use AI-assisted code analysis on our own codebase: we processed around 1,100 source files of our JBStrap framework this way. Omnit works with ISO 27001, ISO 9001 and ISO 14001 certification.
We do not take over a system without the rights to its source code. We do not keep a system alive that cannot be saved: if the audit shows this, we recommend replacing it. We do not run data centres or helpdesks; the handover covers the application and the database. If the previous vendor does not cooperate, the handover is slower and more expensive, because not even the audit can fully recover knowledge that has walked out of the door.
What we did not cover on this page: the steps from a small first step to the complete solution, why it pays to go this way, and how we work along the way. Feel free to forward it to your colleagues.
It takes 2-4 weeks, and we give you a fixed price up front, based on the size of the system. At the end you get a system map, a risk list, a handover plan and a decision proposal, in a report you can also use with another vendor.
Or call: +36 30 235 0100
There is no handover without the rights to the source code. This has to be clarified before the audit, and it is worth involving your legal team.
Then we tell you so and recommend replacing it, because we do not keep a system alive that cannot be saved. You can use the report with another vendor, so you have a basis for the replacement even if we are not the ones doing it.
We set the committed response time in an agreement signed after stabilisation, and the same agreement defines where the boundary lies between the application and the infrastructure.
We give you a fixed price for the Handover Audit up front, based on the size of the system. We price the handover and stabilisation after the audit, and the monthly fee depends on the committed response time and the number of hours included.
After the handover, this is the framework in which we run the system, with a committed response time.
If the audit recommends modernising or replacing the system, or a half-finished development needs completing.
If the system runs on Oracle or another database: tuning, version upgrades and operations.
What does quickly assembled code cost later, and what happens when nobody understands the system any more?
Browse the blog, or subscribe to the Signal over Hype newsletter.
Describe the situation in a sentence or two, and an expert in the field will get in touch with you.
Or call: +36 30 235 0100
