Most Indian health-insurance policies get renewed on autopilot every year. The same insurer, the same product terms, the same premium with its annual increment. Portability is the one regulatory feature that lets you break that cycle and move to a different insurer's product without losing the waiting-period credits and no-claim bonus you have already earned. The feature exists. Using it correctly is a different question.
The decision this page helps you make is narrow but usually saves cash flow and coverage: should you port your current health policy at the next renewal, upgrade it with the same insurer, or leave it alone? The answer depends on whether the product is broken or the sum insured is inadequate, and on the underwriting you can realistically pass on the new insurer's side.
What portability guarantees you, and what it doesn't
IRDAI's portability framework is explicit about what transfers and what does not.
What moves with you:
- Waiting period credits already served, including pre-existing-disease waits and disease-specific waiting periods.
- No-claim bonus accumulated on the outgoing policy, added to the new sum insured up to the new product's NCB cap.
- Continuity of coverage for conditions already declared and covered on the outgoing policy.
What does not move:
- The premium. The new insurer prices the policy at their underwriting, which factors current age, health profile, and city-tier risk.
- The exact product terms. Room-rent sublimits, co-pay structures, disease exclusions, and benefit features can all change.
- Any pre-existing condition the new insurer declines to cover. Portability does not override the receiving insurer's right to underwrite.
The application window runs 30-60 days before the outgoing policy's renewal date. Applications earlier than 60 days get rejected as premature. Applications inside the last 30 days are formally late, though insurers may still accept them (up to 15 days past the deadline) at their discretion if there is no break in continuity — but that is a policy-level courtesy, not an entitlement. File in the 30-60 day window to remove the discretion risk.
What this means for you: portability preserves history, not product. Go in with a clear picture of what you want the new product to do differently, not the assumption that moving will be equivalent coverage at a better price.
The Port-or-Upgrade decision framework
Two distinct problems often get confused under the portability banner. The fix is different for each.
Port when the product is broken. Upgrade when the sum insured is inadequate.
Port triggers — product is broken:
- Room-rent sublimit cannot be removed on the current product (the outgoing insurer does not offer a no-sublimit variant).
- Claim experience has been poor — repeat deductions, TPA disputes, or reimbursements rejected on technicalities.
- Network hospital coverage for your city or tier has weakened versus competitors.
- The product has been discontinued and your renewal is on a grandfathered variant with weaker terms.
- Co-pay or disease sublimits apply at ages where the competition has no such limits.
Upgrade triggers — sum insured is inadequate:
- Tier-2 to Tier-1 city move (hospital billing doubles).
- Family size change (marriage, childbirth, parent dependency).
- Medical inflation has eroded the sum insured below a year of expected worst-case hospitalisation costs.
- NCB accumulation has outgrown the current policy's cap.
If the triggers are upgrade-only, stay with your current insurer and move to a higher sum insured or add a super top-up. Porting for upgrade reasons alone throws away the easiest part of continuity and introduces underwriting risk unnecessarily. If the triggers are port-type, the portability process is the right path — because staying with the same product preserves the same broken terms.
What this means for you: before any portability conversation, write down the specific thing that is broken with the current product. If you cannot name it, you are really shopping for a higher sum insured, which is an upgrade conversation with your current insurer.
Stress-test the premium cost
Run the premium estimator at your current age, preferred city tier, and target sum insured. Compare the output with the renewal notice from your outgoing insurer. A portability decision makes financial sense when the new product's effective premium (after accounting for portable NCB) is comparable or lower at the coverage level you want.
Pair this with the broader adequacy view at the adequacy hub and verify the target sum insured via the health insurance calculator. A port to a smaller sum insured almost never helps — you shrink the base cover and inherit fresh waiting periods on anything you later want to upgrade.
What this means for you: portability is an optimisation, not a rescue. Make the numbers pencil before you trigger the 30-60 day clock.
When porting costs you money
Portability is promoted by brokers and aggregators because it generates a fresh commission. The incentive is genuine, and three cases exist where the transaction genuinely loses money for the insured.
- Age-loaded premium step on the new product. Insurers apply age bands aggressively on newer products. At 45, 50, and 60 the step-ups can be sharp. If the outgoing product was priced under an older (cheaper) age curve, portability triggers the new curve and the premium rises materially for identical coverage.
- Grandfathered features lost on port. Some older policies carry no room-rent sublimit, no co-pay, or no pre-existing-disease sub-limit because of product terms that are no longer offered by any insurer. Porting throws those features away irreversibly.
- Pre-existing condition underwriting on the new side. A condition the outgoing insurer covered without fuss (declared and accepted years ago) may trigger a permanent exclusion on the new product. Read the acceptance letter line-by-line before cancelling the old policy.
Outside these three cases, portability is at worst coverage-neutral. Inside them, porting is net negative — the old product was protecting you from decisions you would not make again today.
Warning
Do not cancel the outgoing policy until the new policy is fully in force. Keep both active through any overlap period. If the new insurer requests medical tests and the results come back with an adverse finding, the new policy can be declined — at that point you want the outgoing policy still on autopilot, not already cancelled. Overlap of 15-30 days costs a small premium but preserves coverage continuity.
Info
For Section 80D deduction continuity under the old tax regime, the portability transaction is neutral. Premium paid on either policy in the same financial year deducts within the same ₹25,000 / ₹50,000 ceiling. There is no "portability hit" on 80D — the old and new premiums are treated as the same deduction bucket.
6-step portability playbook
- Write down the specific product defect driving the port. If the list is empty, cancel the port and pursue an upgrade with your current insurer instead.
- Set a calendar reminder 65-70 days before the outgoing policy's renewal date to begin paperwork.
- Shortlist 2-3 target products. Compare network, sublimits, and NCB caps directly against the defect you named in step 1.
- Run the premium estimator for each at your target sum insured. Verify the post-NCB effective cost.
- File the portability form 30-60 days before renewal (aim for the earlier end). Submit full medical history for any pre-existing condition.
- Keep the outgoing policy active until the new policy's first renewal notice arrives — only cancel after 30 days of confirmed active coverage on the new side.