Architecture to scale
Legacy system modernization

Legacy systems: every day without patches counts

We bring CRMs, online stores and business systems stuck on unsupported versions up to date, without stopping day-to-day work.

Request an assessment Is your PHP still supported?

Spain and Latin America · Assessment before any quote · No downtime for your operation

End of support Live

1,435

days without security patches for PHP 7.4

Pick your system

The problem

It works. That is why nobody updated it.

Many companies grew on a system that was installed years ago and never touched again. On the outside it runs fine; underneath it runs on versions that no longer get patches, on an unsupported server, with customizations only the person who wrote them understands.

What we see most under a system that "runs fine" No security patches
  • PHP 7.4since Nov 2022
  • MySQL 5.6since Feb 2021
  • Joomla 3since Aug 2023
  • CentOS 7since Jun 2024
  • Drupal 7since Jan 2025
  • PHP 8.1since Dec 2025

Security without patches

Flaws found in old versions don't get fixed. The system stays exposed even if nobody notices.

How we fix it: we harden the server first and then upgrade.

Integrations that break

Payments, e-invoicing, email or the website stop connecting, and spreadsheets and manual data entry come back.

How we fix it: we reconnect each integration and test it on a copy.

Dependence on one person

If only one person knows how the system works, every change is slow, expensive or impossible.

How we fix it: we document what changed, where and why.

The assessment

It starts here: we check everything underneath

Before any quote we inventory the language, the database, the server, the system and its integrations. We measure which processes depend on each piece and what a failure would cost.

  • Versions and end-of-support dates for every component.
  • Customizations and integrations that must be kept.
  • Whatever exposes data or could stop the operation, first.
System review · example High risk
Review finished: 3 unsupported components100%
PHP 7.4.33System language Unsupported since 2022
MySQL 5.6Database Unsupported since 2021
CentOS 7Server Unsupported since 2024
Vtiger 6.5Sales and customers Customized
E-invoicingIntegration Fails at times
Recommended path: adapt the code and upgrade to PHP 8.3 Harden the server first. Everything is tested on a copy and the switch has a rollback.
Who we help

Is your system on this list?

CRMs, stores, websites and in-house systems still running on unsupported versions. Find yours: next to it is the guide to understand the risk it carries.

Yours isn't listed?

We can still assess it: the method is the same for any system.

Tell us which one
What we do

Four paths, from the shortest to the deepest

After the assessment we choose with your team the shortest path back to a supported system. You don't always have to rebuild anything.

  1. From day 1

    Harden

    We reduce exposure right away: access, server and verified backups. It buys time with the risk under control.

    Best whenthe risk has to come down now, while the rest is planned.

  2. Upgrade

    We move the system to a current version on PHP 8.3 or later, with its customizations and data.

    Best whenthe product is still alive and has a new supported version.

  3. Adapt the code

    For custom systems, we fix the code so it runs on current PHP versions.

    Best whenthe system is well built and what got old is what lies underneath.

  4. Migrate or redesign

    We move the data and processes to another platform, or build a custom system.

    Best whenthe system no longer fits how the company works.

If the system no longer fits the business, we cover it in custom software development.

No downtime

The same system, supported again

Same data, same customizations, same integrations. What changes is what lies underneath.

Operation online during the whole switch

Language
TodayPHP 7.4No patches since 2022
AfterPHP 8.3Supported until 2027
Server
TodayCentOS 7Unsupported since 2024
AfterUp to datePatched, with verified backups
Database
TodayMySQL 5.6Unsupported since 2021
AfterMySQL 8.4Supported, with daily backups
Invoicing
TodayBy handThe integration broke
AfterAutomaticIntegration working
  • A system that gets security patches again.
  • Integrations that work without manual data entry.
  • Documentation: what changed, where and why, so you don't depend on a single person.
  • A maintenance plan so it doesn't happen again.
How we work

Modernize without stopping the operation

  1. Assessment. We inventory versions, server, integrations and customizations. We measure which processes depend on the system and what a failure would cost.

  2. Plan with dates. We choose the path (upgrade, adapt, harden or migrate) and order it by risk: first whatever exposes data or could stop the operation.

  3. Test copy. Everything is done first on a copy of the system. Nothing touches production without being tested.

  4. Go-live. We switch at the lowest-impact moment, with a rollback ready.

  5. Ongoing support. The system is documented and maintained, so it doesn't fall behind again. See software support and maintenance.

PHP versions

Is your PHP version still supported?

On October 21, 2026, PHP fixed two critical flaws. The minimum safe versions are 8.2.35, 8.3.36, 8.4.27 and 8.5.12, and PHP 8.1 or older don't get the official fix.

Which version does your system run?

Pick a version.

We tell you whether it still gets patches and which path usually makes sense.

Supported PHP versions and minimum safe version
Branch Minimum safe version Supported until
PHP 8.5 8.5.12 2029
PHP 8.4 8.4.27 2028
PHP 8.3 8.3.36 2027
PHP 8.2 8.2.35 Dec 31, 2026
PHP 8.1 or older No official fix Ended

We explain it in detail (in Spanish) in Actualizar PHP: qué riesgo corre un sistema sin soporte.

Written assessment

An assessment before touching anything

We review your system and give you, in writing:

  • Which version each piece runs and since when it has been unsupported.
  • What risk it carries today, ordered by what could stop the operation.
  • The shortest path back to a supported system, with fixed timeline and cost.
Request an assessment

No commitment · Remote, Spain and Latin America · No downtime

FAQ

What people ask us before starting

If your question isn't here, message us on WhatsApp.

What is a legacy system?

It is a system the company still uses every day, but that sits on old technology: unsupported versions, code nobody maintains or integrations that no longer work. The problem isn't its age, but that it has become a risk to the operation.

What happens if I keep using an unsupported version?

The system keeps working, but every new flaw that is discovered stays open forever. Over time, integrations, modules and payment gateways that require current versions also stop working.

Does the system have to be rebuilt from scratch?

It is almost never the first step. Often upgrading it or adapting its code to current versions is enough. Rebuilding only makes sense when the system no longer fits how the company works.

Are the data and customizations kept?

Yes, that is the starting point. In the assessment we list every customization and integration that has to stay, and the migration is checked against that list before going to production.

Can it be modernized without stopping the operation?

Yes. Everything is prepared and tested on a copy of the system, and the production switch happens at the lowest-impact moment, with a rollback ready in case something doesn't go as expected.

What if whoever built the system is gone?

That is the most common case. We read the code and the database, rebuild how it works and document it, so the company stops depending on a single person.

What do you need from our team for the assessment?

Read access to the server and the system, and a talk with whoever uses it every day. We work remotely and on your schedule.

How long does it take and how much does it cost?

It depends on the system, its customizations and integrations. Adapting a well-built system can take weeks; migrating a heavily customized one, months. After the assessment we give you a plan with fixed timelines and cost.

Who maintains it afterwards?

Your team can, with the documentation we leave, or we can take care of it with a support and maintenance plan so the system doesn't fall behind again.

Do you work with companies in Spain and Latin America?

Yes. We work remotely with teams in Spain and across Latin America, on their schedule and under their regulations (for example, data protection in Spain or e-invoicing in Argentina or Mexico).