The biggest fear we hear from business owners considering a new website is not cost. It is loss. "We finally rank for a few things. What if we move and it all disappears?" That fear is reasonable - badly handled migrations do destroy traffic. But a well-planned migration can do the opposite.
Three of our projects started on platforms that had stopped serving the business. Romex Pest Control and NRF2.com were on WordPress. Humless was on a static HTML site. All three moved to living websites and came out ahead. This playbook is the process behind those moves. If you are still deciding whether to migrate at all, read Static Website vs. Living Website first.
Signs It Is Time to Leave WordPress (or Your Current Platform)
WordPress powers a huge share of the web and can work well in the right hands. The problem for most small businesses is not WordPress itself - it is what years of plugins, themes, and patchwork edits turn it into. Common warning signs:
- Plugin sprawl. Dozens of plugins, some abandoned, each a potential security or speed problem
- Fear of updating. Nobody wants to click "update" because something always breaks
- Slow pages. Heavy themes and page builders that fail Core Web Vitals on mobile
- Content bottlenecks. Publishing requires a developer or a lot of manual formatting
- No connection to the business. The site does not talk to your CRM, scheduling, or field software
- Dated content that nobody has time to fix
NRF2.com's founder put it bluntly: "We were embarrassed by the dated content on the old site." That feeling is a signal, not a cosmetic issue.
Phase 1: Inventory Everything Worth Keeping
Before anything is designed, document what the current site has earned:
- Every indexed URL. Pull them from your sitemap and from Google Search Console's page indexing report.
- Pages with traffic or rankings. Export 12-16 months of performance data from Search Console. Our Search Console playbook shows how.
- Pages with backlinks. These carry authority you do not want to lose.
- Pages that convert. Which pages produce calls, forms, or sales?
- Assets. Images, PDFs, videos, testimonials, and downloadable resources.
The output is a migration map: a spreadsheet listing every old URL and what will happen to it.
Phase 2: Decide Keep, Improve, Merge, or Retire
Not every old page deserves to come along. For each URL, choose one action:
- Keep: Strong page, same URL if possible, refreshed design
- Improve: Right topic, weak content - rewrite and expand
- Merge: Several thin pages on the same topic become one strong page
- Retire: Outdated, irrelevant, or duplicate - redirect to the closest useful page
Merging is often where the biggest gains hide. A cluster of thin posts competing with each other becomes a single authoritative resource - the same logic behind our content cluster strategy.
Phase 3: Build the Living Foundation
This is where a migration becomes more than a redesign. The new site should be built with the five living website traits from day one (see What Is a Living Website?):
- A fast, mobile-first architecture with clean URLs and schema markup
- A CMS your team can actually use - Humless now handles 100% of its own updates
- A content engine ready to publish from week one
- Guided lead capture designed for how your customers decide
- Integrations with the systems that run your business
For Romex, the build included a FieldRoutes integration and a full business intelligence portal, so the website became connected to operations instead of sitting beside them. For NRF2.com, it included live research feeds that keep the science hub current automatically.
Phase 4: Redirects, Structure, and Technical Checks
This is the phase that protects your rankings. Do not skip any of it:
- 301 redirects from every old URL that changes to its new equivalent - one-to-one, not everything to the homepage
- Preserve titles and headings on pages that rank, improving them carefully rather than replacing them wholesale
- Rebuild internal links so authority flows to your most important pages - see our internal linking strategy
- Add structured data for your business, services, FAQs, and articles - our schema implementation guide covers the essentials
- Generate a fresh XML sitemap and a clean robots configuration
- Test on a staging site: crawl it, check every redirect, and test forms end to end
Phase 5: Launch Week
Launch is a process, not a button:
- Launch early in the week, not before a weekend
- Submit the new sitemap in Search Console
- Crawl the live site immediately and fix any broken links or redirect chains
- Submit test leads through every form, quiz, and booking flow
- Confirm analytics and conversion tracking are firing
- Update your Google Business Profile and key directory listings if any URLs changed
Phase 6: The First 90 Days
A brief ranking wobble after migration is normal while search engines re-crawl. What separates a good migration from a great one is what you do next. A static rebuild would stop here. A living website starts publishing.
That is why our migration results tend to accelerate rather than merely recover. Romex tripled lead volume in month one, then hit +232% month-over-month impression growth by month two as the content engine ramped up - and spring revenue reached summer levels for the first time in company history.
com saw a 200% increase in eBook subscriptions, 3x content velocity, 60% faster load times, and a 45% drop in bounce rate. Humless went from near-zero visibility to 6,000+ monthly impressions and 200+ monthly clicks.
Track progress with a simple scorecard - we lay one out in How to Measure a Living Website.
The rule I give every business considering a migration: protect what already earns trust. Pages that rank, links people have shared, and reviews customers left years ago are all assets.
Move them carefully, redirect everything, and improve from there. Never start from zero just because the platform is new.
Migration Mistakes That Cost Traffic
- Redirecting everything to the homepage. Search engines treat this like the old page disappeared.
- Changing every URL for no reason. If a URL ranks and makes sense, keep it.
- Dropping content to "simplify." Shorter is not better if the old page answered real questions.
- Launching without tracking. You cannot prove the migration worked if you cannot measure before and after.
- Treating launch as the finish line. The site begins working the day it launches - the publishing plan should already be scheduled.
A Migration Timeline at a Glance
| Stage | Typical focus | Who is involved |
|---|---|---|
| Inventory and audit | Crawl the old site, export Search Console data, list every page with traffic or links | Strategist |
| Content decisions | Mark each page keep, improve, merge, or retire | Strategist and owner |
| Build | New design, AI CMS, schema, integrations, conversion paths | Build team |
| Redirect mapping | One-to-one 301 redirects for every changed URL | Technical lead |
| Launch | DNS switch, sitemap submission, redirect testing, tracking checks | Technical lead and owner |
| Stabilization | Daily then weekly checks of coverage, rankings, and leads | Strategist |
What to Do If Traffic Dips After Migration
A small, short-lived wobble after a migration is common while search engines recrawl the new site. A sustained drop is not normal and usually has a specific cause. Work through these checks in order:
- Redirects: confirm every old URL with traffic returns a single 301 to the right new page, not a 404 or a chain of redirects.
- Indexing: check Search Console coverage for pages that are excluded, blocked by robots rules, or marked noindex by mistake.
- Content parity: make sure important pages did not lose the content that made them rank. Thinner pages often rank lower.
- Internal links: confirm that navigation and in-content links point to the new URLs. Our internal linking guide covers the structure.
- Speed and Core Web Vitals: a slower site can lose ground. See our Core Web Vitals guide.
Migration FAQ
Will I lose my rankings if I leave WordPress?
Not if the migration is done carefully. Rankings belong to your content, URLs, and domain, not to WordPress. Preserve what ranks, redirect what moves, and keep publishing.
Can I keep my blog posts?
Yes. Posts with traffic or links should move over, ideally improved along the way. Thin or outdated posts can be merged or retired with redirects.
How much of my time does a migration take?
Most of the owner's time goes into the content decisions and final review. The technical work - crawling, redirect mapping, and testing - is handled by the build team.
Should I migrate during my busy season?
Avoid it if you can. Even a well-run migration needs a few weeks of close monitoring while search engines recrawl the site. Launching in a slower period gives you room to fix any redirect or indexing issues before demand peaks, so the new site is settled and climbing by the time customers start searching in volume.
The Bottom Line
A migration is the one moment when you can fix years of accumulated problems in one move - but only if it is planned around what the old site earned and what the new one needs to do. Done well, it is not a reset. It is a launchpad.
Thinking about moving off WordPress or a dated site? Learn how we build Living Websites, or start with a free AI Readiness Audit to see what your current site is worth protecting.
