Legacy System Modernization

We read other people's code and modernise a running system without stopping it. The audit comes first, then a plan: what to keep, what to rewrite and what to leave alone.

Price: from $300 Timeline: after the audit

This is a starting price. The exact figure and timeline come from your technical brief, and the review is free.

Who it is for

Modernisation usually starts with a call about something that has already broken, or is about to. The system still runs the business, the person who wrote it is unreachable, and the platform underneath stopped receiving security updates at a date nobody recorded. We give no timeline before reading the code. A number produced without that reading is a guess, and calling it a plan does not make it one.

Problems we solve

· The developer who wrote the system is gone and nobody understands the code
· Every change breaks something unexpected
· The platform no longer receives security updates
· A rewrite is expensive and doing nothing is risky

What is included

· Code and infrastructure audit
· A risk map: where a failure is most likely
· A staged plan with a result for each stage
· Backups and a tested restore procedure
· Step-by-step modernisation without downtime
· Documentation, so another team can continue

What we can build

· Modernisation of legacy web applications
· Migration to a supported platform
· Gradual decomposition of a monolith
· An integration layer over an old system

How we work

· We read the code and the database and describe how the system works
· We show the risks and the urgent points
· We agree a plan with stages, timelines and outcomes
· We work in small reversible steps
· We hand over documentation and credentials

Engagement models

· An audit with a plan, decided on separately
· Time and materials for the modernisation stages
· Support for the modernised system

We also work with off-the-shelf systems

Every widespread system has passed through our hands: WordPress, Joomla, Drupal, OpenCart, DLE. A project written by somebody else does not have to be rewritten from scratch before we can work on it.

What that gives you:
· we learn an unfamiliar codebase and an unfamiliar admin panel instead of turning the project down
· we update the engine and its extensions and close the vulnerabilities that piled up
· we write modules for the system when no ready extension exists
· we move the site to another server and speed it up without downtime

For a new project we do not propose such a system, and the web development page explains why. If your site already runs on one, there is no reason to rewrite it for our convenience.

Stack

Laravel NestJS PHP TypeScript Python Celery Next.js React Vue 3 Inertia.js Blade Tailwind CSS PostgreSQL MySQL Redis Meilisearch iOS Android Docker nginx PM2 Obsidian Telegram Bot API JSON-RPC Claude API

Projects for this service

IT for FinTech and Payment Companies
113 database tables in the legacy platform we maintain

Two generations of a high-load digital asset platform

A legacy core of one hundred and thirteen tables that we maintain, and a new system with balances, user-to-user deals and identity checks.

Laravel PHP PostgreSQL Redis

Industries we do this for

CRM and ERP Development for Existing Systems

We work with companies that already run a system: extending it to fit a changed process, connecting it to the website and accounting software, migrating away from a platform that stopped fitting.

Frequently asked questions

How long does modernisation take?
It is set after the audit. A timeline cannot be given without reading the code, which is why this service has no "from N days" figure: inventing one would mislead both sides.
How do you price modernisation?
Modernisation starts from $800, but the real scope becomes visible only after the audit: the state of the code cannot be read from the outside. The work splits in two: the audit, priced up front by the size of the system, and the modernisation, priced against the agreed plan.
Is a rewrite not cheaper?
Sometimes it is, and we say that out loud. More often a rewrite loses business rules accumulated over years, because they are written nowhere except in the code. The decision is made after the audit, on facts.
Will the system stay online?
Yes. Modernisation runs in stages, each step is reversible and backups are verified before anything starts.

Read next

Discuss your task

Leave a name and a phone number, and we will ask the rest in the conversation.

For example, +998 90 123 45 67

If the brief is already written, attach the file: PDF, DOC, DOCX, TXT, image or ZIP, up to 10 MB. Only we can see it.

We reply within one business day

Have an idea for a new product, or need to grow an existing one?

Tell us about the task. We will study it and propose an option that makes sense technically and economically.

We reply within one business day · Telegram @sbunyod

from $300 Discuss a project