Legacy software maintenance and migration

If your company depends on an old application nobody dares to touch, you are not alone. We recover the business logic, stabilise the system and migrate it to a modern stack without stopping your operations, even if the original developer is gone and all you keep is the executable.

Does any of this sound familiar?

The developer left

Nobody in the company understands how the application works and every change feels risky.

The source code is lost

All that is left is the executable, a few .NET DLLs or configuration files.

Unsupported technology

Visual Basic 6, Access, Delphi, FoxPro, old .NET Framework, legacy Windows Server.

Impossible to integrate

It does not connect to your ERP, your invoicing or any API. Everything is done by hand with Excel.

Operational risk

If the server fails or Windows updates, the company comes to a halt.

Zero documentation

Business rules hidden in the code that nobody has written down anywhere.

How we work

Assessment

We inventory what you have (executables, databases, scheduled tasks, dependencies) and evaluate the risk, condition and real effort of each piece.

Logic recovery

We reconstruct what the application does: decompilation when applicable, database analysis and tests that lock in its current behaviour.

Incremental migration

We replace it module by module, with the old and new systems running side by side, so operations do not stop for a single day.

Go-live and support

Controlled rollout with a rollback plan, documentation and ongoing maintenance if you need it.

What we migrate, and to what

.NET applications

From .NET Framework to modern .NET (LTS), starting from WinForms, WPF, WCF or Web Forms.

Visual Basic 6, Access, Delphi, FoxPro

Data model extraction and reimplementation of the business rules as a web application.

Old databases

From old SQL Server or Access to current engines such as PostgreSQL, verifying data integrity.

Scripts and loose tasks

VBScript, batch, Python 2 or macros turned into maintainable services with logging and alerts.

What you receive

Source code and documentation

All the code and the documentation of the recovered business logic belong to you.

Tests that protect behaviour

To check that the new system does the same as the old one before switching it off.

Migration and rollback plan

With clear phases, risks and checkpoints.

Fixed quote after the assessment

You know what it costs before committing to the full migration.

We work on software you own or have the right to act on. We review ownership and licences with you before starting. This is not legal advice.

Frequently asked questions

Can the code be recovered if I only have the executable?

Often yes, especially for .NET applications, which keep much of their structure when compiled. The result is not identical to the original code (comments and sometimes names are lost), but it lets us recover the business logic. We confirm it in the assessment, before you commit to anything else.

How much does it cost to migrate an old application?

It depends on size, the condition of the code and the source technology. That is why we start with an assessment and, from it, give you a fixed quote for the migration.

Does the business have to stop during the migration?

No. We migrate module by module, with the old and new systems running in parallel, and only switch over once the new one has proven it does the same.

What happens to my data?

We always work on copies, verify integrity after each migration and never touch production without a rollback plan.

Do you work with companies across Spain?

Yes. We work remotely with companies across Spain.

Related

Contact

Email: jmoreno@stellariscode.com · Phone: +34 654 51 63 65