Agency7's full architectural guide — from AI lead generation to autonomous financial operations.
Migrating Off WordPress: When and How for Edmonton Businesses in 2026
WordPress still runs roughly 40% of the web, including thousands of Edmonton business sites. Most of them should stay on WordPress. Some should leave. The question is how to know which you are — and if you're in the "should leave" camp, how to migrate without destroying the SEO and lead flow you've built.
This post is the honest version: when migration makes sense, when it doesn't, what your options are in 2026, and the specific steps to execute a migration that doesn't torpedo your business.
Should you actually migrate?
Reasons to stay on WordPress
- Your site is well-maintained and performs adequately (PageSpeed mobile score > 60)
- You have a content team that's WordPress-fluent
- You rely on specific plugins with no equivalent elsewhere (WooCommerce, BuddyPress, LearnDash, etc.)
- Your developer or agency specializes in WordPress
- Migration cost exceeds realistic ROI from better performance
For most Edmonton SMBs in this bucket, migration is a distraction. Invest in optimization instead.
Reasons to migrate
- Performance is broken (PageSpeed mobile score < 40, LCP > 4s on mobile)
- Plugin dependency has created instability or security issues
- You've had to rebuild 2+ times in the last 5 years
- AI-discoverability is important and WordPress is blocking it
- You've hit a performance ceiling and content/marketing is the bottleneck
- You're growing past WordPress's comfort zone (multi-location, complex integrations, scale)
- Total cost of ownership is ballooning (plugin subscriptions + maintenance + rebuilds)
What migration actually costs
Case 1: WordPress to another WordPress (optimized)
Lighter lift. Migrate to a clean WordPress install with better hosting, lightweight theme, minimal plugins.
- Cost: CA $2,500-$8,000
- Timeline: 3-6 weeks
- Risk: low (same platform, same concepts)
- Outcome: 20-40% performance improvement, better maintainability
Good choice if WordPress is fine conceptually but your current install is a mess.
Case 2: WordPress to Webflow
Moderate lift. Webflow requires rebuilding visually, content can be migrated.
- Cost: CA $6,000-$18,000
- Timeline: 6-12 weeks
- Risk: low-medium (different platform, different CMS model)
- Outcome: 40-60% performance improvement, visual-editing workflow
Good choice if you want designer-friendly editing and design-forward output without going fully custom.
Case 3: WordPress to Next.js / Astro
Largest lift. Full custom rebuild.
- Cost: CA $10,000-$40,000
- Timeline: 8-16 weeks
- Risk: medium-high (dramatically different platform)
- Outcome: 60-90% performance improvement, best AI-discoverability, longest-lived asset
Good choice if web performance is load-bearing for your business and long-term total cost of ownership matters.
Case 4: WordPress to Shopify (for e-commerce)
Mid-size lift.
- Cost: CA $5,000-$25,000
- Timeline: 6-16 weeks depending on catalog size
- Risk: medium (e-commerce complexity, payment transitions)
- Outcome: dramatically better e-commerce UX, purpose-built infrastructure
Only relevant if you're running WooCommerce and your e-commerce needs justify the switch.
What can break
SEO
Biggest concern for most Edmonton businesses. Specific risks:
- URL changes break rankings if redirects aren't perfect
- Schema markup lost if not recreated
- Page speed changes (usually improves but can regress if done poorly)
- Internal link structure disrupted
- Image URLs change, breaking external links
Mitigation: 1:1 URL mapping, comprehensive 301 redirects, post-launch monitoring via Google Search Console.
Content
- Formatting inconsistencies (WordPress's WYSIWYG vs. other platforms' content models)
- Images that don't transfer cleanly
- Embedded media (YouTube, forms, etc.) needing reconfiguration
- Custom fields / structured data on custom post types
Mitigation: content audit before migration, testing of each content type, staging environment.
Functionality
- Plugin-provided features not available on new platform
- Custom functionality that needs rebuilding (not just replatforming)
- Integrations with CRMs, email tools, analytics
Mitigation: feature inventory, API evaluation, parallel testing before launch.
Business continuity
- Scheduled downtime during DNS cutover
- Email deliverability disruption if using host-based email
- Forms that stop working during transition
- Search traffic dips during Google re-crawl
Mitigation: launch during low-traffic period, have rollback plan ready, communicate with stakeholders.
Migration phases in detail
Phase 1: Decision and planning (2-4 weeks)
- Audit current WordPress site (pages, URLs, schema, content types, plugins, integrations)
- Define migration scope and target platform
- Build business case (cost vs. expected improvement)
- Set up staging environment on new platform
- Plan URL mapping
- Identify content, features, and data to migrate
Phase 2: Design and build (4-10 weeks depending on platform)
- Rebuild design on new platform
- Implement schema markup (Organization, LocalBusiness, Service, Article, etc.)
- Create
llms.txt - Set up new hosting, CDN, SSL
- Implement redirects from old URLs to new
Phase 3: Content migration (2-6 weeks, often overlapping build)
- Automated migration tools where possible (WordPress XML export → various importers)
- Manual cleanup for custom post types, formatting issues
- Image migration and optimization (WebP/AVIF conversion)
- Verification of each migrated page
Phase 4: Testing (1-3 weeks)
- Internal QA across browsers/devices
- Core Web Vitals testing
- Schema validation
- Form and integration testing
- SEO audit (Screaming Frog, Ahrefs, Sitebulb)
- User acceptance testing
Phase 5: Launch (1 week)
- DNS cutover (ideally Tuesday-Thursday, low traffic time)
- Google Search Console update (sitemap submission, URL inspection on key pages)
- Monitoring for 404s, traffic drops, ranking changes
- Quick-fix team available for 72 hours post-launch
Phase 6: Post-launch stabilization (4-12 weeks)
- Monitor Google Search Console for indexing issues
- Track ranking changes for key queries
- Fix redirect issues as surfaced
- Verify AI engine crawling (GPTBot, ClaudeBot, PerplexityBot in logs)
- Optimize based on real-user metrics (RUM / CrUX data)
The URL mapping challenge
The single most important part of any WordPress migration is URL mapping. Get this wrong and you lose rankings.
Best practice: 1:1 mapping
Every old URL maps to exactly one new URL via 301 redirect. Examples:
/services/plumbing/→/services/plumbing/(same URL preserved)/blog/2023/10/great-post/→/blog/great-post/(date structure removed)/?page_id=42→/about/(ugly query URL → clean URL)
When URL structure changes
Sometimes the new platform has different URL patterns. Change structure in one move:
- Document every old URL with its new URL
- Implement 301 redirects before launch
- Submit new sitemap to Google
- Expect 2-6 weeks of ranking volatility
- Don't change URLs again for 6+ months after migration
Orphan URLs
Old URLs that don't have a clean new equivalent (discontinued services, old campaign pages). Options:
- 301 redirect to the most relevant new page
- 410 Gone (explicit removal signal)
- Never 404 — it's the worst option
Redirect tools
WordPress migration redirects can be implemented at various layers:
.htaccess(if Apache)nginx.conf(if Nginx)next.config.tsredirects (if migrating to Next.js)- Vercel/Netlify redirects (platform-level)
- CDN-level redirects (Cloudflare rules)
Platform-level is usually cleanest.
What to audit on your WordPress site before migrating
Content inventory
- Total pages / posts
- Content by type (pages, blog posts, case studies, services, products, etc.)
- Top 20 pages by traffic (must migrate carefully)
- Pages with significant backlinks (must preserve)
Technical inventory
- All active plugins (which are mission-critical, which aren't)
- Custom code in theme / child theme
- Custom post types / fields
- Forms and integrations
- Analytics setup (GA4, Search Console, etc.)
SEO inventory
- Current ranking keywords
- Schema markup in use (via Yoast, Rank Math, or custom)
- XML sitemap structure
- Robots.txt configuration
- Canonical URL patterns
Media inventory
- Total image count and size
- Image optimization status
- Video / audio files
- Downloads (PDFs, etc.)
Specific migration paths
WordPress → Webflow
- Use WordPress CSV export for content
- Webflow CMS for blog / dynamic content
- Webflow's built-in SEO tools for schema basics (add custom code for full schema)
- Budget extra time for redesigning in Webflow (WP themes don't translate)
WordPress → Next.js
- Use WordPress REST API or WPGraphQL for content pull
- Or: export content to markdown/MDX for static content
- Build pages in React components
- Implement schema as JSON-LD components
- CMS options: headless WordPress (keep WP as CMS), Sanity, Contentful, Strapi, Prismic, or markdown files in git
WordPress → Astro
Similar to Next.js but Astro is optimized for content-heavy sites.
- Great for blogs and marketing sites
- Worse for interactive applications
- Usually the right answer if you're migrating a content site and don't need complex frontend interactivity
WordPress → Shopify (e-commerce)
- Use Shopify migration tools or Cart2Cart
- Manual product data cleanup
- Redirect old WooCommerce URLs to Shopify equivalents
- Budget significantly more time for product catalog migration than page migration
WordPress → another WordPress (optimized)
- Use All-in-One WP Migration or Duplicator
- Clean slate approach: start with new WordPress, migrate content only (not themes/plugins)
- Fresh lightweight theme (GeneratePress, Kadence, Astra)
- Minimum viable plugins (security, backup, SEO, caching)
Realistic outcomes
Success looks like
- 60-90% Core Web Vitals improvement
- Rankings recover within 4-12 weeks
- Maintenance burden meaningfully reduced
- Content editing experience better or comparable
- AI-discoverability significantly improved (schema + llms.txt + clean HTML)
Failure modes
- URL mapping incomplete → rankings crash, never fully recover
- Content migrated poorly → broken pages, bad formatting, lost authority
- New platform doesn't support needed functionality → business continuity issues
- Migration done without strategy → ends up with worse site at higher cost
Most migrations that fail do so for organizational reasons (scope changed mid-project, rushed launch, inadequate testing), not technical reasons.
When NOT to migrate
You just launched your WordPress site in the last 12-18 months
Usually too early. Optimize what you have. Revisit in 2-3 years.
Your traffic is low and flat
Migration cost won't be recovered. Spend the money on marketing and content instead. Revisit if traffic grows.
Your team is deeply WordPress-fluent
Retraining is a hidden cost. If your marketing team lives in WordPress and you'd need to re-train on Webflow or Next.js, factor that in.
Current site is acceptable, just not exciting
"Could be better" isn't a migration trigger. "Actively losing business" is.
You don't have budget for proper migration
Cheap migration = broken migration. Wait until you can do it right.
Frequently asked questions
How long will my rankings take to recover?
4-12 weeks for most pages, if URL mapping is clean. Longer if URLs changed significantly. Plan for 2-3 months of reduced organic traffic during stabilization.
Should I migrate during a seasonal slow period?
Yes. Edmonton trades: migrate in late fall or late winter (between peaks). Edmonton retail: avoid Q4. Edmonton B2B: summer is often quieter.
Can I DIY a migration?
Not really. Content migration can be DIYed. Proper URL mapping + schema + testing is beyond most non-developers. Budget for professional help.
What about paid ads during migration?
Pause or reduce during the first 2 weeks post-migration. Landing pages need to stabilize. Resume once you've confirmed conversion tracking and page performance is clean.
Will Google penalize me for migrating?
No. Google documents migration best practices and accommodates it. Temporary rank fluctuation is expected, not a penalty.
What if I hate the new platform after migration?
Remigration is expensive and traumatic. Mitigate by: testing the platform extensively before committing, building a small pilot first, choosing platforms with genuine strengths for your needs rather than trendy choices.
Can I migrate just part of my site?
Yes, but it's tricky. Gradual migration (page by page, section by section) creates split infrastructure complexity. Only do it if the site is very large and a full migration is impractical.
How do I pick between Next.js, Webflow, Shopify, and optimized WordPress?
See our Squarespace vs Wix vs WordPress vs Next.js post. Match platform to your business needs, not to what's trendy.
Thinking about migrating off WordPress? We'll audit your current site and tell you honestly whether migration makes sense — often we recommend optimization instead of rebuild. Book a free consultation. See our web development Edmonton service and how long does it take to build a website for project planning context.
Get the Autonomous Enterprise Blueprint
A 14-page architectural guide covering the Agency7 mandate, the fractured pipeline, agentic ledgers, and the generative engine optimization playbook — delivered as a PDF to your inbox.