Rated 5.0 out of 5,5.072 Google reviewsThis is our most common move. We built the Sanity sites for Krown, Hopewell Residential and ERP-One.
Sanity sites we've built
Krown
Hopewell Residential
ERP-One
SocialNext
CHF BC
Why teams leave WordPress
Most of the WordPress sites we move work fine for visitors. The trouble is behind the scenes.
Usually the site was built with a theme or Elementor a few years ago. Editors can now drag a section out of place, a plugin update breaks a page every few months, and small structural changes need a developer. Every plugin is one more thing to keep updated.
In Sanity, editors fill in fields and choose from sections we've designed. The layout lives in code, so nobody can drag it out of place. The front end is a Next.js or Astro site with no plugins to patch.
What moves and what doesn't
Everything visitors and search engines see comes across. Some WordPress machinery is replaced on the way.
Posts and pages
Move by script through the WordPress REST API, with their dates, authors, categories and tags. Body content becomes Portable Text, Sanity's structured rich text.
URLs
Every post and page keeps its path where it can. Where a path has to change, such as category archives or attachment pages, it gets a 301 to its closest new page.
SEO settings
Yoast or Rank Math titles, descriptions, canonicals and social images map to fields in Sanity, page by page.
Media
Images and PDFs move to Sanity's image CDN with their alt text. Old /wp-content/uploads/ links redirect, so PDFs linked from other sites still open.
Forms
Contact Form 7, Gravity Forms and the like don't move. We rebuild each form and send it to the same inbox, CRM or spreadsheet as before, then test it with real submissions.
Plugins
Each one is replaced in code, by a service or dropped. The inventory shows which ones the site actually uses.
Editors
Get new Sanity logins. WordPress passwords don't carry over. If the public signs in to your site (members, courses, a shop), see "When to stay on WordPress" below.
How the content maps
Post types
Each post type, including custom ones, becomes a Sanity document type with its own fields.
Custom fields
ACF and other custom fields become typed fields: dates are dates and links are links, so they can be checked before publishing.
Categories and tags
Become references, so renaming one updates it everywhere.
Page builder sections
Elementor or block layouts become a short list of sections editors choose from. We design those sections from the layouts your site actually uses.
Shortcodes and embeds
Become content blocks with a preview, in place of bracketed codes in the text.
Menus and settings
Become navigation and settings documents in Sanity.
How the move runs
Four to six weeks for a like-for-like move, then four weeks of checks.
01
URL and content inventory (week 1)
We crawl the site and pull its Search Console and analytics history, then list every post type, custom field, plugin and form. You give us an admin login and Search Console access.
You keep: the URL inventory and plugin list, as a spreadsheet.
02
Content model and redirect map (weeks 1 to 2)
We map each post type and field to its Sanity schema, and each old URL to its new address. You decide what to retire or merge.
You keep: the Sanity schema and the redirect map.
03
Build in Next.js or Astro (weeks 2 to 5)
We rebuild every template to match the current site, then improve speed, accessibility and structured data underneath. You review on a staging site that stays out of Google.
You keep: the code, in your own repository.
04
Scripted import (weeks 3 to 5)
A script moves posts, pages, media and SEO fields into Sanity, and we can re-run it right up to launch so nothing published in the meantime gets lost. We check a sample of every content type against the live site.
You keep: the import script and a clean export of your content.
05
Launch and four weeks of checks
The redirects go live with the site. Each week we compare Search Console coverage, rankings and 404s with the inventory and fix anything that slips. Your editors get a training session before launch.
You keep: a before-and-after report, and editors who know Sanity.
Next.js or Astro?
Both read from Sanity in the same way, so the choice is about what the site needs to do.
Astro suits content sites: marketing pages, blogs, resources. It sends very little JavaScript to the browser. This site runs on Astro, and moving to it cut one of our case study pages from 1.3 MB of JavaScript to 14 KB.
Next.js suits sites that behave like applications: logins, dashboards, booking flows, heavy personalisation. Krown's 300+ dealer microsites and booking engine run on Next.js and Sanity.
If you aren't sure, we'll recommend one after the inventory. Your content and the Sanity schema are the same either way.
The WordPress migration checklist
The WordPress-specific checks we run before launch, on top of our website migration checklist.
Trailing slashes
WordPress URLs usually end in a slash. The new site either keeps them or redirects them, and does it the same way everywhere.
Archives and feeds
/category/, /tag/, /author/, date archives and /feed/ URLs are kept, rebuilt or redirected. None are left to 404.
Uploads
Every linked /wp-content/uploads/ file still resolves, especially PDFs other sites link to.
Sitemaps
Yoast's sitemap_index.xml redirects to the new sitemap, and Search Console gets the new one.
Yoast and Rank Math data
Titles, descriptions, canonicals and noindex settings match the old site page by page.
Forms and tracking
Every form is submitted for real, and GA4 events fire as before.
When to stay on WordPress
Not every WordPress site should move. If the business runs on WooCommerce, a learning platform such as LearnDash, or a membership plugin, rebuilding all of that costs more than it saves. The same goes for a team that knows WordPress well and likes it. In those cases we'd suggest a cleaner rebuild on WordPress through our WordPress development work.
There's a middle route too: headless WordPress, where your team keeps writing in WordPress and the front end is rebuilt in Next.js or Astro. Our headless CMS development page covers when that makes sense.
What a WordPress to Sanity migration costs
Most of our like-for-like WordPress migrations cost between $6,000 and $10,000 CAD. Where a site falls depends on how many kinds of page it has, how many custom post types and fields need modelling, and which plugins have to be rebuilt in code. Registered charities and nonprofits get 10% off.
Templates
How many kinds of page the site has, not how many pages.
Custom post types and fields
Each one needs a schema and a place in the import script.
Plugins and forms
Anything the site depends on that has to be rebuilt.
Design changes
A refresh on the way adds to the cost; a new structure is priced as a website redesign.
You get a fixed price after the URL and content inventory.
Paper Crane is one of our go-to partners when it comes to custom web development. The team is wonderful to work with, super collaborative, and always on top of the latest tech with great pros/cons lists around various platform options depending on a client's needs. Robert is a great addition to any digital pitch team too as he's able to outline explain tech options in a results-friendly way. And don't even get me started on how awesome their tracksuits are...
Jill Dewes · Google ·
5 out of 5 stars.
We have been working with Paper Crane for years, and they have been an outstanding partner. They are professional, easy to work with, and consistently deliver high-quality work. Their team brings strong expertise in strategy, design, and digital development.
Paper Crane has supported us across a wide range of projects, including a company rebrand and new logo, a complete website rebuild, a custom knowledge base product, and design improvements for our new software products. Their expertise and approach have made them an invaluable partner to our software company. We look forward to our continued partnership.
Will our URLs and Google rankings survive the move?
Yes, if the redirects and on-page details carry over. Posts and pages keep their paths, everything that has to change gets a 301 to its closest new page, and Yoast or Rank Math settings move page by page. We compare rankings and coverage weekly for four weeks after launch.
What happens to our Elementor or page builder layouts?
We rebuild them as a set of sections your editors pick from. The pages look the same, but nobody can drag a column out of place.
Can our editors learn Sanity?
Yes. Editing in Sanity means filling in labelled fields and choosing sections, which most teams find simpler than a page builder. We train your editors before launch, and live preview shows the page as they type.
Should we use Next.js or Astro?
Astro for content sites, Next.js for sites with logins, dashboards or booking flows. The Sanity side is the same either way, and we recommend one after the inventory.
What about our forms, search and plugins?
Forms are rebuilt and sent to the same inbox or CRM. Site search is rebuilt on the new stack. Each plugin is replaced in code, by a service, or dropped if nothing uses it.
Can we keep publishing during the migration?
Yes. The import script re-runs right up to launch, so anything published on WordPress in the meantime comes across. We freeze edits for a day or two around the switch.
How much does a WordPress to Sanity migration cost?
Most of our like-for-like WordPress migrations cost between $6,000 and $10,000 CAD. You get a fixed price after the inventory.
Moving off WordPress?
Book a 30-minute call. Send us your site first, and we'll tell you what moves easily, what needs rebuilding and roughly what it would cost.
We use cookies to see how the site is used and to measure our ads. Accept, or decline and we'll keep to the cookies the site needs to work. Privacy policy