Services / Websites & Conversion / CMS & Migration
Choosing a CMS is a lifecycle decision — not a quick pick.
The right CMS platform saves five-figure maintenance costs every year — the wrong one costs a six-figure migration in three years. I choose task-first and migrate without data loss.
Editor experience
The marketing team has to be able to publish itself. No dev bottleneck for every copy change.
No tool lock-in
The data is yours, schemas are exportable. A switch stays possible if the platform no longer fits.
Migration plan
Phased migration instead of a big bang. Content, SEO and tracking are migrated together.
What you can book
Six building blocks, individually or as a package
We start with the CMS audit — after that it becomes clear whether migration or cleanup makes sense.
CMS audit
Editor workflow analysis, tech-debt inventory, plugin health, hosting costs. Output: cost-benefit map.
Stack choice
Headless (Sanity, Contentful, Payload, Strapi) vs. traditional (WordPress, Webflow, Statamic). Including a decision matrix.
Schema architecture
Content types, block architecture, localization strategy, workflow roles. Custom-tailored to your marketing team.
Content migration
Script-assisted migration of existing content, image optimization, meta-tag cleanup. With data validation.
GDPR + hosting
EU hosting (Vercel EU, Cloudflare), DPA/SCC clauses, backup strategy, GDPR data-model check.
Editor onboarding
Documentation, Loom tutorials, one or two hands-on workshops with the marketing team. Self-service from day 1.
How do we differ?
Three ways to choose a CMS
SaaS provider, WordPress studio or senior operator — all three have their place. Here's the honest comparison.
| SaaS provider directly Webflow, Framer, Squarespace | WordPress studio Classic web agency | Truong Suarez Stack-agnostic + migration hand | |
|---|---|---|---|
| Stack lock-in | High (proprietary format) | Medium (WP export possible) | Low (schemas exportable) |
| Performance | Medium (hosted, edge CDN) | Variable (plugin-bloat risk) | High (Next.js + edge hosting) |
| Editor experience | Strongly visual | Classic, many workflows possible | Custom schema, adapted to your team |
| Scaling ceiling | CMS limits, complex workflows difficult | DB limit, plugin conflicts | Headless setup scales horizontally |
| Best phase for you | Marketing team without dev resources | Classic mid-market with WP experience | Anyone wanting to avoid tech debt long term |
Comparison based on publicly available information, as of 2026. If your situation would be better served elsewhere, I'll tell you so in the intro call.
How we work
Five phases, one point of contact
The CMS audit is the anchor. Clarity first, then migration — every phase has an output you keep.
CMS audit
Editor interviews, tech-debt scan, cost-benefit analysis. Output: stack recommendation.
Schema concept
Content types, block logic, localization model. Output: schema documentation.
Implementation
CMS setup, front-end integration, build pipeline. Output: staging site.
Content migration
Script-assisted migration, validation, manual cleanup. Output: content library.
Editor onboarding
Documentation, workshops, Q&A sessions. Output: self-service team.
Stack
What we work with
Stack-agnostic — we choose by task, not by preference.
Headless CMS
- Sanity
- Contentful
- Payload CMS
- Strapi (self-hosted)
Visual / SaaS
- Webflow
- Framer
- Statamic
- Storyblok
WordPress (when it makes sense)
- WP-CLI
- Block editor (Gutenberg)
- Bedrock (Composer-based)
- Custom themes (Next.js + WPGraphQL)
Hosting / Ops
- Vercel (EU)
- Cloudflare Workers
- Hetzner (EU hosting)
- GitHub Actions (CI/CD)
Recommended entry point
Two paths, depending on where you stand
Clean up existing CMS pain or migrate to a new platform? That changes the depth of the entry point.
For you if
You want to clean up your existing CMS
You have tech debt (plugin bloat, slow loads, editor frustration) but don't want to migrate fully. A focused diagnosis with a cleanup roadmap is often enough.
7–10 days · report + 60-min call
Core Audit / Renew existing
- – Plugin & tech-debt audit
- – Editor workflow analysis
- – Performance status (Core Web Vitals)
- – Cleanup roadmap with effort estimate
For you if
You want to migrate to a new CMS
Your existing CMS has hit its limits and you want to switch to headless or another stack. You don't just need a diagnosis but a stack recommendation plus a migration plan.
7–10 days · report + 60-min call
Core Audit / Build new
- – Stack recommendation with decision matrix
- – Schema concept for the new CMS
- – Migration roadmap (effort + risks)
- – GDPR hosting recommendation
Not sure? The symptom triage on the audits page helps you choose. The audit fee is credited toward a follow-up project.
When this becomes relevant
Typical starting points
Three recurring situations where CMS & migration is the right tool.
Migration
Relaunch without SEO loss
How a CMS switch and SEO migration run in one workstream — without losing rankings.
GDPR
GDPR consent compliance
Which CMS platforms run GDPR-compliant without having to vet every single plugin.
Accessibility
BFSG accessibility 2025
Why the CMS choice decides whether accessible content stays maintainable without permanent workarounds.
FAQ
What clients often ask before the first collaboration
Headless or traditional CMS — which is better?
No blanket answer. Headless (Sanity, Contentful) for: performance-critical, multi-channel (web + app + newsletter), dev-driven teams. Traditional (WordPress, Webflow) for: marketing self-service without dev, fast iteration. In the audit I weigh tasks against stack instead of selling a favorite platform.
WordPress or Contentful — which use case?
WordPress: mid-market with an in-house content team, lots of existing content, a classic funnel. Contentful: multi-brand, international rollout, tight integration with apps or e-commerce. Sanity is often the better headless middle ground — flexible and affordable.
How painful is a migration really?
Realistically: 8–12 weeks for 100–500 pages, of which about 30% is tech (schema, migration script) and 70% content cleanup (images, meta tags, broken links). To avoid the pain, plan 8 weeks of buffer and work with phased migration instead of a big bang.
How long does editor onboarding take?
For headless with a custom schema: 2–3 workshops of 1–2 hours, after which about 80% of the marketing team works independently. Complex workflows (multi-stage approvals, branch publishing) need 1–2 months of polish. Documentation and Loom videos stay available permanently.
Custom CMS build or standard platform?
A custom build (e.g. Payload with its own UI) almost never pays off — over 95% of requirements are covered by SaaS or open-source CMS. Custom causes exponential maintenance costs. I only recommend custom when a very specific workflow (e.g. a newsroom CMS with approval trees) can't be represented otherwise.
Let's talk
Three paths — depending on where you are.