When you migrate your reseller business, the right customer communication turns a potentially worrying event into a reassuring one. The good news is that because usernames, ownership, and databases are preserved, there’s very little your customers actually need to do — so your message can be short and confident. Here’s what to say and when.
The guiding principle
Tell customers what’s happening, reassure them it’s seamless, and be specific about anything they need to do (usually nothing). Over-explaining the technical detail invites worry; a calm, brief notice projects competence.
Before the move — a heads-up
A short advance note sets expectations: “We’re upgrading our hosting infrastructure for better performance and reliability. Your website and login details won’t change, and we’ll handle everything. We’ll let you know when it’s complete.” This frames the move as an improvement, which it is.
On cutover day — the window notice
If you’re switching DNS at a set time, a brief same-day note is courteous: “We’re completing our infrastructure upgrade today during [low-traffic window]. You may not notice anything; if you do, it’ll be brief. No action needed on your part.”
After the move — confirmation
Close the loop positively: “Our infrastructure upgrade is complete. Your site is now on faster servers. Your login and site are unchanged — if anything looks off, just reply and we’ll sort it immediately.”
What customers actually need to do
- Usually nothing — logins and sites are unchanged
- Only if they host email on devices and you moved mail servers: update mail server settings (supply them)
- Only if they manage their own DNS pointing at a raw old IP: update to the new one (supply it)
If something goes wrong
Have a brief, calm holding message ready in case a customer reports an issue: acknowledge, reassure that the old environment is available as a fallback, and that you’re on it. Because you keep the old server live for a few days, you can resolve issues without drama.
Get the tone right
The tone of your migration communication shapes how customers feel about it. Frame it as an upgrade (which it is), be specific that there’s nothing for them to do (which is usually true), and keep it brief. A confident, low-drama message signals that you have it under control. Over-explaining the mechanics invites questions and worry where none is needed.
Templates you can adapt
Advance notice (a few days before)
“We’re upgrading our hosting infrastructure to give you faster, more reliable service. Your website and login details won’t change, and we’ll handle the entire move for you. We’ll confirm once it’s complete — no action needed on your part.”
Cutover-day note (optional)
“We’re completing our infrastructure upgrade today during a low-traffic window. You likely won’t notice anything; if you do, it’ll be brief. There’s nothing you need to do.”
Completion note
“Our upgrade is complete — your site is now on faster servers. Your login and website are unchanged. If anything looks off, just reply and we’ll sort it right away.”
Be precise about customer actions
- Most customers: nothing to do — say so explicitly
- Customers with email on devices (if you moved mail servers): provide the new settings
- Customers managing their own DNS at a raw old IP: provide the new IP
Timing your messages
Align your messages with the migration timeline: a heads-up before, an optional window notice on cutover day, and a confirmation after. If you use private nameservers, you may not even need a cutover note, since customers’ DNS doesn’t change. Match the communication to how much (if anything) actually changes for them.
Have a calm fallback message ready
Prepare a brief holding response in case a customer reports a problem: acknowledge it, reassure them the previous environment is available as a fallback, and that you’re addressing it. Because you keep the old server live for a few days, you can resolve issues without it becoming a crisis — and your message can reflect that calm.
What’s next
- Private Nameservers During a Reseller Migration
- Accounts Keep the Same Usernames
- How to Roll Back a Migration if Needed
Still stuck? Our team can run or finish the migration for you — open a support ticket and we’ll take it from there.
Key takeaways
Frame the migration as an upgrade, keep messages brief, and be specific that most customers need do nothing — which is true, since usernames, ownership, and databases are preserved. Send a heads-up before, an optional window notice on cutover day, and a confirmation after. Keep a calm fallback message ready, knowing the old server stays live as a safety net.
What do my customers actually have to do?
For the large majority, nothing — their logins and sites are unchanged. The only exceptions are customers with email configured on devices (if you moved mail servers, give them the new settings) or those managing their own DNS at a raw old IP (give them the new IP). Say ‘nothing to do’ plainly where it’s true.
Common mistakes to avoid
- Over-explaining the technical detail and inviting needless worry
- Telling everyone to take action when most need do nothing
- Going silent and leaving customers guessing during the move
- Having no prepared response if a customer reports an issue
The best migration communication is calm, brief, and honest about how little customers need to do. Because the move preserves logins, ownership, and data, ‘nothing to do’ is usually the truth — and saying it plainly, with a confident upgrade framing, turns a potential worry into a non-event for your customers.
Was this helpful?
Thanks for your feedback!
