Solve With Software

React, Angular and Node apps the agency left behind

A React, Angular or Node application from 2018 to 2022 whose agency has stopped replying is a legacy system with a young face. The code is mainstream, which is the good news. The bad news is that AngularJS died in 2021, Node 20 went out of support in April 2026, Create React App was retired in 2025, and the hundreds of packages the app depends on have moved on without it. Solve With Software takes the code into your own repository, gets it building on supported versions, recovers the hosting and the credentials, and then modernises it in stages, on a fixed price from the assessment.

Book a free consultation

Free · 1 hour · no obligation

Why a 2020 app is already legacy

Because the ground moved. A modern web application is a few thousand lines you wrote on top of a few hundred packages you didn't, and those packages have release schedules of their own.

  • AngularJS, the original Angular, reached end of life in December 2021. Applications on it get no fixes unless you pay a third party for extended support. The move to modern Angular is a rewrite, not an upgrade.
  • Angular gives each major version 24 months. Angular 22 is current; anything more than two majors back is unsupported.
  • Node.js 20 went out of support on 30 April 2026. Node 22 is in maintenance until April 2027; Node 24 is the version to be on.
  • Create React App, which most React projects of the era were started with, was retired in February 2025. It still runs; it's not maintained.
  • Everything else: a lock file with packages at 2020 versions, a build tool nobody has run in years, and a security scanner that lights up like a Christmas tree.

Built in 2003 or 2020, stuck is stuck. If your business can't move it forward, it's a takeover.

What we usually find

A codebase that's readable and a project that won't build. The agency's laptop had the right Node version, the right environment variables and the deploy script, and none of that came with the handover. Somewhere there's a Firebase project, a Heroku account or an AWS bill in the agency's name. The database is Postgres or Mongo on a hosted service whose login is in an ex-employee's inbox.

The application itself is usually fine. Rules in the API, screens in the front end, a data model that reflects the business. What it lacks is a home you control and a build that works on a machine that isn't the agency's.

The paths

Take it over and get it building. The repository into your organisation. Environment variables found or rebuilt. Node pinned to a supported version. A build that works on a clean machine, then in a test environment, then in staging. Hosting, database, domain and third-party services moved into accounts you own. This is the first stage, always, and it takes the app from "stuck" to "supportable" without changing what users see.

Upgrade in place. Angular major by major, with the official migration tooling, each step tested. React off Create React App onto Vite or a framework, with the components unchanged. Node to the current long-term release with the packages that need it updated. Contained work, done in stages, each priced.

Rewrite the parts that can't upgrade. AngularJS is the usual case: the components are rebuilt in modern Angular (or React, if the team prefers) one screen at a time, with a hybrid arrangement letting old and new run together until the last screen has moved.

Modernise and extend. Once it builds and it's on supported versions, the app is yours to move forward: the features the agency never finished, the integration that was always phase two, AI where it pays back.

The assessment reads the code and the package list and prices each path as a fixed number.

The things you need to own, and probably don't

Part of every takeover is a list of accounts, and it's usually longer than anyone expected: the source repository, the hosting, the database, the domain and DNS, email sending, file storage, the payment provider, the analytics, the error tracker, the app's own API keys to other services, and the developer accounts if there's a mobile app. Each one either moves into your name or gets recreated. The assessment produces the list; the first stage works through it.

Your data

Usually on a hosted database service, and it stays there or moves once into an account you own, reconciled on the other side. Nothing meets a change until the change has proven itself somewhere else: built and tested against a copy in a test environment, then run in staging, before anything connects to live.

What it costs

The assessment is from £395 + VAT, sized on a free one-hour consultation, with an exact price before you commit. For a React, Angular or Node app it gets the code building in a test environment, audits the packages and the accounts, and prices the takeover and the upgrades as fixed numbers. What drives the price and the payment terms each have a page.

The risks of waiting

Packages with published vulnerabilities and no one applying the fix. A runtime out of support on a public server. A hosting account in the agency's name that lapses when the card does. And the widening gap: every month the app isn't upgraded, the upgrade gets harder, because more of the ecosystem has moved on.

How we approach it

Get it building, get it owned, then move it forward in stages. Marc Allington builds on React, Angular and Node and has taken over enough agency-built applications to know where the environment variables hide. Everything we build runs on open, widely used technology, in your own accounts, with full source code and ownership transferring to you on final payment.

The technical checklist for a React, Angular or Node takeover

CheckWhy it matters
Does it build on a clean machine, and on which Node version?The first failure tells you what the handover missed.
Framework and version: AngularJS, Angular N, React with CRA or Vite, NextSets the upgrade path, and whether any part needs rewriting.
Package audit: unmaintained, vulnerable, pinned to nothingThe security exposure and the size of the upgrade stage.
Environment variables and secretsWhere they are, who has them, and which services they open.
Hosting, database, domain, DNS, email, storage, payments: whose name?The ownership list. Each moves or is recreated.
Tests, CI, deployment processUsually some tests and a deploy script that lives on someone's laptop.
Integrations and API keys to third partiesEach is a dependency and a credential.
Mobile app, if any, and the developer accountsA separate ownership problem with its own store deadlines.

Each answer goes into the report with its stage and a fixed price.

Questions

What people ask before they book.

Our app is only a few years old. Is it really a legacy system?

Age isn't the issue. Being stuck is. If nobody can build it, upgrade it or change it, it's a legacy system whatever year it was written, and the takeover is the same shape as for a VB6 one, with better tools.

Sometimes it's in a repository you already have access to and nobody realised. Sometimes it's recoverable from the deployed application. Sometimes the contract gives you the right to it and a letter gets it. The assessment establishes what you have before anyone spends money on a rebuild.

Not in place. AngularJS ended in 2021 and modern Angular is a different framework. The screens are rebuilt one at a time, with old and new running together, and the API underneath usually carries on as it is.

Only if the account moves into your name. Hosting, database and domain in someone else's account are the risk that turns a stuck app into a lost one. Moving them is the first stage.

It depends on how far the packages have drifted and how many accounts have to move, which the assessment measures. The shape is the usual one: building, owned and on supported versions within about six weeks, then stages, each priced before you commit.

Start with a free consultation

An hour on your system, online or by phone. From there we size the assessment, from £395 + VAT, and give you an exact price before you commit.

Want the numbers first? See how pricing works.

Written by Marc Allington, founder. .