Cloud migration with the bill modelled before the move, not after

Most disappointment with cloud comes from one omission: nobody modelled the monthly bill before the migration, so «cheaper» turned out to mean «differently expensive».

Custom software SaaS products AI development Web applications AI chatbots Nearshore teams

Cloud migration

Assessment first, strategy per component, then the move

There is no single cloud migration. There are three strategies, and most systems need a different one per component.

What cloud migration services actually involve

A migration is three decisions repeated per component. Rehost — move the virtual machine as it is: fastest, least benefit. Replatform — swap the database or queue for a managed service: moderate work, most of the operational gain. Refactor — change the application to use cloud primitives: expensive, justified only where it removes a real constraint.

Which one applies is a per-component answer, and it depends on licences, data gravity, compliance and how much the team can operate afterwards. That is what the assessment produces — along with a modelled monthly bill, which is the number people actually get wrong.

When a migration is justified — and when it is not

Justified when hardware is at end of life, when scaling means procurement, or when a single person is the only one who can rebuild the environment. Not justified when the workload is steady, well understood and already cheap on owned hardware: we will say so, and moving back from cloud is a legitimate project we also take.

Signals it is time to move

hardware is at end of life or out of warranty;
scaling up means a procurement cycle, not a config change;
backups exist but have never been restored;
the environment can be rebuilt by exactly one person;
the current cloud bill is growing faster than the load.

Signals it is time for cloud migration: ageing hardware, procurement-bound scaling, untested backups and a bus factor of one

Price

Assessment $1,790, migration from $18,900

Timeline

Assessment in 5 days

Payment

50/50 by milestone

Pricing

What a cloud migration costs with us

The assessment comes first and is credited against the work. Cloud bills go to your account directly — we are not a reseller and take no margin on infrastructure.

Rehost, replatform or refactor

Three strategies, and the honest answer is usually «different ones for different components».

Criterion

RehostReplatform (managed services)

ReplatformRehost (lift and shift)

Time to move

Fastest — weeks

Moderate — weeks per component

Operational gain

Almost none: same servers, new landlord

Backups, patching and scaling become someone else's job

Monthly bill

Often higher than the hardware it replaced

Predictable, and modelled before the move

Application changes

None

Config and connection strings, occasionally code

Risk profile

Low technical risk, high bill risk

Moderate, staged, reversible

When it wins

Deadline-driven exit from a data centre

You want the operational benefit, not just a new location

Process

How the move runs, and where the money hides

The cost model is the part most vendors skip — it is the first thing we produce.

The cost model, before anything moves

We price the target architecture component by component: compute, storage, managed database, egress, inter-zone traffic, backups and support plan. Egress and cross-zone traffic are where estimates usually fail, so they get their own line.

The gap between the modelled bill and the first real invoice is a number we track — it belongs in the report, not in a surprise.

Environment parity and infrastructure as code

Terraform or equivalent from the start, so staging and production are the same thing with different sizes, and rebuilding the environment is a command rather than a memory.

Nothing is configured by hand in a console, because a hand-built cloud is a new bus factor of one.

Data move with a dry run

Every data migration is rehearsed on a copy: row counts, integrity checks, a data-quality report and a documented cutover with a rollback window.

For large datasets we plan the transfer method and the freeze window explicitly rather than hoping the link holds.

Cutover, then cost review

Staged cutover by component with rollback available at each step; unavoidable windows agreed in advance and kept short.

Thirty days after the move we review actual spend against the model and tune what is over-provisioned — see DevOps services.

Why us

Why teams hand us the migration

Four things we can prove, rather than four adjectives.

No reseller margin, no vendor bias

We take no commission from AWS, Azure or GCP and do not resell their capacity. The recommendation follows your licences and your team, not our margin.

The bill is modelled up front

A per-component monthly estimate before the move, including egress and inter-zone traffic — the two lines that turn a cheap migration into an expensive one.

Rollback at every step

Staged cutover with a way back at each component. No single weekend decides whether your business trades on Monday.

Infrastructure as code, handed over

The environment is code in your repository, with a runbook a new engineer can follow. If you never call us again, nothing stops working.

Industries

Cloud migrationby industry

Data gravity and compliance differ by domain: warehouses and lines cannot pause, property portals cannot lose listings, finance cannot lose an audit trail.

18 sectors

IT companies and digital agencies
Insurers and brokers
Lenders and microfinance
E-commerce
Wholesale and distribution
Manufacturing
Freight and forwarding
Clinics and medical centres
Dental
Car dealers and service centres
EdTech
Legal and consulting firms
Equipment rental
Real estate agencies
Property developers
Travel and events
Beauty and wellness
Construction and renovation

FAQ

Cloud migration questions

Six answers that usually replace a discovery call.

How long does a cloud migration take?

Weeks per component, staged, with rollback at each step. The assessment produces a per-component plan before anything moves.

AWS, Azure or GCP?

Whichever your team can actually operate and your licences favour. We are not a reseller and earn nothing from the choice.

Will it be cheaper than what we run now?

Sometimes. We model the monthly bill before the move; if the honest answer is no, you get that in writing rather than in the first invoice.

Can you move us back, or between clouds?

Yes. Repatriation and cloud-to-cloud moves are legitimate projects, and infrastructure as code is what makes them possible without a rewrite.

What about downtime?

Staged cutover with a rollback window. Where a freeze is unavoidable it is agreed in advance and kept as short as the data allows.

Do you stay on after the migration?

Optional. DevOps support from $790 a month, or a clean handover with a runbook your team can follow — both are real options, not one disguised as the other.

2–4×

faster on the code-writing share

in 3 weeks

from idea to MVP

230+

projects delivered

17 years

of engineering experience

Work