Skip to content
ANB Codes

AI and automation

Upgrading old software

We move apps off ageing code, expensive no-code builders and hosted sandboxes onto a modern stack under your own accounts, with the live data intact and no surprise downtime.

Overview

Move old or outgrown software onto something modern that you own.

Many businesses run on software that was built quickly, on a no-code builder or a hosted sandbox, and has since become expensive or hard to change. Often the owner does not even hold the code, database or hosting in their own name. Moving to a modern set-up under your own accounts restores control and makes future changes cheaper and safer.

The first step is deciding what moves as it is, what needs fixing and what should be rebuilt. New accounts for code, database and hosting are then opened in your company's name. The live data is copied and checked repeatedly, table by table, until every count matches, and security gaps found along the way are closed before the switch.

The switch happens at a quiet hour, with the old system kept ready as a fallback for an agreed period. You receive the migrated app, a migration report and a rollback plan. A cookware distributor's system was rebuilt this way, with its existing records carried across. Afterwards, a care plan can keep the new set-up maintained and up to date.

What you receive
Migrated app · Migration report · Rollback plan
Typical technology
GitHub · Vercel · Supabase · PostgreSQL · Docker

Who it's for

Is this right for you?

If the current app is stable, affordable and easy to change, moving it may not be worth it yet.

  • A business whose app is stuck on a builder platform with rising bills
  • A company with software that was built fast and is now hard to change
  • An owner who doesn't hold the code, database or hosting in their own name

Scope

What goes into it

Every engagement is scoped to your goal. These are the parts most projects include.

  • AssessmentWhat to keep, what to fix and what to rebuild.
  • Data migrationRehearsed, verified and reversible.
  • Security fixesClose gaps found during the move.
  • Your own accountsCode, database and hosting in your name.
  • Cut-over planA quiet-hour switch with a fallback.

Timeline

How a typical project runs

Usual length: usually 4 to 16 weeks. Your written scope gives the exact plan.

  1. 01Weeks 1–2

    Keep, fix or rebuild list

    We review the app, data and hosting, and agree which parts move as they are and which need work.

  2. 02Weeks 2–3

    New accounts in your name

    We open the code, database and hosting accounts under your company, with delegated access for us.

  3. 03Weeks 3–12

    Rehearsed data move

    We move a copy of the live data, check every table and count, and repeat until it matches every time.

  4. 04Weeks 12–16

    Quiet-hour cut-over

    We switch at a quiet hour, check the live system, and keep the old one ready as a fallback.

One-time project

A fixed quote for an agreed scope, paid in milestones. You own the code and accounts once it's paid.

Monthly care plan

A monthly subscription that keeps your software secure, monitored and improving, with response times in writing.

Getting started

What happens after you get in touch

Discuss your project
  1. 01Tell us the problemA short form or a call. A senior lead replies within one working day.
  2. 02One callWe sign an NDA first if you need one, then go through your goals, users and current systems.
  3. 03Written scope and fixed quoteWithin 48 hours of the call, with milestones and a timeline.
  4. 04Build in milestonesYou see working software at every milestone, and you own what we build.

Questions

Before you ask

What changes the size of the job

  • The size and age of the app, and how much needs rewriting
  • How much live data there is and how many places it's stored
  • Security gaps or broken features found during the move
Will there be downtime?

Usually minutes, scheduled for a quiet hour, with the old system kept as a fallback.

Can we keep using the app while it's being moved?

Yes. Your team keeps working on the old system throughout. Only the final switch needs a short pause, at a time you choose.

What happens to the old platform afterwards?

We keep it as a fallback for an agreed period, then help you export a final copy and close the account.

How is this priced?

As a one-time project with a fixed quote, agreed after a short call and paid in milestones. After launch you can add a monthly care plan for hosting, updates and support.

Previous work

Projects where we did this

Tell us what you need built.

Share the problem in a few lines. After one call you'll get a written scope and a fixed quote within 48 hours.