Website Migration Readiness Scorecard for SMEs

Changing website hosting looks simple from the outside. Point the domain to a new server, upload the files, install SSL, and move on. In real business websites, the risk is usually hidden in the connected parts: email, DNS records, redirects, forms, login pages, payment links, analytics, Search Console, old URLs, and the person responsible for watching the site after the move. That is why a migration should start with a readiness score, not with a DNS change. This scorecard is built for SMEs in India, the Gulf, and global service markets that want to move a website, rebuild a site, change hosting, or shift from an old agency/server to a cleaner setup without breaking leads, email, or search visibility. ## Quick Answer A website is migration-ready when the current setup is documented, backups are restore-tested, DNS and email records are mapped, the new site is tested privately, SSL works, important URLs are redirected, forms and checkout are tested, and someone monitors the site after launch. If the readiness score is under `17/20`, fix the gaps before moving live traffic. ## Why SME Website Migrations Fail Most failed migrations do not fail because hosting is impossible. They fail because the migration owner only moves the visible website. The hidden dependencies stay behind: - email MX records; - SPF, DKIM, and DMARC records; - subdomains used for apps, panels, or landing pages; - old campaign URLs; - payment success and failure URLs; - contact forms and SMTP settings; - Google Search Console and sitemap signals; - SSL certificate coverage; - CDN or proxy settings; - old WordPress uploads, media, and redirects. For a business owner, the damage is practical. Leads stop arriving. Email bounces. Ads point to a broken page. WhatsApp buttons work but form notifications do not. Google may crawl redirect mistakes. Staff lose confidence in the new site even if the homepage looks fine. ## The 20-Point Migration Readiness Score Use this before touching live DNS. Give each item: - `0` if unknown; - `1` if partly checked; - `2` if verified and documented. ### 1. Ownership and Access You should know who controls the domain registrar, DNS host, website hosting, email provider, SSL, CDN/proxy, CMS/admin, payment gateway, analytics, tag manager, and Search Console. If the current agency, developer, or old vendor controls these accounts, do not start migration until ownership is clear. ### 2. Backup and Restore A backup is not enough. A restore-tested backup is safer. Confirm that website files, database, uploads/media, environment/config files, theme, plugin, and CMS settings are included. For WordPress, check database, uploads, plugins, theme, permalink settings, and custom code. ### 3. DNS Record Inventory List all important DNS records before any cutover: - A and AAAA records; - CNAME records; - MX records; - SPF, DKIM, and DMARC; - TXT verification records; - subdomains; - CDN/proxy records; - old app or landing page records. Email breaks often because MX and authentication records are missed during a website-only migration. ### 4. Email Routing Plan Decide whether email stays where it is or moves separately. If email stays, DNS changes must preserve MX, SPF, DKIM, DMARC, and verification records. If email moves, plan old mailbox access, new mailbox testing, aliases, forwarders, and authentication before changing MX. ### 5. Staging or Preview Test Do not discover broken pages after DNS is live. Test a staging or preview copy for homepage, service pages, contact forms, checkout/payment paths, login areas, support links, WhatsApp links, mobile layout, speed, redirects, and SSL. ### 6. SSL and Mixed Content The new host should support SSL before public launch. Check that `https://` loads correctly, images/scripts/styles do not cause mixed-content warnings, and key subdomains are covered if they are part of the move. ### 7. Redirect Map If URLs are changing, prepare redirects before launch. Map old important URLs to their new destination. Prioritize pages with traffic, backlinks, campaigns, local listings, ads, email links, and internal links. ### 8. SEO and Search Console Checks After launch, review: - sitemap; - robots.txt; - canonical tags; - redirect behavior; - indexable pages; - analytics; - Search Console coverage; - important landing pages. For domain moves, Search Console change-of-address steps may be relevant after the move and redirect setup are complete. ### 9. Forms, Leads, and Payments Test the parts that make money or create support work: - contact forms; - quote requests; - booking links; - WhatsApp links; - click-to-call; - checkout; - payment success/failure pages; - login and password reset; - support/ticket forms; - CRM or email notifications. ### 10. Monitoring and Rollback A migration is not finished when the homepage loads. Assign a person to monitor the first 24-72 hours. Watch uptime, forms, email, DNS propagation, Search Console, analytics, redirects, support tickets, and customer complaints. Keep a rollback path ready if a critical issue appears. ## Score Bands - `17-20`: Ready for a controlled migration. - `12-16`: Almost ready; fix weak areas before DNS cutover. - `0-11`: High risk; do not migrate live traffic yet. ## When to Delay a Migration Delay the migration if: - nobody knows who controls DNS; - email records are unclear; - no restore-tested backup exists; - the new site has not been tested privately; - key URLs do not have redirects; - contact forms or checkout are untested; - SSL is not ready; - no one is assigned to monitor after launch. Rushing these gaps usually costs more than waiting. ## How Hostao Can Help Hostao can help SMEs plan website hosting, WordPress hosting, domains, SSL, business email, DNS checks, and practical migration support. If you are planning to move a business website, use the readiness scorecard first. If the score is weak, fix the risky parts before changing live traffic. CTA: Book a Hostao migration review at `https://meet.hostao.com`.