- The businesses that regret switching hosts almost never regret the new host.
- They regret something they forgot to check before leaving the old one.
What to Check Before You Leave Your Current Hosting Provider in Nepal
Most regret we see around hosting switches in Nepal has nothing to do with the new host being worse. It's something left behind on the old account that nobody thought to check first: a domain still locked to the old registrar, an email address nobody remembered was configured there, an SSL certificate paid for a year in advance and abandoned. This is a checklist to run through before you give notice, not after.
1. Confirm Who Actually Controls Your Domain
Your domain registration and your hosting are sometimes with the same company, sometimes not, and it matters. If your domain is registered through your current host, unlock it and get the authorization/EPP code before you cancel anything, otherwise transferring it later becomes a slower, more painful process, sometimes requiring the very support team you're leaving.
2. List Every Email Account Actually in Use
Log into the current hosting control panel and list every email address configured there, not just the ones you remember using daily. Old staff accounts, an info@ address someone set up once and forgot, an invoicing@ address tied to accounting software, all of it needs to move or be consciously decided against, not silently vanish.
3. Check for Anything Auto-Renewing on the Old Account
SSL certificates, add-on domains, backup services, anything billed separately from the base hosting plan. Cancelling the main hosting doesn't always cancel these automatically, and providers don't always refund unused time, so check the billing panel directly rather than assuming.
Let WebsNP Manage Your Hosting So You Don't Have To
WebsNP's managed hosting plans include free cPanel migration from any other host, a Nepali support team on WhatsApp, and pricing in NPR with eSewa and Khalti accepted. We've been doing this in Kathmandu since 2014 — no ticket queue, no runaround.
See Managed Hosting Plans4. Export Everything You Might Need Later
- A full site backup, files and database, kept separately even after migration, as insurance against anything missed.
- Email archives if your provider doesn't guarantee full mailbox history transfers automatically.
- Any custom server configurations, cron jobs, redirects, or `.htaccess` rules that took time to set up and are easy to forget existed.
5. Get the Actual Cancellation Terms in Writing
Some Nepali hosts require notice before cancellation, some hold a final invoice, some have unclear policies on data retention after you leave. Ask directly, in writing, rather than assuming a graceful, no-friction exit. Knowing the terms before you start the move avoids a surprise final bill or a rushed timeline you didn't plan for.
6. Don't Cancel Until the New Setup Is Verified
Keep the old account active, even if you've stopped paying attention to it day to day, until the new host is fully tested: site loading correctly, email sending and receiving, DNS fully propagated. A week of overlap costs little. Cancelling too early, before confirming everything moved, is the single most common way a "smooth" migration turns into a real problem.
Making the Actual Move Easier
Once this checklist is done, the technical migration itself is usually the easy part. WebsNP's free cPanel migration handles the technical transfer, files, databases, email, DNS, so once you've confirmed domain control and listed what's on the old account, our team takes it from there. Message us on WhatsApp before you give notice to your current host, and we'll walk through what specifically needs to move for your setup.
