# Change your CMS without losing your rankings. The traffic you've earned is an asset. We migrate it like one: URL-for-URL mapping, redirects for everything that moves, and rankings watched through launch, while your content becomes structured data your team (and your future AI systems) can actually work with. **Sound familiar?** ## Why businesses leave their CMS - **The site got slower and scarier.** _(Developers)_ What changes: No plugin stack to patch. Speed comes from code you own. - **The agency stopped replying.** _(The business)_ What changes: You leave with the code, the content, and the docs in your name. - **Editing anything takes a developer.** _(Editors)_ What changes: A Studio built around your team: real-time editing, visual preview, no ticket. - **You're going AI-first.** _(AI)_ What changes: Structured content is the prerequisite. A migration is step one. Recognize two of these? The audit says which are costing you traffic, and which a move would fix. **Why Sanity** ## Your content stops being pages and becomes data. The migrated site runs on structured content: every service, article, and answer is data, not a blob in a page. That's AI-native, not AI-garnished: AI systems can read the site cleanly, and the migration becomes step one of your AI roadmap, even if step two waits a year. - **For your editors:** Real-time editing with a visual preview. Hard to break, no developer on standby. - **For the business:** Faster pages, no patch weekends, and a content model you own outright. - **For your AI roadmap:** Every fact in one place, so AI assistants retrieve the truth and agents can act on it. **Where traffic goes** ## Where migrations actually lose traffic Replatforms don't lose rankings mysteriously. Four causes do most of the damage; here is how we close each one. ### The redirect map. Old URLs that 404 hand years of link equity to nobody. How we prevent it: Every URL is mapped before cutover: kept, redirected, or retired on purpose. You approve the map before anything moves. ### Structured data that quietly goes missing. Rich results vanish when the new templates skip the JSON-LD the old site carried. How we prevent it: We snapshot the structured data the old site carries, rebuild it in the new templates, and re-test rich results before launch. ### Sitemap regressions. The new sitemap quietly lists a fraction of the pages the old one did, and Google notices before your team does. How we prevent it: We diff the new sitemap against the old one page by page, so nothing drops out of the index unnoticed. ### Image and social-preview drift. Broken OG tags and renamed image paths bleed image search and every shared link. How we prevent it: OG tags and image paths are parity-checked link by link before cutover, so shared links keep their previews. The checklist runs longer than this page: canonicals, robots rules, redirect chains, and internal links get the same before, during, and after cutover treatment. That checklist is the project. **The scope** ## What a migration includes ### What moves Restructured into Sanity, not pasted into it. - Pages, posts, and custom types - Media, with alt text and captions - Categories, tags, and relationships - Authors and roles - Forms, integrations, and metadata - The redirects you already have ### What we protect Nothing 404s by accident. - Every URL: kept, redirected, or retired on purpose - Rankings: parity-checked, then watched 30 days past launch - Rich results, sitemap, and social previews - Your editors, trained before handover - Your design, if you want to keep it Redesign is a choice, not a bundle. **How it works** ## Start with a free call, not a contract. 1. **Call** — Thirty minutes, free. You talk, we ask questions, and we both find out whether there's something worth building. _You leave with: A straight answer: worth moving, or not._ 2. **Audit** — We go through your current site and its traffic and rank what we find by return: what must survive the move, what shouldn't. What it earns today goes on record as a baseline, so parity is measured, not guessed. _You leave with: A proposal, ROI-ranked. Not a pitch._ 3. **Build** — Fixed scope, fixed price, weekly updates. You always know what's shipping and when. _You leave with: A migrated site, rankings watched through launch._ 4. **Run** — Optional. We stay on to keep it working and keep it growing, or take the keys; everything is yours either way. _You leave with: A system that keeps running. Yours either way._ Every project matures into a system that runs. **Before you call** ## The questions every owner asks. ### Will we lose traffic? The honest answer: a migration done carelessly loses traffic, which is exactly why the URL map, redirects, and parity QA are the core of the project, not extras. Done properly, rankings carry over; done well, the faster, better-structured site gains ground. ### What happens to our old URLs? Every one is mapped: kept identical where possible, 301-redirected where the structure improves, consciously retired only when a page earned nothing. You get the map before launch. ### What happens on launch day? The redirect map goes live before the domain flips, so no old URL ever goes unanswered. The sitemap is submitted the same day, the old site stays on standby as a rollback, and we watch search coverage and errors from the first hour. Launch day is designed to be boring. ### Which platforms do you migrate from? WordPress, Webflow, Squarespace, Wix, Drupal, and custom builds no one wants to maintain. Each has its own traps; the audit finds yours before cutover. ### Can you take over a site another agency built? Yes: inherited and half-finished builds are normal work. The audit tells you what you actually have; you decide what happens next. ### Do we have to redesign at the same time? No. A migration can preserve your current design entirely. Many businesses pair it with a [Growth Website Build](https://nativewise.ai/growth-website-build) since the site is open anyway, but that's a choice, not a bundle. ### What happens to our plugins? We audit every plugin before anything moves and sort them into three piles: features we rebuild into the new site (forms, booking, galleries), services that stay as integrations (email, CRM, analytics), and plugins that only existed to patch WordPress, which can go. You see the list before the proposal, so nothing surprises you mid-project. ### Can you handle a large site with thousands of posts? Yes. The audit and the content model take longer, and the migration itself runs as a script we test on a copy of the site first, then re-run at cutover so nothing published in between is lost. The process is the same at any size. ### Will we need a developer to manage Sanity afterwards? For day-to-day content, no: your editors change copy, add pages, and publish. For structural changes (a new content type, a new integration), yes, the same as any CMS. [Maintenance](https://nativewise.ai/growth-website-retainers) covers that if you keep us on. ### Who watches rankings after launch? The project does, for the first 30 days: that's when migration regressions surface, and the watch is part of the scope, not billed after it. Then the site is yours. Growing what it earns is a practice, not a project: SEO and AEO monitoring, monthly content, quarterly refreshes. That's the [Growth retainer](https://nativewise.ai/growth-website-retainers): optional, with the scope in writing. **Get a proposal** ## Move without losing what you've earned. Send us your URL. We'll tell you what a safe move looks like, and whether it's even worth it yet. 1. **Call** — 30 minutes, free. 2. **Audit** — Your current site and its traffic, ROI-ranked. 3. **Proposal** — What we'd move, and in what order. You'll hear back within one business day, from the person who'd run the migration.