
Slingshot Bio
Roboto converged Slingshot Bio's WordPress and Shopify sites into one headless Shopify build on Next.js and Sanity, instrumented end to end and AI-ready.
From WordPress to Sanity
Last verified:
The process
First we check the existing WordPress and see whether the data is clean enough to move straight over to Sanity, and plan around any auth walls or bot protection in the way.
Then we work out how WordPress renders its pages and pull the content out, even without CMS access.
Everything extracted runs through our sanitization pipeline, which flags slop, normalizes structure, and leaves us clean content to work with.
Before anything moves, we agree the Sanity content model with you, shaped around how your editors actually work.
We transform the content to the agreed schema and run a full dry run, so mappings and edge cases prove out before production.
Once the dry run is clean, everything moves into Sanity in one controlled cutover.
Every old URL gets mapped to its new home with the right redirect, so rankings and link equity survive the move.
Finally, automated browsers sweep the new site for data issues, design regressions, and missing SEO signals.
WordPress to Sanity
A content-only move from WordPress to Sanity takes at least six weeks. A move that comes with a redesign takes longer: Slingshot Bio's, which also folded a separate Shopify store into the same build, took three months from design to launch. Cost follows how messy the content is, more than how much of it there is: how many post types and ACF field groups you have, how many block types and shortcodes sit in post bodies, and how much content plugins hold outside the posts table.
WordPress keeps a post as one blob of HTML in wp_posts, with everything else spread through wp_postmeta. Sanity wants the opposite: typed fields, references between documents, and body copy stored as Portable Text, which is structured JSON rather than markup. So most of the work happens before anything moves. We go through the field groups and block types, decide which ones are real content and which were only ever layout, and agree the Sanity schema with your editors first.
Then we script the transform and run it as a full dry run into a separate dataset. Gutenberg and classic-editor HTML goes through an HTML-to-Portable-Text converter, with a custom rule for each block type you actually use. Anything it can't map gets flagged rather than dropped. Images come out of the uploads folder and into Sanity's asset store, and every inline image URL in the body copy is rewritten to point at the new asset.
We build the redirect map from the WordPress permalink structure before cutover, including the category, tag, author and attachment URLs WordPress generates on its own, and keep the old site live until the new one is verified. 1st Call Immigration's WordPress site had blocked content updates for five years with repeated PHP errors; after the move to Sanity and Next.js it scored near-perfect on Lighthouse for performance, accessibility and SEO.
Content mapping
| In WordPress | In Sanity | What to know |
|---|---|---|
| Posts and pages | Document types | One schema per type, so a case study and a blog post can carry different fields instead of sharing one template. |
| Gutenberg blocks and classic editor HTML | Portable Text | Paragraphs, headings, lists and links convert directly. Custom blocks become typed objects inside the text. |
| ACF field groups | Fields and objects on the schema | Repeaters become arrays and flexible content becomes a page builder made of block types. |
| Custom post types | Their own document types | |
| Categories, tags and custom taxonomies | Referenced documents | References keep the relationship, so renaming a category doesn't break every post that uses it. |
| Media library | Sanity image and file assets | Alt text comes across. Editors set crops and focal points in the Studio. |
| Authors | Author documents | |
| Yoast or Rank Math titles and descriptions | An SEO object on each document | Carried across as they are, so search snippets don't reset to defaults at launch. |
| Menus | A navigation document |
Watch for these
Elementor, Divi and WPBakery store layout as nested shortcodes or their own markup inside the post body. None of that converts to Portable Text on its own, so we rebuild those pages as Sanity page-builder blocks or strip the layout and keep the copy.
Forms, sliders, tables and anything WooCommerce manages sit outside the posts table, so a posts export misses them. We list every plugin that holds content during the audit and plan each one separately.
Sanity has no comment system. Comments can be archived as read-only data, moved to a third-party service, or dropped, and that choice needs making before cutover.
WordPress serves date archives, tag pages, author pages, attachment pages and feeds without anyone creating them. Each of those URLs needs a redirect or a deliberate 410, or it becomes a 404 that search engines still have indexed.
Key pain points
Talking trash about WordPress is therapy at this point. We've had to build it for years, and it's consistently awful. I guarantee that if you have used it for long enough, you've experienced a site-breaking PHP error or been locked out of your admin panel due to a faulty plugin. We know the world of horrors, and we regret adding to that share of the web. Yes, it really does power over 40% of all sites, roughly 41.5% at the last count.

Potential security vulnerabilities
Core, plugins and themes all need regular patching, and some fixes aren't yours to make. In October 2026, PHP2Shell left WordPress sites exposed until they or their host updated PHP, and WordPress.org said no WordPress update was planned.

Heavy reliance on plugins
If you want any new feature, install a new plugin. Before you know it, your site is held together by 27 plugins and a prayer that none of those plugins are removed from the market.

Compatibility issues
Themes, plugins, and core updates sometimes play nicely together, leading to surprise breakages and debugging sessions you didn’t plan for.

Maintenance takes time
WordPress doesn’t run itself. You have to run backups, security patches, plugin conflicts, and random errors. Someone has to tuck it in at night.

Performance needs tuning
WordPress sites need caching, CDN, and database optimization to stay fast, especially if you plan to scale.

Customization has limits
You think you can do a lot with themes and plugins, but when it comes to custom experiences, it means custom dev work (or going headless entirely).
Key advantages
You know where our bias' lies. We think Sanity is literally the best headless content management out there. The schema is code-based, so it can be easily versioned, scaled, and extended without a heap of third-party hoops to jump. Providing you build it with a solid foundation, which we always recommend Turbo Start Sanity, it's going to be the most valuable hub for content you can imagine.
It's got a very unique tooling called the Live Content API, which in simple terms means
when you press publish, its live.
No issues with caching, and a single API usage that scales perfectly with multichannel content delivery.
It also offers one of the best editorial experiences in the industry with Presentation and customizable content structures. We're obviously huge fans of it, and we've pivoted our business with it when we realized how ahead it is.

Real time collaboration
You write, your teammate tags in, adds citations, and updates the same doc without stepping on each other. It’s the fastest way to ship content without the "who has edit access?" chaos.

Live preview block building
With Sanity, you don’t have to guess what your page might look like. Real-time previews update the moment you type. It’s a 1:1 mirror of your site before it ever goes live, so your campaigns look right the first time.

Meta tags, structured content
Sanity’s structured content gives Google clean data and rich schema, so your pages surface higher without manual hacking. Automated schema, smarter metadata, and better rankings.

Better media management
A blazing-fast media library with first-class support for Cloudinary, Mux, Wistia and more. Upload, drag-and-drop, preview without wrestling with assets, and waiting for spins of doom.

Automated social sharing
Ever wanted to share one update, and automatically populate every social platform? Welcome to the future we've built that. Why should social media be a chore.

Automated image generation
Sanity keeps your subject centered and sharp like a tiny author thumbnail or a full-page hero banner. There are no awkward crops, or chopped heads. Your visuals just look right everywhere.
The migration is step one. Our Sanity team handles what comes after: builds, integrations and the content model work that keeps the new platform clean.
Sanity development agencyTell us what you're building. We reply within one working day. Jono or someone on the team picks up every message personally.
You can also book a call.
Functional, beautiful, websites that you actually want to edit