Get onto AWS in waves while the business keeps working

We plan a route for each application, migrate in tested groups and modernise only the parts where the effort is worth it.

Sound familiar?

Which of these sounds like your team?

A renewal decision is coming

Your hardware or hosting contract is up for renewal, and a move to AWS is on the table.

Legacy systems set the pace

Your roadmap moves only as fast as the oldest application allows.

Tangled systems

Pull one application out and something else might break, but nobody can say what.

A move nobody should notice

Customers and staff keep working throughout, so every switch has to happen around them.

Paying more for the same servers

Year after year the hosting line in the budget grows, with nothing new to show for it.

The database is the bottleneck

New features stall because the database underneath can't support them.

Process

How we work

  1. 01

    Map what you have

    We list your applications, trace what each one relies on and estimate what it will cost on AWS.

  2. 02

    Choose a route for each

    Every application gets its own approach, and they are grouped into waves.

  3. 03

    Switch over group by group

    Each wave is tested before the switch, with a way to fall back if needed.

  4. 04

    Improve what's worth improving

    After the move, we improve the applications where the return justifies the work.

Specifics

Technical details

  • A full list of your applications, their data and what links them, plus an estimate of AWS running costs
  • For every application we pick one of the 7 Rs: rehost, replatform, refactor, relocate, repurchase, retain or retire
  • A secure base on AWS is in place before the first workload arrives
  • Applications that rely on one another move together, and each cut-over is rehearsed with a rollback ready
  • When the gain is clear, we bring in managed databases, event-driven integration, serverless functions or containers
  • Once live, resources are resized to match real usage

Options

Flexible to fit you

  • Lift applications across unchangedorRework them to suit AWS
  • One big switchorA series of smaller waves
  • Your engineers work with oursorGrootan does all of it
  • Grootan operates it after the moveorYour team takes charge after the move

Measurement

What we measure

  • How many applications are now on AWS
  • How long each switch takes you offline
  • What it costs to run everything each month
  • How often you can ship a change

FAQ

Questions we hear

Why modernise an application at all?

Because an older application makes every change slow and growth hard. Modernising is the rework that lifts those limits, leaving something your team can change, operate and scale without a fight.

Can our applications go across unchanged?

Yes, and that is often the first step. Modernisation can follow later, for the applications where it pays back.

What happens to the old system while you migrate?

Your users keep working on it. Behind the scenes, the new system is built and tested part by part, and only a tested part takes over from the old one.

What will the migration cost us?

That comes down to the size of the job and how complicated it is, which we look at together on the first call.

Start mapping your route to AWS

Related

More Cloud & AWS services