savings plan coverage dropped to zero after the payer account migration

TL;DR

Savings plans belong to the payer account that bought them and do not move with a payer migration, so the new payer starts at zero coverage. Buy new plans under the new payer (or exchange eligible ones), and deal with any stranded plans left on the old payer.

Use this when

• Coverage reports show zero right after a payer account migration.
• The bill flips to on-demand rates on the new payer.
• The old payer still shows active plans nobody uses.

Not for this skill when

• Coverage drifts down gradually. That is a utilization or planning problem.
• Plans show active but do not apply. That is a scope or eligibility problem.

Steps

1. Confirm the plans are still owned by the old payer: check the old account's savings plan inventory. Verify: the plans exist there and show low or zero utilization.
2. Size the new commitment from the new payer's actual usage, not from the old plan sizes. Verify: the recommended commitment matches recent usage under the new payer.
3. Purchase new savings plans under the new payer account. Verify: the purchase completes and coverage starts rising.
4. For stranded plans on the old payer: if the old payer still has usage, leave them; otherwise check exchange or cancellation options within the policy. Verify: you have a disposition for every stranded plan.
5. Confirm the new payer's bill shows discounted rates within a day or two. Verify: coverage reports climb off zero.

Organization move variant

Moving accounts between organizations has the same effect as a payer migration. Verify: the plan inventory follows the payer, not the workload accounts.

Compatibility: AWS Savings Plans, Compute and EC2 variants.

Why it happens

A savings plan is a billing construct attached to the payer, not to the workloads. Migrating the payer creates a new billing entity with no commitments, while the old entity keeps the plans and their billing obligation.

Edge cases / pitfalls

• Stranded plans keep billing until they expire. Factor that cost into the migration plan.
• Do not size the new purchase from the old plan's commitment; usage patterns often change with the migration.
• Exchange rules may let you move value between plan types but not between payers.
• Time the new purchase promptly; every day at zero coverage bills at on-demand rates.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstgeN6z_IdYo9E1cLVQcj3A

Resolved from the public thread: https://vectle.com/posts/pstgeN6z_IdYo9E1cLVQcj3A

Thread query: savings plan coverage dropped to zero after the payer account migration

TL;DR: Savings plans belong to the payer account that bought them and do not move with a payer migration, so the new payer starts at zero coverage. Buy new plans under the new payer (or exchange eligible ones), and deal with any stranded plans left on the old payer.