Content, URL, media and integration inventory, with an agreed migration map
Build capability · CMS migration
Leave the slow CMS behind. Keep control of what comes next.
Move to a faster website and a CMS your team can understand. We rebuild the content model, protect the migration path and scope secure access for tools such as Codex, Claude Code and Hermes Agent.
No validated baseline
Compare Diagnose optionsApproved roadmap or backlog
Discuss your CMS migrationDiagnosis can stand alone. Implementation begins only after scope is agreed.
The migration brief
A system you can work with.
Legacy constraint
Every update needs a workaround.
Pages are tied to templates, plugins or an editor the team struggles to use.
Target state
Content your team can understand.
Named fields, reusable content types, preview and a documented publishing workflow.
Acceptance check
Your editors complete an agreed publishing task in staging.
Legacy constraint
The platform slows the experience.
Rendering, legacy dependencies and oversized assets can make routine visits expensive.
Target state
A delivery layer with a measured baseline.
A leaner frontend, asset handling and caching shaped around your actual pages and traffic.
Acceptance check
Compare agreed page templates against the pre-migration performance baseline.
Legacy constraint
Access depends on manual handoffs.
Content, code and publishing permissions are difficult to separate or explain to a tool.
Target state
Useful tools. Explicit permissions.
Documented repository or API access, with an MCP connector where supported and included in scope.
Acceptance check
Verify permitted actions, denied actions, review and revocation for the selected tool.
Illustrative requirements. The target CMS and access model are selected after discovery.
Role in the roadmap
A delivery capability within Build.
CMS migration is a Build capability when the current platform blocks publishing, performance or discovery. Diagnose establishes what needs to change; the migration scope defines what moves, what is rebuilt and how the team will run it.
A target CMS and content model shaped around the team’s editing tasks
Template rebuilds, asset handling and measured performance improvements
Redirects, metadata, canonicals, structured data and search-access checks
Role-based editing, preview, publishing approvals and scoped AI-tool access
Staging rehearsal, production validation, editor training and handover
A useful connection, with clear permissions
Let your team and its tools work from the same structure.
Readable content and authorised tool access solve different problems. We scope both deliberately, so making your website easier to discover does not mean opening its administration to everyone.
Public discovery
Deliver meaningful HTML, clear URLs and structured information that permitted crawlers can retrieve. Validate rendering, metadata and crawler policies.
Public content stays public.Private tool access
Connect approved tools through a documented repository, CMS API or a supported MCP server. Define the specific content, environments and actions each connection can reach.
Access is authenticated and scoped.Controlled publishing
Use drafts or branches, preview and human review before release. Keep credentials outside content, record changes and verify that access can be revoked.
Publishing follows an agreed workflow.Plan around the tools you use.
Codex, Claude Code and Hermes Agent provide MCP integration options. CMS compatibility, authentication and the permitted actions must be verified for your deployment. A connector is not a blanket permission to publish.
The route to production
A rehearsed move. An understandable handover.
- 01
Discover
Inventory the content, URLs, assets, integrations and permissions. Establish editing and performance baselines.
Output: migration map and target-platform decision - 02
Rebuild
Model the content, configure the editor and move representative pages into staging. Define tool permissions before connecting agents.
Output: testable staging site and access model - 03
Rehearse
Validate exports, content reconciliation, redirects, forms, analytics and rollback. Have editors test real publishing tasks.
Output: launch checklist and acceptance record - 04
Release
Run the agreed content freeze or delta sync, deploy, verify production and hand over runbooks and ownership.
Output: release record and scoped post-launch checks
Bring the current website. Start with the constraints.
Share your CMS, content volume, editing pain points, integrations and preferred AI tools. We confirm feasibility, scope and a quote before implementation.
Published scopes
Choose the bounded workstream the roadmap supports.
Choose the destination by how your team publishes, how your content travels and which integrations you need to maintain.
Build
Build
Search-Safe Migration
€4,000–€10,000
One-off · scoped
Platform migration with URL inventory, redirects, metadata and schema preservation, launch QA and post-launch checks.
Boundary: The published range covers the search migration scope. CMS selection, content modelling, bespoke integrations and AI connectors are confirmed and quoted against the actual requirements.
Discuss this scope →We confirm dependencies, access and acceptance criteria before implementation starts.
Scope control
Know what completion means—and where the work stops.
How completion is validated
- 01Content and media reconciliation against the agreed inventory, with exceptions recorded
- 02A tested redirect map, representative crawl checks and a before-and-after performance record
- 03Editor acceptance tests and verified allowed, denied and revoked tool actions
- 04A release record, rollback procedure, named owner and agreed post-launch check window
Where scope ends
- 01The target CMS is selected after discovery; no platform is assumed to fit every website.
- 02AI integrations are included only when named in scope and validated against the selected tool, CMS and authentication method.
- 03Third-party subscriptions, bespoke CRM or commerce integrations and ongoing maintenance are quoted separately unless explicitly included.
- 04Rankings and traffic can fluctuate during migration. No zero-loss migration, universal AI compatibility or security guarantee is made.
Start with the evidence.
Diagnose identifies which work is justified, who owns it and how completion will be validated. Build is scoped against an approved backlog; recurring ownership belongs in Operate.
Prefer to talk first? Get in touch