Platform migration
Website migration services, without losing what you have built
Moving platforms is where most sites lose their rankings, their content, or both. I move yours across intact: every URL redirected, every page accounted for, nothing quietly dropped.
What actually goes wrong in a migration
Migrations rarely fail on the build. They fail on the thousand small things around it: URLs that change shape and never get redirected, metadata that does not survive the export, content that existed on the old site and simply is not on the new one.
The damage shows up weeks later as a slow ranking decline nobody can trace back to launch day. By then the old site is gone and the evidence with it.
I run migrations from an inventory. Every page, every URL, every piece of metadata is recorded before anything moves, then reconciled after launch. If something did not make it across, we know before Google does.
Platform pairs
Common migration paths
WordPress to Shopify
Moving a WooCommerce catalogue onto Shopify, with product data, URLs and SEO carried across.
WordPress to Shopify →Framer to WordPress
Rebuilding a Framer site on WordPress when you need a CMS, plugins, or a team that can edit without a designer.
Framer to WordPress →Into or out of HubSpot
HubSpot CMS migrations in both directions. I have shipped a full HubSpot rebuild as reusable modules.
HubSpot migration →The redirect map is the whole job
Every migration lives or dies on one document: the map of every old URL to its new destination. Get it right and rankings transfer within weeks. Get it wrong and you lose traffic that took years to build, usually without realising until a quarter later.
The mistake is treating redirects as a launch-day task. By then the old site may already be partly dismantled and the full URL list is hard to reconstruct. The map has to be built first, from a crawl of the live site, while everything still exists.
It also needs to be complete rather than convenient. Redirecting everything to the homepage technically avoids 404s and is close to useless, because a homepage redirect tells Google the old page no longer has an equivalent. Each URL needs its actual destination.
What to watch after a migration goes live
The first fortnight after launch is where problems are cheap to fix and easy to miss. Rankings normally wobble for a week or two while the new URLs are recrawled. That is expected. What is not expected is a steady decline that does not recover.
I watch three things: crawl errors in Search Console, impressions by page compared to the same period before launch, and whether the redirect map is actually firing on live requests rather than just existing in a config file.
Most migration damage is recoverable if it is caught in the first month. After six months, with the old site gone, it is a rebuild of the lost content rather than a fix.
Process
How a migration runs
→
Full inventory of the current site: every URL, title, description and asset recorded
→
Redirect map built before the build starts, not after launch
→
Content and media moved across, with nothing left hotlinking the old platform
→
Rebuild on the destination platform in a proper design system
→
Reconciliation pass: every old URL checked against the new site
→
Post-launch monitoring so ranking movement is caught in days, not months
Which one do you actually need
Migration versus redesign
You need a migration when
→
You are moving from one platform to another
→
The current platform cannot do what the business now needs
→
Licensing, hosting or maintenance costs have become the problem
→
Your team cannot work in the current system
You need a redesign when
—
The platform is fine but the site is not converting
—
The design is dated but the foundations are sound
—
Content and structure are the issue, not the technology
—
You want better results without changing systems
Case studies
Migrations and rebuilds I have shipped
Snappy Kraken
Solo front-end owner on a HubSpot CMS rebuild. Marketing site, product pages and pricing shipped as reusable modules in 21 days.
Read the case study →Advisor Websites
UI/UX redesign of B2B landing pages for financial professionals, rebuilt around a single conversion path.
Read the case study →Investment
What a migration costs
$5,000 to $50,000
Migration pricing tracks page count and how clean the source site is. A tidy 10-page site is straightforward. A decade of accumulated pages with no consistent structure is a different job.
→ Fixed scope, quoted after the inventory
→ Redirect mapping included, never an add-on
→ Rankings monitored after launch
Book a CallFAQs
Common questions
Will I lose my Google rankings when I migrate?
Not if redirects are mapped properly and content survives the move. Ranking loss in migrations is almost always caused by unredirected URLs or content that quietly disappeared. Both are preventable with an inventory-first process.
How long does a platform migration take?
Typically 4 to 10 weeks depending on page count and how much needs rebuilding rather than transferring. The inventory phase tells us which it is.
Can you migrate my WooCommerce products to Shopify?
Yes. Product data, variants, images and category structure move across, with URL redirects mapped so existing product rankings are preserved. I have handled catalogue work at scale, including a 1,546-item B2B catalogue.
What happens to my old site?
It stays live until the new one is verified. I do not take the old site down until every URL has been checked against the new build.
Do you migrate to Framer as well as away from it?
Both. Framer is a genuinely good fit for marketing sites that do not need a heavy CMS. It is a poor fit when you need plugins or non-technical editors. The right answer depends on who maintains the site after launch.
Planning a platform move?
Book a call and bring your current site. We will scope what actually needs to move.
Book a Call© Jackai Agency 2026. B2B web design, Vancouver BC.
