Cloud migration / Migration planning

Cloud Egress and Exit Cost: What to Price Before Moving

Short answer: Cloud egress is only one part of exit cost. A serious migration estimate also prices data export, recurring transfer, storage retrieval, rewrites, testing, downtime, rollback, and new operations.

Decision rule
  • Move only when repeatable savings survive migration cost and the new operating model.
  • Verify current provider pricing directly before buying or migrating.

RunPlacement quiz

Pressure-test this workload

Move only when repeatable savings survive migration cost and the new operating model.

Uses workload type, budget, GPU need, data movement, priority, and ops tolerance.
Use the quiz

Right fit

  • A cheaper provider looks attractive but the data path is unclear.
  • A team wants to leave a major cloud after a cost spike.
  • The workload may be partially movable instead of fully portable.

Quick checks

  • Estimate total data to export and recurring data movement after migration.
  • Check storage retrieval, replication, snapshot, and backup assumptions.
  • Price testing, downtime, rollback, and provider-specific service replacements.

Rough math

  • Exit project cost = data movement + engineering time + testing + downtime risk + rollback buffer.
  • Monthly savings = current steady run rate - destination steady run rate.
  • Payback period = exit project cost / monthly savings.

Red flags

  • The destination quote excludes equivalent backup, monitoring, and support.
  • The current workload depends on managed services that must be rebuilt.
  • The team prices egress but ignores downtime and rollback.

What to do next

  • Use the cloud exit checklist to price the move.
  • Consider partial migration if one line item causes most of the pain.
  • Run the quiz after the current baseline and target baseline are known.

Related resources

Use a worksheet before making the call

These supporting pages turn the decision into fields a buyer, engineer, or founder can actually compare.

Cloud migrationCloud Exit Cost ChecklistChecklist / 7 sections / sourced

A checklist and payback worksheet for pricing the real cost of leaving AWS, GCP, or Azure before migration starts.

 Workload placementWorkload Placement WorksheetChecklist / 7 sections / sourced

A practical worksheet and decision map for deciding where a workload should run before provider choice hardens.

Related decisions

Keep narrowing the placement question

Follow the adjacent pages when the first answer exposes a deeper cost driver or operating constraint.

Cloud migrationBare Metal vs Cloud Break-Even: When Dedicated Servers WinCommercial comparison

Bare metal can win when a workload is steady, portable, highly utilized, and operationally owned. Cloud usually wins when flexibility, managed services, or variable demand matter more than unit cost.

 AWS bill shockAWS Pricing Calculator Alternative: What to Use for Placement DecisionsTool evaluation

For placement decisions, an AWS pricing calculator is useful but incomplete. You also need workload shape, hidden bill drivers, migration cost, operational tolerance, and whether the problem is AWS itself or one expensive line item.

 Workload placementManaged Platform vs Cloud: When Less Control Is the Better PlacementCommercial comparison

A managed platform can be the better placement when engineering focus and reliability matter more than infrastructure control. Direct cloud can be better when the team needs flexibility, deep customization, or lower unit cost at scale.

Framework

Use the underlying decision model

These framework pages define the terms and formulas behind this specific decision.

Cloud migrationCloud Exit Payback Frameworkcloud exit payback

Cloud exit is financially serious only when steady savings repay migration work, data movement, service replacement, downtime risk, rollback planning, and new operations inside an acceptable window.

 Workload placementWorkload Placement Frameworkworkload placement

Choose workload placement by matching the workload's cost driver, data movement, performance needs, operational tolerance, and commitment horizon to the right infrastructure category.

FAQ

Is egress the same as cloud exit cost?

No. Egress is a data transfer line item. Exit cost also includes engineering work, testing, downtime risk, rollback, and replacement services.

When is partial migration better?

Partial migration is often better when one workload slice causes the cost problem and can move without dragging the whole platform with it.

How long should migration payback be?

That depends on risk tolerance, but the payback window should be explicit before the team treats a lower hosting quote as savings.

Sources

RunPlacement quiz

Pressure-test this workload

Move only when repeatable savings survive migration cost and the new operating model.

Uses workload type, budget, GPU need, data movement, priority, and ops tolerance.
Use the quiz