WordPress migration without the downtime and broken links

WordPress migrations that don’t lose traffic, links, or rankings, scoped from a paid 60-minute migration plan. If you are moving WordPress between hosts, replatforming off Drupal, Wix, Squarespace, or static HTML onto WordPress, or restructuring URLs on a site that already ranks, the cost of doing it badly is months of recovery. The cost of doing it well is a real plan, written down, with the redirect map already built before anyone touches DNS.

WordPress since 2007 · custom post types, REST endpoints, Gutenberg blocks, WP-CLI, and site-specific plugin architecture · 20+ plugins published on WordPress.org · Fort Erie, Ontario

Book a 20-minute discovery call Ask a question first

The problem you’re sitting in

Migrations are where WordPress projects most often go publicly wrong. The site moves, traffic drops 40 percent, the redirect map missed a thousand legacy URLs, the email forms break for two days, and the executive sponsor who approved the budget is now in a meeting asking why.

The cost of planning vs. Reacting This diagram contrasts two approaches to WordPress migration: one where planning is neglected and problems are addressed reactively, leading to traffic drops and technical issues; and another where proactive planning, including a complete URL inventory, pre-launch redirect mapping, canonical URL audits, and indexation monitoring, results in a smoother transition. The emphasis highlights the importance of building the redirect map before DNS changes. MIGRATION SUCCESS The cost of planning vs. Reacting A migration plan delivers predictable outcomes Doing it badly Incomplete, reactive work Doing it well Proactive, planned work URL inventory Incomplete URL inventory Complete URL inventory built beforehand Redirect rules Redirect rules written after launch Redirect map built before DNS change Canonical-url audit No canonical-url audit on the new site Canonical-url audit on the new site completed Indexation monitoring No monitoring of indexation in the weeks after cutover Monitoring of indexation in the weeks after cutover
I lay out the difference between building a redirect map proactively versus reacting to broken links after launch.

The work is not hard if you have done it before. It is brutal if you have not. The failure modes are the same every time: incomplete URL inventory, redirect rules written after launch instead of before, no canonical-URL audit on the new site, and no monitoring of indexation in the weeks after cutover.

What I do

  • Host-to-host WordPress migrations. Off shared hosting onto a real platform, between managed hosts, or onto your own infrastructure. With staged cutover and DNS plan.
  • Platform-to-WordPress migrations. Drupal, Joomla, Wix, Squarespace, Webflow, Ghost, static HTML, custom CMS exports. Content modeling, taxonomy mapping, redirect maps, media migration.
  • Multisite consolidations. Pulling separate WordPress installs into a multisite network, or splitting a multisite back into independent installs. Both directions, both with their own pitfalls.
  • Domain and URL restructures. Domain changes, subdomain-to-subdirectory moves, taxonomy slug changes, permalink-structure changes on sites that already rank. Each of these has a redirect-map shape that is non-negotiable; the question is whether you build it before launch or after.

How an engagement starts

Most migration engagements start with a paid 60-minute Migration Plan call. You bring the source environment details, the destination, the constraints, and the deadline. I bring the question list and a written plan that lands in your inbox the same day: scope, risks, redirect-map approach, cutover timing, monitoring window, and a fixed-fee quote for the migration itself.

If the plan call surfaces that the migration is simpler than you thought and you can run it in-house, I will tell you that on the call. The plan is the deliverable; the build is a separate decision.

What this is not

  • Not a content rewrite. Migration moves your content; it does not rewrite it. If you want a content overhaul, do it before or after, not during.
  • Not a redesign. If you are migrating and redesigning at the same time, that is two projects pretending to be one, and I will recommend sequencing them.
  • Not ongoing hosting. I do not resell hosting. I will recommend hosts I trust and help you set up the relationship directly.
  • Not “migrate by tomorrow.” Real migrations need a real timeline. Emergency cutovers exist; they are priced accordingly.

Who this is for

  • Fit. Sites with real organic traffic where losing it would hurt the business.
  • Fit. Teams replatforming onto WordPress from a CMS they have outgrown, or off WordPress hosting that has stopped fitting.
  • Fit. Organizations consolidating multiple sites into one, or splitting a single site into properly-separated properties.
  • Not fit. Brand-new sites with no traffic to preserve. The plan and discipline are overkill at that scale.
  • Not fit. Buyers who want a “click this button to migrate” plugin recommendation. Those plugins exist. They handle the easy 80 percent. The remaining 20 is the part that breaks the project.

Why work with me on this specifically

  • Prior portfolio work for one of Canada’s largest news networks during the 2011–2012 platform migration. Eleven newspaper mastheads, real legacy URL inventories, real redirect maps, real consequences for getting it wrong.
  • WordPress development since 2007. Migrations have been part of the work the entire time, on every scale from one-person blogs to multisite networks.
  • SEO discipline integrated into the migration plan, not bolted on after launch. Redirect-map shape, canonical-URL audit, and indexation monitoring are part of the engagement, not separate consulting.
  • Independent client work, off the day-job hours at Sherwin-Williams.

When you are ready

If you have a migration on the calendar and you want a senior set of eyes on the plan before the cutover, the 20-minute call is the lowest-friction way to start.

Book a 20-minute discovery call Ask a question first

Tell me about your project

The fastest way to a straight answer. Tell me what you need and I will reply within a business day, honestly, even when the answer is that I am not the right fit.

Prefer to talk? Call 647-641-0643

Share Your Project Details

Use this form for project scope, technical SEO support, onsite training requests, or a focused next-step conversation.

Required fields.

Include your goals, team size, current blockers, and any launch or training date you have in mind.