Loading...
Loading...
WordPress → Sanity port
Move your WordPress site onto Sanity and Next.js, without a redesign. This fits a marketing site with a costly plugin stack, frequent content changes and organic traffic worth protecting. Your marketing lead can then publish routine updates without waiting on the plugin queue.
Three routes
The smallest change that removes the block on your team is the right one. I will tell you which one I think it is after I read your plugin list and your URLs.
If hosting, theme weight or unused plugins cause the cost, repair WordPress. The inventory should be allowed to end there.
Not my work. Your own developer does it.
Your design is fine, your plugin debt is real, and your team waits on a developer. Move the site as it looks today onto Sanity and Next.js.
Scoped in writing after the inventory.
You need new page types, a block library, permissions and an approval process. That is a project, not a move.
Scoped as a project, in writing, after the inventory.
Who does the work
Scope
The process
The written scope comes after the inventory. You approve the remaining work before the build starts.
You and I agree the pages in scope, the plugins we replace, who decides, and what AI may do.
Output: A written scope and a set of control rules.
I list every plugin, custom post type, field group, form and URL. You mark what the business cannot lose.
Output: A plugin replacement table, a URL redirect map and my route recommendation.
I map your fields into a Sanity schema and build the page sections. I then set the permissions and put up a staging site.
Output: A working content model and a staging site, ready for your content.
I move the approved content into staging using the import method agreed in the scope. Staging must match the approved inventory before review.
Output: A complete staging site with a visible change log.
I check every URL, redirect, metadata field and form against the old site. You review staging and send one list.
Output: A parity report, an acceptance checklist and the acceptance fixes.
I record the rollback point, launch, and watch Search Console. I then show your team how to edit and restore a version.
Output: A live site, an editor guide and a rollback point.
If you want AI in it
The CMS works with AI switched off, and most teams start that way. If you include it, these controls become acceptance requirements in the written scope.
Safeguards
A move off WordPress puts your search results, your forms and your launch at risk. Here is what holds each one down.
Questions
Often, yes. A faster host, fewer plugins and a cleaner theme fix many sites for far less money. Move only when the plugin layer itself blocks the work. I tell you which one I think it is after the inventory, and a repair is a valid answer.
Nothing moves across as a plugin. Each active plugin gets a named replacement, and we agree the full list in step 2, before the build starts. Yoast becomes fields in the CMS plus code in the front end. Contact forms move to a form service. Caching plugins become the CDN.
Search performance is the main risk. I collect URLs from the agreed sources, carry the approved metadata across and test the redirect map on staging. I monitor Search Console after launch. I cannot promise a ranking.
The page builder goes. Elementor holds its layout in its own format. I extract the text, the images and the calls to action as content. I then rebuild the layout as page sections your team can reuse. Your team gains reusable sections and loses free-form drag and drop.
Sanity charges per seat, and it has a free plan for a small team and a small document count. Viewer seats are free on every plan. Read the Sanity pricing page before you set a budget, because vendor prices change. Your other monthly cost is the Vercel plan for the site.
Checkout does not move to Sanity. Sanity holds content, not commerce. A store needs a commerce platform. That is a bigger project than this page covers, and I will say so rather than take it.
That depends on your numbers, and I will not invent them. A site at this size usually carries four bills. Managed hosting, plugin and theme licences, a maintenance retainer, and a security subscription. Send me those invoices. I add up the yearly cost you remove, and I set it against the written scope. If it does not pay back, I tell you to stay on WordPress.
You own the site, code and accounts. The written scope states the defect warranty. It also lists the WordPress costs and maintenance work that end at launch, and the package maintenance that remains. There is no subscription to me.
Send your WordPress URL, current plugin list and latest hosting or maintenance invoice. I will tell you whether repair, port or rebuild deserves a written inventory.
Send me your WordPress URL