Audit and migration plan
One source website, a content inventory and a map of old and new routes before the build begins.
Redesign & migration
For an existing website that needs a clearer experience or a more reliable foundation — while its content, routes and dependencies need careful attention.

Selected work
A selected digital presence in a technically detailed environment, where context and clarity matter together.
View selected workBase scope
One source website, a content inventory and a map of old and new routes before the build begins.
Up to seven reusable templates, one visual direction and responsive implementation for the agreed new structure.
Up to 30 standard content items to migrate, necessary redirects and a move into the agreed content system.
A test version, two dedicated migration approvals and a carefully planned switch to the new site.
Several source systems, complex databases, a shop, client data, unusual integrations after a technical assessment, large manual content work and scope beyond the agreed templates or content are planned separately.
Working together
We identify what should be protected, improved or consciously left behind.
OutcomeA migration boundary and risk overview
We prioritise content, routes and technical dependencies before implementation.
OutcomeA confirmed migration plan
The new direction and implementation develop alongside the agreed migration plan.
OutcomeA working test version
You verify transferred content before the new version goes live.
OutcomeA controlled site changeover
Practical questions
No. We start with a short audit of content, routes, forms and relevant technical dependencies. It shows what needs to move and what can change.
It is a starting boundary for pages or records with a standard structure. A larger or more varied archive is assessed after the audit.
No. We can prepare a technically careful transition within the agreed scope, including necessary redirects, but cannot guarantee ranking positions.
The audit determines that. We review the current platform, source access, content and dependencies before offering the migration scope.
Tell us what no longer works and what must stay intact. We will help frame a safe, useful next step.
For 30 calendar days after launch, we cover corrections to implementation errors in the agreed result.