Content migration
WordPress export → Sanity, Contentful, or MDX. Content modeled, not just copied.
// wordpress → next.js
Out of WordPress, into something you control.
Migration work for content sites that have outgrown WordPress — performance dragging, plugins fighting, editors held hostage by themes. We migrate to Next.js with rankings intact.
// where teams get stuck
WordPress that's expensive to keep and risky to leave.
- Twenty plugins, three of them load-bearing, two of them abandoned.
- A theme that nobody on the current team can read.
- Editors copying HTML into the visual editor.
- Page speed that drops every time someone updates a plugin.
// what's included
What ships.
Redirect map
Every WP URL mapped to the new structure. SEO continuity defended.
Custom post types preserved
Wherever they earn it, modeled as Sanity types. Wherever they don't, retired.
Performance budget
LCP under 2.5s on 4G. Documented and monitored.
Editor training
Your editors stop fighting WordPress and start writing. Walkthrough included.
// how we work
Three phases. Built to last.
01 · Calibrate
Content audit. Redirect map drafted. Written scope.
02 · Build
Next.js + CMS in parallel with content migration. Weekly demo.
03 · Hand off
Cutover with redirects live. Editor training. Support window starts.
// common questions
What teams ask before signing.
Not if the redirect map is right. We've migrated sites with six-figure organic traffic without losing rankings. The risk is in the cutover; we plan it carefully.
Most plugin functionality has a better home post-migration. Forms → typed fields. SEO plugin → Next.js metadata API. We document each one.
Yes. We rebuild the visual design natively in Next.js, matching the old theme's intent, not its quirks.
Scoped per project. Timing depends on content volume and integration depth. We share the timeline in the written proposal after the discovery call.
Scoped per project. We scope by content size and integration count, and send a written proposal after the discovery call.