How to do a website migration?

When business owners imagine a website migration going wrong, they picture corrupted files or a broken database. In reality, the transfer itself is rarely the problem — the danger lives in the window when traffic shifts from the old server to the new one.

According to Pantheon's WordPress migration guide, the greatest risk isn't moving files or importing a database — it's the DNS propagation window, when visitors are routed between servers and sequencing matters most. Get that window wrong, and customers hit error pages while your site technically "exists" in two places.

The fix is preparation, not speed. Pantheon's guidance is blunt: zero downtime is achieved by how you prepare, and the order of steps matters — especially the first one. Lower your DNS TTL (time to live) to 300 seconds at least 24–48 hours before the move, so that when you're ready to switch, traffic redirects to the new server in minutes instead of hours.

That's also where most DIY attempts fall apart. The migration itself might take a small-site owner one to three hours, but the preparation discipline — DNS timing, cache strategy, rollback planning — is what separates a smooth cutover from a costly one. Pantheon notes that managed or professional migration services exist precisely for situations involving complexity, large databases, or downtime that costs revenue.

The same preparation logic extends to what happens after launch:

• Flush permalinks and clear every cache layer so the new server serves fresh, correct pages
• Test transactional emails and cron jobs — the invisible machinery that often breaks silently
• Keep the old host active for 7–14 days as a rollback safety net
• Manage new data carefully during that window to avoid split data if you need to roll back

There's a lesson here from the data-migration world, too. At Datafold, a validated process of automated translation, automated validation, and human review of outliers is endorsed by data engineers as the recommended way to run any migration — because it's faster, more accurate, and eliminates many sources of human error where mistakes matter most.

This is why preparation-heavy migrations are often better handled by a team that does them routinely. At AI Business Sites, migrations and rebuilds are managed end-to-end for clients — and because clients own their code, content, data, and domain outright, there's no lock-in on either side of the move. If you'd rather not learn DNS TTL timing by trial and error, a free strategy call is a good place to start the conversation.

Not all website migrations are created equal. The path you choose depends on your site's complexity, your technical comfort level, and how much downtime your business can afford.

According to Pantheon's migration guide, there are three primary approaches: plugin-based tools for straightforward sites, manual migration for full control, and managed services for complex environments. Each carries different risks and requirements.

Plugin-based migration works well for simple WordPress sites with standard configurations. These tools automate the transfer of files and databases, making them accessible to non-technical users. However, they struggle with large databases, multisite installations, or custom server configurations.

Manual migration gives you complete control over every step. You export your database, transfer files via FTP, update configuration files, and handle DNS changes yourself. This approach typically takes 1–3 hours for small sites, but significantly longer for larger or more complex setups, according to migration experts. It requires comfort with database management, file transfer protocols, and server settings.

Managed or professional migration makes sense when you're dealing with complexity — multisite networks, large databases, e-commerce functionality, or situations where downtime directly impacts revenue. Professional services handle the technical heavy lifting while you focus on running your business.

Here's what each path requires:

• Plugin tools: Install, configure, run — best for basic sites under a few gigabytes
• Manual process: Database export, file transfer, DNS updates, URL replacement, testing
• Managed service: Hand off credentials, approve the plan, review before launch

The research is clear on one point: business owners without technical expertise should avoid DIY migration methods. The risks are too high. A single mistake during DNS cutover can take your site offline for hours. A botched database import can corrupt customer data. An overlooked 301 redirect can tank your search rankings.

This is exactly why AI Business Sites handles migration as part of our done-for-you service. We manage the entire process — from lowering your DNS TTL 24–48 hours before the move to keeping your old host active for 7–14 days as a safety net, following the industry-standard preparation steps that prevent downtime.

You shouldn't need to understand serialized data, DNS propagation windows, or rollback procedures to move your website safely. That's our job. Yours is running your business.

After the migration goes live, the work isn't done—validation is critical to protect your site and SEO. This phase ensures everything functions correctly and prevents ranking drops from broken links or indexing issues.

Start by flushing permalinks in your CMS to reset URL structures and clear all cache layers—including server, plugin, and CDN caches—to serve fresh content. Test transactional emails (like order confirmations) and cron jobs (scheduled tasks) to confirm automations still trigger correctly. These steps catch silent failures that could disrupt user experience or backend processes.

Next, implement 301 redirects for any changed URLs to preserve link equity and guide users and search engines to the correct pages. If you’ve moved domains, submit a "Change of Address" request in Google Search Console to help Google update its index efficiently. Finally, keep the old host active for 7–14 days as a rollback safety net while monitoring for issues, as research shows this window is essential for recovery if problems arise post-migration. Pantheon’s migration guide emphasizes that these validation steps are not optional—they’re how you avoid the most common post-migration pitfalls. For AI Business Sites clients, this process is managed end-to-end, but understanding these steps highlights the technical care behind a seamless transition.