WordPress Migration: STL’s Checklist for Zero Downtime
Moving a live site is high stakes. Downtime means lost revenue, frustrated users, and SEO setbacks. At STL Website Development, we follow a disciplined, engineering-first playbook to execute a wordpress migration with zero interruption to your customers. Below is our proven checklist—from discovery to cutover to post-launch QA—that minimizes risk and preserves performance, data integrity, and search visibility.
Our approach to zero-downtime wordpress migration
Every site is different, but the goal is the same: predictable execution and clean handoff. We start with discovery and a rollback-ready plan, then migrate on a fully synced staging environment. Next, we run a timed cutover window with DNS controls that limit propagation delays. Finally, we harden the new stack and verify everything from payments to pixel fires.
Highlights of our approach:
- Plan with specificity: roles, tools, timelines, rollback.
- Clone everything: database, uploads, media, custom code, and server rules.
- Freeze content during cutover to avoid data conflicts.
- Validate SEO, forms, tracking, payments, and caching on staging.
- Switch DNS with low TTLs and live monitoring.
This process protects user sessions, orders, and lead submissions while keeping your brand online and trusted.
Technical checklist for wordpress migration
Use this as a preflight before any move:
- Hosting and PHP parity: Match PHP versions, web server type (Nginx/Apache), MySQL/MariaDB, and OS-level libraries. Document differences that could affect plugins or media handling.
- Inventory the stack: Theme(s), child themes, plugins (versions and licensing), MU-plugins, object/page caching, CDN, WAF, and cron jobs.
- Backups and snapshots: Offsite backups of files and database, plus provider-level snapshots where available. Test a restore to confirm integrity.
- Staging environment: Private, blocked from indexing, mirroring production paths and salts. Sync production data into staging immediately before go-live rehearsal.
- URLs and environment variables: Confirm home/site URLs, wp-config, salts, memory limits, upload limits, and any environment keys.
- Media and file paths: Verify uploads path, custom directories, and case sensitivity issues (especially moving between Windows/Linux).
- Database collation/charset: Standardize to utf8mb4 and consistent collations to avoid broken characters or sorting anomalies.
- SSL/TLS and redirects: Pre-install certificates and configure 301 rules. Plan canonical HTTPS and www/non-www behavior.
- Performance layer: Replicate caching (page, object, opcode), purge strategies, and CDN behaviors. Document cache key rules for logged-in users and eCommerce.
- Email and SMTP: Migrate SMTP credentials or transactional email providers; test password resets, form notifications, and order emails.
- Cron tasks: Move wp-cron to real cron if needed; catalog schedules for backups, feeds, and subscriptions.
- Search indexing guardrails: Keep staging noindexed; prep robots.txt and meta directives for production only.
- TTL strategy: Lower DNS TTLs 24–48 hours pre-cutover to reduce global caching and enable a fast switch.
- Observability: Enable server logs, PHP error logs, access logs, uptime monitoring, and analytics annotations for the move window.
For foundational references, see WordPress’s official Moving WordPress guide and Google’s Site Moves documentation:
- https://wordpress.org/support/article/moving-wordpress/
- https://developers.google.com/search/docs/advanced/crawling/site-moves
Build a staging copy the right way
A flawless migration is rehearsed, not improvised. We clone production to staging, scrub secrets, and disable indexing. Then we validate:
- Theme and plugin compatibility against the target PHP/database versions.
- Custom post types, taxonomies, and permalink structures.
- Media rendering, image sizes, and any WebP/AVIF conversions.
- Search and replace for domain references in serialized data.
- Critical UX flows: checkout, account creation, lead forms, and gated content.
During this stage, we also run on page seo checks: titles, meta descriptions, canonicals, open graph, XML sitemaps, robots.txt, and hreflang where applicable.
Content freeze and editorial coordination
We coordinate a content freeze window before cutover. For high-velocity sites, we implement selective write-blocking or delta-sync strategies to capture last-minute orders, comments, or posts. Editorial teams receive a precise timeline, so there are no surprises.
DNS switch and cutover without disruption
When staging is signed off, we execute a timed cutover:
Pre-cutover
Confirm backups and rollback points.
Lower TTLs are already in place; verify via DNS queries.
Warm caches and prebuild critical pages.
Put a brief maintenance banner in place only if absolutely necessary for logged-in admins, not public users.
Cutover
Sync final database and uploads delta.
Update site URLs, flush permalinks, and clear all caches.
Switch DNS A/AAAA/CNAME to the new origin; monitor propagation and error logs in real time.
Post-cutover
Validate transactions end-to-end, including payment gateways and webhooks.
Spot-check key geographies and ISPs for propagation.
Restore normal TTLs.
We keep monitoring and support on standby during the entire window to ensure the wordpress migration is invisible to users.
Go-live runbook and verification
Our runbook includes:
- Form submissions, emails, and CRM integrations
- Search, filtering, and pagination
- 404s and redirects, including legacy paths
- Analytics tags, pixels, and conversions
- Accessibility spot checks for critical templates
Post-migration QA and on page SEO validation
Right after launch, we perform:
- Crawl and redirect audits: Validate 301 maps, detect soft 404s, and ensure canonical chains are clean.
- XML sitemap submission and Search Console checks: Resubmit sitemaps, verify coverage, and monitor for spikes in crawl errors.
- Performance tuning: Verify TTFB, LCP, CLS, and core caching behavior. Re-run image optimization and preconnect/preload hints as needed.
- Security hardening: Enforce HTTPS, headers (HSTS, CSP where applicable), and apply least-privilege credentials.
- Content parity: Compare counts of posts, products, media, and taxonomies between old and new.
- CDN and WAF rules: Confirm cache hit ratios and threat protection without false positives.
We also re-check structured data, internal linking, and schema to ensure continuity in rich results. If needed, we align copy and headings with an updated on page seo strategy to capture quick-win improvements post-move.
What we move—and what we improve
A migration is a chance to modernize. If your stack needs a refresh, our team can pair the move with:
- Architecture updates and custom functionality as part of our custom website development services: https://stlwebsitedevelopment.com/website-development/
- Proactive care with our ongoing website maintenance plans: https://stlwebsitedevelopment.com/website-maintenance/
- A refreshed brand system through professional logo design: https://stlwebsitedevelopment.com/logo-design/
- Higher-converting messaging via our conversion-focused copywriting services: https://stlwebsitedevelopment.com/copywriting/
FAQ: Your wordpress migration questions answered
How long does a wordpress migration take?
Simple sites can move in a day with prep; complex eCommerce or multilingual installs often require 1–2 weeks of planning and rehearsal. We schedule cutover during your lowest-traffic window to minimize risk.
Will my SEO rankings drop during migration?
When redirects, canonicals, and sitemaps are correct, rankings typically hold steady. We monitor Search Console closely and fix any crawl issues immediately to preserve visibility.
Can you migrate WooCommerce without downtime?
Yes. We implement a content/order freeze or a delta-sync for orders and customers, then perform a narrow cutover window to ensure no data loss.
Do you support moving from other builders into WordPress?
Absolutely. We rebuild templates, import content, map redirects, and carry over tracking and integrations as part of a comprehensive plan.
What if something goes wrong?
We maintain tested rollback points, so we can revert swiftly while we investigate. Our change log and runbook make troubleshooting fast and transparent.
Ready for a zero-downtime move?
A safe, seamless wordpress migration comes down to planning, rehearsal, and disciplined execution. If you’re preparing to move servers, hosts, or platforms, our team is ready to lead the process end-to-end. Contact STL Website Development to schedule a discovery call and get a tailored migration plan that keeps your site online, fast, and secure.
