There is a system in your company that everyone knows about, and nobody talks about. A claims engine no one opens anymore. A billing platform two people understand, both close to retirement. An ERP three vendors walked away from. Everyone knows it is a problem. Nobody wants their name on the fix.
So it runs. Quietly, on workarounds stacked on workarounds, each one older than the last. It does not send alerts. It just makes the business a little slower every quarter, and the people closest to it stop noticing.
Then something forces the issue. A vendor drops support. A security review flags it. The two people who understood it retire. Now the question is not whether to fix it. It is who will take it on, and whether anyone can.
Four firms do this work for a living. Here is how each one takes over a system nobody else would touch.
What Keeps These Systems Alive Past Their Expiry Date
The systems nobody wants to touch are rarely broken. They run payroll, process claims, move money. They work. That is exactly why they survive.
A legacy system is business critical by definition. If it were not, it would have been shut off years ago. The reason nobody touches it comes down to a simple calculation. The cost of replacing it looks worse than the cost of leaving it alone, quarter after quarter, until the question stops getting asked.
McKinsey found that nearly nine in ten executives have started a transformation project in the past two years. Most of them point to outdated systems as a reason. The problem is not that old systems exist. It is that no one will take ownership of fixing them.
1. Avenga
Avenga focuses on enterprise software modernization for manufacturers burdened by systems that have turned out to be a complicated knot. Legacy systems, IIoT devices, MES layers, and cloud solutions have all been integrated together, leaving no one with a complete understanding of the situation. Here comes Avenga to integrate all components without disrupting the process.
The cooperation will cover edge-to-cloud data foundations, which will allow for linking sensors, machines, and enterprise systems into one coherent system. This approach will include creating digital twins, which will allow for simulating machines and production lines even before touching the actual factory equipment.
This method will be perfect for those manufacturers where each change in the system means a huge risk.
How ownership gets handled here:
- The assessment team stays on through production, so context never leaves the room
- In-house cloud certifications keep migration and engineering inside the same engagement
- Flexible engagement models let clients choose how much of the work Avenga owns
2. Luxoft
Most modernization projects fail. Luxoft puts the number at 77% of organizations that have abandoned at least one legacy modernization program. Their success rate on mainframe work is 100%.
Here is where Luxoft separates itself. When the tools to move a legacy system do not exist, they build them. Compilers, code converters – whatever the job needs for technologies like z/OS COBOL, JCL, IMS, and CA Gen.
A Fortune 500 client found out how far that goes. Their mainframe application was holding up a data center move, and more than one attempt to modernize it had already collapsed. Luxoft picked it up, moved the operating system from zOS to RHEL, converted the JCL to Python automatically, wrote an IMSDB-to-SQL adapter, and tuned the GNU COBOL compiler until performance held.
That kind of engagement is what digital transformation consulting looks like when the patient is already on the table, and other surgeons have left.
How ownership gets handled here:
- Custom-built compilers and converters handle legacy technologies other vendors avoid
- In-house tools get developed when off-the-shelf approaches fail
- The team takes over migrations that have already broken down elsewhere
3. Itransition
Itransition runs a project rescue service for work that has hit a wall. The offering covers code audit, reengineering, development finalization, team augmentation, scope revision, and infrastructure reconfiguration. Emergency fixes can start within days when a release is blocked by code integrity, execution, performance, or security problems.
One example is the Evoz Baby Monitor. A Chinese development company had already failed to deliver a complete working system, leaving the project with intricate functionality and complex architecture that nobody could finish. Itransition took over the rescue, implemented the core functionality, and got the hardware device communicating with iPhone over the internet.
The finished product connected a mobile app, a back-end web service with audio pattern recognition, desktop configuration tools, and a payment-integrated website. That recovery shows what software delivery performance means when the starting point is a half-built mess.
This fits companies holding a system that no previous vendor could finish.
How ownership gets handled here:
- Rescue work starts with a code audit and reengineering assessment
- Emergency fixes can begin within days when a release is blocked
- The team takes over incomplete projects and finishes what others abandoned
4. TechMagic
TechMagic works with more than 200 customers from FinTech, Enterprise SaaS, and HealthTech industries. The company deals with projects of relatively small size compared to those that large consulting firms target, which guarantees that there will be no queue for your work. The CEO of the FinTech company talked with seven consulting firms before he chose TechMagic, because the decision was made based on the quality of processes and systems rather than pricing.
The company is seen by its clients as a group of critical thinkers that offers solutions that go beyond ticket processing. It is very important when the system is fragile, and the easiest way of fixing it can damage some other parts of it. Clients with experience working with companies whose members disappeared in the middle of the project appreciate that TechMagic is not too big and the people who initially scoped the work will do the entire process.
This fits enterprises with a difficult system that bigger firms would rather pass on.
How ownership gets handled here:
- Smaller footprint means the work gets attention instead of sitting in a queue
- Clients report proactive problem-solving rather than passive ticket execution
- The same people who scope the work stay involved through delivery
Why These Systems Get Abandoned in the First Place
Most complex systems are not abandoned simply because of their inherent complexity and infeasibility. Most of the time, they are abandoned because the owner will find owning them to be a money-losing venture for an average vendor. A fixed-scope contract will not work with a documentation-less codebase with untrackable dependencies.
That economics problem explains the pattern. The firms above take these systems on because their engagement model can survive the unknowns. Luxoft builds its own compilers when off-the-shelf tools do not exist. Itransition runs rescue work that starts with an audit before anyone commits to a price. Avenga keeps the assessment team on through production, so the scope can move without a new contract. TechMagic stays small enough that a messy project does not get buried under bigger accounts.
None of that is charity. It is a different commercial structure, built for work that cannot be scoped in advance.
FAQ: Questions That Come Up Before Someone Hands Over the Keys
Nobody calls a firm like these without a few things on their mind. The questions below are the ones that come up most often when a company is deciding whether to let an outside team take over a system nobody inside wants to own.
What happens in case of the system being so outdated that no person in the company’s technical support has ever seen anything similar?
This happens more often than one would imagine, and usually marks the distinction between the respectable companies and the others. Luxoft has been in such situations when they were faced with the migration of a mainframe application, which used some technologies unknown to most people nowadays. They developed the tooling themselves because nothing of the kind was available out-of-the-box. A company that knows how to deal with the modern stacks won’t even touch your problem. A company with the relevant experience will let you know in advance whether it’s worth doing.
In case something goes wrong in the process of migration and the production system stops working – who takes responsibility?
This is probably the question that ruins many agreements, but it should be. Ask what happens in case some change makes your system stop working during business time. Itransition offers rescue services in just this case, and their projects start with an audit preceding any estimate. This order is important. When a company estimates the cost of work without understanding the system – it’s guesswork, and you have to pay the price of that.
What about those people who created the original software?
Some of them stay around, but most of them leave eventually. The knowledge they had goes away too – this may very well be a reason for further abandonment of the system. Avenga provides its digital transformation consulting services with the assessment team staying around during the entire process up to the production stage, so no context dependence on particular people is there. For your organization, this may make all the difference in the world.
How do you scope a project when nobody knows what is inside the codebase?
You do not, at first. The honest answer is that scoping comes after the audit, not before. Sigma Software rebuilt missing documentation on an ERP project by working alongside the client’s own team rather than pretending the gap could be papered over. Any firm that promises a fixed scope on day one is either overcharging for the risk or planning to change the terms once they are inside.
What if the system cannot go offline during the takeover?
Manufacturing and financial platforms usually cannot. Avenga handles this in industrial settings by using digital twins to test changes virtually before anything touches the live equipment. The same logic applies elsewhere. Ask how they plan to work around uptime requirements, and listen for specifics. A firm that has not thought about this has not done this kind of work before.
How long does it actually take?
Longer than the first estimate and shorter than doing nothing. The range depends on how much documentation survived and how many dependencies nobody has mapped. The firms above tend to give honest ranges rather than a single number, because they have been burned by optimistic timelines before.
Bottom Line
As a complex system is left unattended, it becomes progressively harder to restore. The interdependencies increase. The experts leave. With each year that passes by without action, the eventual cost of restoration will grow higher.
The business model is what defines a company’s ability to survive chaos. Luxoft creates tools where there are none. Itransition performs audits before pricing. Avenga provides digital transformation consultancy with one team handling the project from analysis to delivery, thus making changes possible without breaking the contract. The people who define the problem stay around to solve it and are watched while doing so.
This kind of organization is vital for companies maintaining a platform that was abandoned by three other vendors.