How to upgrade or downgrade a client
Check usage against the new plan first, then change the package, adjust billing, and confirm nothing broke on the way.
Clients change size. A site that started as a single page grows into something with real traffic; a client who once needed five mailboxes might now need one. Moving them between plans is usually a quick, in-place change from your reseller control panel — the part worth doing carefully is everything around it, not the change itself.
Confirm the move is actually needed
Before upgrading someone, check whether they have genuinely outgrown their current plan or are simply hitting a temporary spike — a one-off traffic event does not always justify a permanent plan change. Before downgrading someone, check their current usage against the new plan's limits properly; a client who asks to save money on a smaller plan they will immediately exceed is heading straight back to you with a "why isn't my site working" ticket.
Compare actual current storage, bandwidth and mailbox usage against the smaller plan's limits before making the change. A downgrade that immediately puts the account over its new limits is a worse outcome for the client than the conversation about why they cannot move down yet.
Tell the client before you change anything
Confirm with the client what is changing: the new limits, any price difference, and when the change takes effect. This matters even for an upgrade a client explicitly asked for — confirming it in writing avoids any confusion later about what was agreed, particularly around price.
Making the change
-
Change the package in your reseller control panel
Most reseller platforms let you move an account to a different package in place, without recreating it — files, database, email and domain settings stay exactly where they are. Check your specific control panel's process, as this is where a wrong click matters most.
-
Confirm the site and email straight after
Load the site and check a mailbox sends and receives before considering the move complete. A package change is usually clean, but "usually" is not the same as "always", and a two-minute check catches the exceptions before the client does.
-
Update the billing to match
Adjust the recurring charge on the account to the new plan's price. Decide how you handle the current billing period — full charge at the new rate from the next renewal is the simplest approach, and proration is fairer but adds complexity. Whichever you choose, apply it consistently rather than deciding case by case, and make sure your billing software reflects it, not just your own notes.
Handle nameservers and domains sensibly
A plan change on the same reseller platform does not normally touch nameservers or DNS at all — the domain keeps pointing exactly where it already did, because the account itself has not moved anywhere, only its resource allowance has. The one exception worth checking is a client on a legacy setup pointing directly at an IP address rather than nameservers; confirm that address has not changed as part of the package move before you consider the job finished. If it has, treat it as a small DNS update alongside the plan change rather than something to discover later from a client asking why their site has disappeared.
Watch for a pattern, not just the individual request
If several clients on the same tier keep asking to upgrade for the same reason, that tier is probably sized wrong rather than each client being an individual exception. How to design the plans you sell covers adjusting your packaging when this happens, rather than handling the same conversation repeatedly as if it were new each time.
Keep an eye on your own plan's headroom too
Moving clients up uses more of your reseller plan's total capacity, not just the individual account's allowance. If you are upgrading clients regularly, periodically check where your own plan sits against its limits — see how many clients fit on a reseller plan? — rather than discovering the ceiling only once you hit it.
If you can see an account approaching its limits, raising it proactively reads as attentive service rather than a sales pitch, and it avoids the client finding out the hard way — via a full mailbox or a stalled upload — that they needed more room.
Handled properly, a plan change is a routine piece of account management rather than a risky operation. The risk mostly lives in skipping the check beforehand and the confirmation afterwards, not in the change itself.
Log every plan change somewhere outside the control panel too — your billing software's notes field is usually enough. A year from now, when a client queries their price or a limit, you want a record of exactly what was agreed and when, rather than having to reconstruct it from memory or guess at what the account looked like before.
Related reading
A short, clear list of plans that map to real client needs beats a long list of tiers nobody, including you, can remember the difference between.
How to bill hosting clients automaticallyRecurring invoices, automatic payment collection and a clear failed-payment process, so renewals no longer depend on you remembering them.
How many clients fit on a reseller plan?It depends on your plan's real limits and how much each client actually uses, not a fixed number that applies to everyone.
Do I need billing software to resell hosting?Not for your first few clients, but manual invoicing stops being manageable well before you might expect it to.