Question 1

What do cloud migration services include?

Accepted Answer

A migration covers everything needed to move a working system without losing data: an inventory of what runs today, a design for the target environment, building it, moving databases and files, testing on a copy of real data, the cutover itself, and shutting down the old setup. With us it also includes documentation of the new environment and a short support period after the move.

Question 2

How much downtime will a cloud migration cause?

Accepted Answer

For most business applications we plan a window of minutes to a few hours, usually out of hours. The figure comes from the rehearsal, where we time the final data sync and switch. Where even that is too long, we use database replication so the final step is a short write freeze. You get the expected downtime in writing before the cutover date is set.

Question 3

Can you move us from shared hosting or an office server to AWS or Azure?

Accepted Answer

Yes. Shared hosting and office servers usually hide cron jobs, mail settings and hard-coded paths, so the inventory step matters most here. We list every scheduled task, mailbox setting and integration before choosing the target. We also check whether a full AWS or Azure setup is needed at all, since a single VPS or Lightsail instance is often enough for a small application.

Question 4

Can you help us move off the cloud to a VPS or our own servers?

Accepted Answer

Yes. Repatriation makes sense for steady, predictable workloads where managed services and data transfer make up much of the bill. We compare the real running costs, including the work of maintaining servers yourself, and plan the move the same way as any other migration. AWS and Azure both offer, on request, a waiver of data transfer charges for customers moving their data out, and we check whether you qualify before the move.

Question 5

How do you make sure no data is lost during the migration?

Accepted Answer

We take a full backup before anything changes and test that it restores. After each data copy we compare row counts, file counts and checksums between old and new. During the cutover writes to the old system are stopped before the final sync, so nothing is written to two places. The old system stays intact until you confirm the new one is correct.

Question 6

How long does a cloud migration take?

Accepted Answer

A single application with one database is often a matter of weeks from inventory to cutover. Larger estates with several applications, integrations and large data volumes take longer and are usually moved in stages, one system at a time. The written plan gives you a timeline for each stage before work starts.

Question 7

How are cloud migration services priced?

Accepted Answer

Migrations are quoted as a fixed price after the assessment, based on the number of applications and databases, data volume, the downtime you can accept and how much needs fixing along the way. Ongoing management afterwards is a fixed monthly retainer. Tell us what you run today and where you want it, and we will send an estimate.

Question 8

Do we need to change our application code to migrate?

Accepted Answer

Usually only a little. Common changes are moving file uploads to object storage, reading configuration from environment variables instead of files, and removing hard-coded IP addresses or paths. We list these in the plan and can make the changes ourselves, since the same team writes application code.

Software, cloud and AI systems, built to last.

Nine disciplines, one engineering team.

Systems in production.

We also build products of our own.

A written architecture before any code is written.

The technologies we use, organised by layer.

IT systems that organisations depend on every day.

Our values

The sectors we work in.

Services built around your operations.

Looking for something specific?

{{ svc.title }}

Specific services

Related projects

{{ land.title }}

{{ land.problemsTitle }}

{{ land.includesTitle }}

{{ land.plansTitle }}

{{ land.stepsTitle }}

{{ land.whyTitle }}

Related work

Questions we get asked.

Industries we build for.

Our work, from 2020 to today.

{{ proj.title }}

Platforms we run. Libraries we publish.

Five stages, from first conversation to production.

Engagement models

Notes from the engineering team.

{{ post.title }}

{{ b.x }}

Common questions.

Tell us what you are building.

{{ legalTitle }}

{{ s.h }}

{{ ctaLead }} Let's talk.