Reward-Point and Milestone Portability: What Survives a Product Change and What Does Not

Published: 19 October 2026 Category: how-to-guides | cardbuzz

You have spent eleven months chasing a milestone — one more month of spending and the big voucher unlocks. Then the bank offers you an upgrade, and a cold question lands: does your progress survive the move? Reward points and milestone counters are governed by portability rules that vary by issuer, and misunderstanding them is the most expensive unforced error in card upgrades. This guide maps what typically transfers, what typically resets, and how to protect both before you sign anything. All examples are illustrative.

Points vs milestones: two different assets

Treat these as separate things, because issuers do:

  • Reward points are a stored balance — a currency sitting in your account. On a product change within the same rewards programme, the balance usually carries over intact.
  • Milestone progress is a counter — spend ₹X within the anniversary year to unlock benefit Y. Counters are frequently tied to the specific card product and the anniversary cycle, and they reset far more often than point balances do.

The practical consequence: your 40,000 banked points are probably safe; your ₹3,80,000 of progress toward a ₹4,00,000 milestone (illustrative figures) may evaporate the day the new card activates. Always verify each asset class separately.

What typically survives a product change

  • Accrued reward-point balances, when both cards earn into the same programme. Most issuers pool points at the customer level rather than the card level, so a product change is invisible to the balance.
  • Account vintage and credit limit, which are account-level attributes, not card-level ones.
  • Add-on card linkages, usually — though the physical add-on cards are reissued (see the companion checklist).

What typically does not survive

  • Milestone spend counters. The new card commonly starts a fresh anniversary cycle with a zeroed counter, even if the old card was 95% of the way there.
  • Card-specific benefits already "in flight." Lounge-visit quotas, golf rounds or voucher entitlements tied to the old product generally do not transfer mid-cycle.
  • Fee-waiver spend counters. If your old card waived its fee at ₹3,00,000 of annual spend (illustrative) and you were at ₹2,80,000, that progress usually resets with the product change.
  • Accelerated earn categories banked toward caps. Monthly or quarterly category caps restart under the new card's terms.

"Typically" is doing heavy lifting in every bullet above. Issuer policies differ, and some issuers explicitly preserve milestone progress on upgrades as a goodwill feature. The rule is not to assume — it is to ask, in writing, before the change executes.

The pre-change audit: a four-step routine

Run this 2–3 weeks before any product change:

  1. Screenshot your points balance and milestone dashboards. Dated evidence resolves 90% of post-change disputes.
  2. List every in-flight counter: milestone spend progress, fee-waiver progress, lounge quota remaining, voucher validity dates.
  3. Redeem or accelerate what is expiring. If a milestone is within reach, consider pulling planned spending forward to cross it before the change. If points expire soon, redeem them — do not let a product change strand them.
  4. Get the portability answer in writing. Ask specifically: "Will my milestone spend counter of ₹[X] toward [benefit] carry over to the new card, or reset?" A vague "your benefits will continue" is not an answer.

Timing the change around the anniversary

The cleanest product changes happen just after an anniversary cycle closes: milestones have paid out, counters have reset naturally, and there is nothing in flight to lose. The messiest happen mid-cycle with a nearly-complete milestone. If your upgrade offer has no expiry, waiting 30–60 days for the cycle to close can be worth more than any upgrade bonus. Illustratively: forfeiting a ₹5,000 upgrade sweetener to protect a nearly-earned ₹10,000 milestone voucher is good arithmetic.

Conversely, if the old card's annual fee just hit and the new card's first year is fee-waived, the fee maths may favour moving immediately even at the cost of partial milestone progress. Run both sides; do not decide on instinct.

The downgrade case

Portability matters on the way down, too. When downgrading to a no-fee card, confirm that your banked points remain redeemable at the same value — some programmes devalue redemptions for lower-tier products, or restrict premium redemption options (airline transfers, for example) to higher tiers. An illustrative 40,000-point balance redeemed at ₹0.50 per point instead of ₹1.00 is a ₹20,000 haircut hiding inside a "free" downgrade. Ask for the redemption table of the destination product before you move.

A worked example: the mid-cycle upgrade trap

Assume you hold Card Old (illustrative: ₹8,000 annual fee) with an anniversary of 1 June. It is mid-April. Your milestone dashboard shows ₹4,50,000 of spend against a ₹5,00,000 milestone that pays a voucher you value illustratively at ₹12,000, and your fee-waiver counter sits at ₹7,60,000 against an ₹8,00,000 waiver threshold (illustrative). The bank offers an upgrade to Card New with an illustrative upgrade bonus worth ₹4,000, valid for 30 days.

If you move now and the counters reset, you forfeit a near-certain ₹12,000 milestone and a near-certain ₹8,000 fee waiver — ₹20,000 of illustrative value — to capture a ₹4,000 bonus. The arithmetic is not close. The disciplined play: let the offer lapse (targeted offers recur), push ₹50,000 of planned spending through Card Old in the next six weeks, collect the milestone and the waiver, then upgrade in the clean post-anniversary window. Patience here is worth roughly ₹16,000 on illustrative numbers — the best-paid waiting you will do all year.

Red flags in the fine print

  • "Benefits are subject to the new card's terms from the date of issuance" — usually means counters reset.
  • "Accumulated spends will be considered as per the new product's anniversary" — ambiguous; demand a worked example.
  • Any portability promise made verbally without a reference number — get it emailed.

Product changes are administrative events, but your points and milestones are financial assets. Audit them like assets: inventory, value, protect, then move.

All figures in this article are illustrative; actual fees, rewards and terms vary by card and issuer — always verify against the issuer's current most-important-terms document.