Renewing, upgrading, switching accounts: the order matters

Upgrading before renewing means paying twice for the same month. There is one correct order.

Three actions that look similar and cost very different amounts. Done in the right order, one of them saves you a whole month.

Case 1: plain renewal

The easy one. Renew before expiry, not after — some vendors require a fresh verification or a new payment method once the plan has lapsed.

Rule of thumb: handle it 2–3 days early. Not on the last day, and never across a weekend.

Case 2: upgrading

Correct order: upgrade first, then think about the renewal cycle. Doing it the other way means paying twice for the same period — once to renew the old tier, once to start the new one.

Unused days on the old tier come back proportionally; that is our own rule, written in the refund policy. So the cheapest sequence is: run the old tier almost to the end, then start the new one.

Case 3: switching accounts

Usually because the old account was banned or the region needs to change. Order matters more here: verify the new account can log in and can upgrade before paying. Otherwise the money is gone and the new account cannot be upgraded, which turns into a refund.

Conversations and projects do not move with you. Export what you need before abandoning the old account.

Case 4: two subscriptions at once

One account generally cannot hold two tiers of the same product. Running two in parallel means two accounts — and the two login environments must stay separate, or you invite a risk flag on both.

Quick reference

• Renewal only → 2–3 days before expiry
• Upgrade → start the new tier as the old one runs out
• New account → confirm it can upgrade before paying
• Parallel use → two accounts, separate environments

If you are still choosing a tier, start with the price list, then read monthly vs annual.

Back to plans →