Introduction
A website migration is one of the riskiest jobs in web development. Move a host, change a domain, switch platforms, or redesign a site, and a small mistake can cost you rankings, traffic, emails, and sales for months. Yet migrations are unavoidable: hosting gets slow, a rebrand needs a new domain, or a growing business outgrows its old platform.
This website migration checklist for Indian businesses covers the whole move, from planning to the day of the switch to the 30 days after. It includes backups, DNS and email records, WordPress steps, SEO protection, e-commerce and payment testing, a rollback plan, costs, and the mistakes that cause most failures. Follow it in order, tick every item, and your migration will be boring in the best possible way: nothing breaks, and nobody notices except you.

What Is a Website Migration?
A website migration is any major change to where or how your website runs. The common types are changing hosting providers, changing domains, moving from one platform to another such as Wix to WordPress or Magento to WooCommerce, switching from HTTP to HTTPS, redesigning the site, and merging two websites into one. Many Indian businesses do two at once, such as moving host and redesigning, which doubles the risk and makes a checklist essential.
The reason migrations fail is rarely the move itself. It is the things people forget: an email record, a redirect, a tracking code, or a payment gateway setting. This checklist exists to catch those things before they cost you money.
Before You Start: Planning and Inventory
Start two weeks before moving day. First, write down why you are migrating and what success looks like: faster loading, lower cost, a new domain, or a better platform. Then take a full inventory of everything that must move.
List your domain and registrar, hosting account, SSL certificate, email accounts and provider, subdomains, databases, files, plugins and themes, payment gateways, forms, CRM and email marketing connections, tracking codes, and any scheduled jobs or cron tasks. Note every third-party service that talks to your website, including UPI payment gateways, SMS providers, WhatsApp APIs, and shipping integrations. Indian sites often forget the SMS and UPI connections, and those are the ones that break orders silently.
Set a timeline by site type. A small brochure site usually takes 2 to 4 days. A WooCommerce store or a site with 500 plus pages usually takes 1 to 2 weeks. Pick a low-traffic window for the switch, typically late night or early morning on a weekday, and tell your team and your customers in advance if downtime is possible.
Backups: Your Safety Net
Never migrate without a full backup, and never trust a single backup. Take a complete backup of files and the database, download it to your own computer, and store a second copy in cloud storage. Test that the backup actually restores, because a backup you have never tested is only a hope.
For WordPress sites, use a plugin such as UpdraftPlus, Duplicator, or All-in-One WP Migration to create the backup, and keep the backup file outside the hosting account you are leaving. Write down every login you will need on moving day: hosting, domain registrar, email, payment gateway, and Search Console. If you do not have registrar access, get it now, because a migration without domain access can stall for days.
DNS and Email: The Records That Break Most Migrations
DNS is where most migrations go wrong, so handle it carefully. At least 48 hours before the move, lower the TTL (time to live) on your DNS records to 300 seconds. This makes the switch propagate in minutes instead of hours when you change the records.
Take a screenshot or export of every DNS record before you touch anything: A, AAAA, CNAME, MX, and TXT records. Email runs on MX records, and spam protection runs on SPF, DKIM, and DMARC records. If you move hosts and forget to copy the MX records, your email stops. If you forget SPF and DKIM, your emails start landing in spam. Test email sending and receiving on the new host before you switch the DNS, and test again after, including order confirmation emails and contact form emails. Google Workspace and Zoho Mail are common in India, so confirm their exact records with their setup guides rather than guessing.
The WordPress Migration, Step by Step
Most Indian small business sites run on WordPress, so here is the method that works. First, create a staging copy on the new host and install the same WordPress version, theme, and plugins. Second, migrate the files and database with Duplicator or All-in-One WP Migration, and run a search-and-replace for the old domain if the domain is changing. Third, check the staging site page by page: home page, key service pages, blog posts, contact forms, login area, and checkout.
Fourth, test the admin area, the media library, and scheduled posts. Fifth, update the site URL settings and check that images load from the new location. Sixth, only when the staging site is perfect, point the DNS to the new host. Our guide to How to Speed Up a WordPress Website in India is worth reading before the move, because a migration is the best time to fix speed problems rather than carry them to the new host.
SEO Protection: Redirects, Sitemaps and Search Console
SEO protection is the part that saves your rankings. Crawl your old site with a tool such as Screaming Frog and export every URL. Build a redirect map: every old URL must point to the right new URL with a 301 redirect. Never redirect everything to the home page, because Google treats that as a soft 404 and your rankings will fall.
If the domain is changing, use the Change of Address tool in Google Search Console, and verify both the old and new properties. Update the XML sitemap, the robots.txt file, and all canonical tags to the new URLs. Remove any staging blocks, such as noindex tags, robots.txt disallows, and password protection, before you go live. Check that Google Analytics, Tag Manager, and Google Ads tracking codes are present on the new site, because losing tracking means losing your data. Keep the old hosting active for at least 30 days after the move, so you can roll back if something goes wrong.
Testing Before You Go Live
Test the new site as if you were a customer, on both mobile and desktop. Check the home page, the five most visited pages, the contact form, the login area, and the checkout flow end to end. Place a test order with UPI and with a card, and confirm that the order email arrives and the payment settles. Test every form, every download, and every link in the main menu and footer.
Check SSL: the padlock must show on every page, with no mixed content warnings. Check page speed on the new host and compare it with the old one. Check that images, videos, and fonts load correctly. Then ask one colleague to test it too, because fresh eyes catch what you miss. Only sign off when every test passes.
E-commerce, Payments and Business Functions
WooCommerce stores need extra checks. Pause new orders for the migration window if you can, and warn customers in advance. Test the full checkout with UPI, cards, and net banking, and confirm that stock levels, coupons, and shipping rates carried over correctly. Check that order emails, GST invoices, and SMS notifications still work on the new host.
Test every business function, not just the shop. Contact forms must send to the right inbox. Member logins must work. Scheduled jobs, such as daily backups and subscription renewals, must run on the new server. Webhooks and API connections to your CRM, accounting software, and delivery partners must be re-tested. Our Website Maintenance Plan for Indian Businesses explains the ongoing checks that keep a migrated site healthy after launch.
Migration Day: The Go/No-Go List
On migration day, follow a written sequence and do not skip steps. Confirm the backup is fresh, put the site in maintenance mode if needed, migrate files and database, update the DNS records, and wait for propagation. Then run the live tests again: home page, key pages, forms, checkout, email, and SSL.
Use a go/no-go list before you declare the migration done. Go only if the home page loads fast, the top 20 pages return 200 status codes, forms and checkout work, email sends and receives, SSL is valid, and Search Console shows the new sitemap. If any item fails, pause and fix it. Do not declare success while a test is still red.
The Rollback Plan: What to Do If It Goes Wrong
Every migration needs a written rollback plan before it starts. Decide in advance what counts as a failure: more than 30 minutes of downtime, checkout broken, or email down. If that happens, point the DNS back to the old host, restore the old site from the backup, and tell customers honestly what happened and when it will be fixed.
Keep the old hosting account active for 30 days and do not cancel it on migration day. Keep the backup for 90 days. Write down who does what during a rollback, and who has the passwords. A plan you wrote before the crisis is worth ten times a plan you invent during it.
Post-Migration Monitoring: The First 30 Days
The work is not over on launch day. Monitor both servers’ logs for the first week, and watch Search Console daily for crawl errors, indexation drops, and redirect problems. Check rankings for your 20 most important keywords weekly, and compare organic traffic with the same period before the migration.
Check that the new sitemap is indexed, that old URLs redirect correctly, and that no staging URLs leaked into Google’s index. Test the site speed weekly for a month, and fix any new errors the moment they appear. After 30 days of stable traffic and no errors, you can safely cancel the old hosting. A migration is only finished when a month has passed with no problems.
Costs and Timelines in India
Costs depend on site size and who does the work. A DIY migration costs mainly your time, plus any plugin licences. A freelancer in India typically charges Rs 5,000 to Rs 25,000 for a small site and Rs 25,000 to Rs 75,000 for a store or a large site. An agency usually charges Rs 25,000 to Rs 1,50,000, depending on complexity, with extra charges for redesigns and platform changes.
Timelines follow site size: a brochure site takes 2 to 4 days, a blog or medium site takes 3 to 7 days, and a WooCommerce store or a site with 500 plus pages takes 1 to 2 weeks. Add a week if the domain is also changing, because DNS, email, and Search Console steps all take longer. Our breakdown of How Much Does a Website Cost in India in 2026 helps you budget for the wider project, not just the move.

Common Migration Mistakes and Their Fixes
- Forgetting MX records, so email stops. Fix: export all DNS records before the move and test email before and after.
- Redirecting everything to the home page. Fix: build a full redirect map from a crawl of the old site.
- Leaving staging blocks live, such as noindex or password protection. Fix: check robots.txt and meta tags on launch day.
- Not lowering TTL before the move, so the switch takes hours. Fix: set TTL to 300 seconds 48 hours early.
- Cancelling old hosting on migration day. Fix: keep it active for 30 days.
- Forgetting payment gateways, SMS, and UPI connections. Fix: list every integration in the inventory and test each one.
- Skipping the backup test. Fix: restore the backup to a staging site before you trust it.
- Migrating and redesigning at the same time without a plan. Fix: migrate first, redesign second, or budget double the time.
FAQ
How long does a website migration take in India?
A small brochure site takes 2 to 4 days. A blog or medium site takes 3 to 7 days. A WooCommerce store or a site with 500 plus pages takes 1 to 2 weeks. Add a week if the domain is also changing.
Will a website migration hurt my Google rankings?
It can, but it should not if you follow the checklist. Keep every URL with a 301 redirect, update the sitemap and Search Console, and monitor rankings for 30 days. Most ranking drops after a migration come from missing redirects or staging blocks left live, and both are preventable.
How much does website migration cost in India?
A freelancer typically charges Rs 5,000 to Rs 25,000 for a small site and Rs 25,000 to Rs 75,000 for a store or large site. An agency usually charges Rs 25,000 to Rs 1,50,000. DIY costs mainly your time plus any plugin licences.
Should I change my domain and host at the same time?
Avoid it if you can. Change one thing at a time so you can tell which change caused any problem. If you must do both, budget double the time and test twice as carefully.
When should I cancel my old hosting?
Keep the old hosting active for at least 30 days after a successful migration, and keep the backup for 90 days. Cancel only after a month of stable traffic, no crawl errors, and no customer complaints.
What is the biggest website migration mistake?
Forgetting email. Most migrations focus on the website and forget MX, SPF, DKIM, and DMARC records, so email stops or lands in spam. Export every DNS record before the move and test email sending and receiving on the new host before you switch.
Conclusion
A website migration succeeds when it is boring: nothing breaks, rankings hold, email keeps working, and customers notice nothing. That result comes from the checklist, not from luck. Plan two weeks ahead, inventory every integration, back up and test the backup, lower TTL early, copy every DNS and email record, protect SEO with a full redirect map, test the new site like a customer, and keep a written rollback plan ready. Monitor for 30 days after launch before you cancel the old host. Follow these steps, and your next migration will be the uneventful kind.
