A CMS (content-management system) migration moves website content, design elements, and data from one system to another, often to gain speed or performance, according to Shopify in Shopify's CMS migration guide. A website redesign changes a site's content, code, structure, layout, color scheme, and navigation to improve user experience, usually without changing the underlying CMS, according to ContentBloom in ContentBloom's redesign overview. The two projects are often confused because both can change how a site looks.
The practical test is what moves. Migration swaps the platform behind the site. Redesign updates the presentation on the same platform.
Official resources:
- Follow Google's site move and migration best practices — Check current steps to preserve search rankings during a CMS or URL move.
- Read Google's original advice to move first and redesign second — Verify why Google recommends splitting a site move from a redesign.
Table of Contents
- What does each project change?
- Which problem are you solving?
- Why does migration need data work?
- How do you limit risk?
What does each project change?
Redesign focuses on appearance and use. It revises templates, navigation, color, layout, and page structure. Migration focuses on core function, features, and content workflows, as Zesty.io describes the split.
Migration scope is broader behind the screen. It covers pages, posts, media, user data, taxonomies, and custom fields. It also covers metadata, URL slugs, internal links, and connected integrations.
- Pages, posts, media, and user data
- Taxonomies, custom fields, and metadata
- URL slugs, internal links, and redirects
- Forms, search, and CMS-connected integrations
Which problem are you solving?
Choose redesign when visitors struggle to read, navigate, trust, or complete tasks. Common signals are dated layouts, tangled menus, weak calls to action, and poor mobile use. The CMS stays, but the experience changes.
Choose migration when editors struggle to publish or the platform limits growth. Common signals are slow publishing, rigid content models, weak permissions, and costly maintenance. A migration can also change back-end infrastructure without changing visual presentation, while a redesign can change presentation without moving platforms, according to Firecrawl.
Why does migration need data work?
Migration is an extract-transform-load task because source and target data models rarely match, according to Firecrawl's developer guide. WordPress stores content in wp_posts plus meta tables. Many modern systems use typed content models with strict fields. That mismatch forces mapping and cleanup.
A post body may split into title, slug, excerpt, blocks, and relations. Media needs new references. Taxonomies, custom fields, slugs, and links need explicit rules. Test the mapping on real content before moving the full site.
How do you limit risk?
Treat migration as riskier for continuity. Shopify warns of downtime, formatting problems, and data loss. Owners, editors, developers, and organic-search visitors all feel the transition when pages break or slow down.
Do not combine a platform move with a major visual overhaul. Doing both at once compounds failure points and hides the cause. Google advises splitting domain moves from redesigns into two phases, described in Google's site-move best practices. Move first, then redesign second.
