Moving a software product between cloud providers

A startup's free cloud credits are running out, and another provider is offering new ones. We count the full cost of moving, including the team's time, before recommending it.

2 min readMade-up stories, not client work

Cloud Migration: story 6 of 15

A made-up story

Picture a young software company whose free cloud credits are about to end. Another provider offers a generous new batch to switch.

What's going wrong

Switching sounds like free money. But the product uses features specific to the current provider, and the team is small and busy shipping.

What they have today

  • A product built on one provider's special services
  • A small engineering team
  • A growing cloud bill

What we can't ignore

  • Customers can't notice the move
  • The roadmap can't stop for months
  • Cash matters at this stage

The choices

  • Worth a look

    Switch providers for the new credits

    Saves money for a while, at the cost of weeks of engineering and some risk.

  • Our pick

    Stay, and trim the bill first

    Often cuts the bill without any move at all.

  • Maybe later

    Move to a simpler, cheaper host

    Worth a look if the product turns out to need only the basics.

What we'd do

Trim the current bill first and measure the result. Then compare it with the full cost of moving: engineering time, data transfer, rework, testing and running both for a while. Move only if the gap is big and lasting, and then move in stages.

Why

  • Trimming is quick and low risk
  • The full cost of moving is usually bigger than it looks
  • Engineers stay focused on customers

Where the money really goes

No prices here: this shows where the costs sit, not what they'd be for any real business.

The new credits are visible. The engineering weeks, the rework and the slower roadmap are not, and they're often bigger.

Cloud bill
Lower for a while with credits, then back to normal prices.
Engineering time
Weeks of rework and testing instead of new features.
Running both
Two bills while traffic moves across.

Running, growing, and staying safe

If something breaks

Staying put avoids the riskiest moment, the switch-over. If a move happens, stages keep it safe.

When it grows

Either provider can handle growth. The question is cost and effort, not capacity.

Keeping it safe

Every move means re-checking access and secrets. Staying avoids that work.

What the business gets

  • A lower bill without a risky move
  • A roadmap that keeps moving
  • A decision based on the full cost

These are the kinds of results the approach aims for, not measured results.

When we'd look again

If the trimmed bill is still far higher than the alternative, and the product is easy to move, a staged switch becomes worth pricing in detail.

If you liked this, read

About these stories. These stories are made up to show how we think. They are not client projects, describe no real business, and contain no measured results.

Next: Removing the single point of failure in a young SaaS product

Everything runs on one server, and a big new customer is asking about uptime. Two app servers and a managed database fix the real risk; a full rewrite would not.

Read the next story