05 / Legacy systems

Modernize legacy software without losing its value

Long-established systems contain business knowledge. Understanding the existing software is often the right first step before considering replacement.

When this matters

  • Original developers have left
  • Documentation is incomplete
  • Important change requests must still be implemented
  • An application must run until a planned replacement

How I work

  • Reverse engineering and code reviews
  • Bug fixes and refactoring
  • Change requests and performance work
  • Stabilization and transition support

Technologies and practical experience

  • Taking over long-running Access/VBA applications with Oracle or SQL Server backends.
  • Reverse engineering, focused bug fixing, change requests and incremental modernization.
  • Maintaining related Delphi and C#/.NET components where needed until planned replacement.
Example: Mercedes-Benz environment

A business application developed over more than 25 years was maintained and enhanced until its planned cloud replacement.