Migration work

Move to a better-fitting website without losing the parts you have already earned.

A site migration is not a copy and paste job. Before the new design goes live, you need to know which pages, articles, images, and routes still matter, and what should happen to the rest.

A careful migration

Redesign the site without making its useful history disappear.

A visible redesign is only part of the job. The route plan needs to cover what stays, what gets rewritten, what redirects, and what can safely be retired.

That matters most for older blogs. An article may need a full rewrite before it belongs in search again, but losing its route by accident is not a useful migration strategy.

01

See what is there

List the pages, posts, media, metadata, and special files before deciding what the new site needs.

02

Separate useful history from old sales copy

Keep worthwhile articles and routes. Rewrite, redirect, or retire the pages that no longer fit.

03

Build and test

Create the new pages, bring over approved media, and test the routes, metadata, and visual result.

04

Switch with a route plan

Launch when the redirects, sitemap, headers, and public URLs have a known outcome.

U

URLs do not get left to chance

Every known public URL gets a planned outcome before the new site becomes public.

M

Media moves with the right pages

Images and logos are reviewed with their pages, then kept locally where they belong.

S

Search signals are checked before launch

Canonical URLs, sitemap entries, redirects, and relevant category pages are reviewed as part of the build.