Should you migrate and redesign your website at the same time?

Migrate and redesign together when the new direction is approved, the current experience needs replacing, and your team can review the combined scope. Separate them when the immediate problem is the platform and the existing content and design still do their job.

The choice affects delivery and diagnosis. If the CMS, URLs, content, design, and conversion journey all change together, it becomes harder to explain a performance change after launch.

Name the problem before choosing the project

Ask what the business needs to improve. Slow campaign publishing might call for better components and editor ownership. Confusing product positioning might call for new content and design. Broken integrations need technical attention regardless of how the site looks.

These problems can coexist, but they should have separate acceptance conditions. “Launch the new site” does not tell you whether a marketer can now publish independently or whether a lead reaches the right team.

Compare three scopes

• Like-for-like migration: rebuild the approved experience on the new platform, preserving useful content and paths where practical.
• Migration with structural cleanup: keep the visual direction while improving components, CMS fields, and known technical problems.
• Migration with redesign implementation: build a new approved experience alongside the platform move, with explicit design and content dependencies.

Beqi implements designs supplied by your team or design partner. If those designs are still changing, account for that work and approval time before committing to the development schedule.

Use readiness as the deciding factor

Consider two illustrative situations. A team has a reliable design, a near-term campaign deadline, and a publishing bottleneck. Moving the existing experience first may solve the urgent problem. Another team has approved designs, outdated messaging, and time for thorough review. A combined project may avoid building an experience it already plans to replace.

Ask four questions: Are the new designs approved? Who owns the final copy? How dependent is the business on current search entrances? Can the team test every affected journey before launch?

Reduce changes you cannot explain

Google recommends sequencing major site changes rather than changing everything at once. Treat that as a reason to examine the scope carefully, especially when URLs also change.

Even in a combined project, maintain a release log, preserve important paths where practical, and record the pages and journeys being replaced. Compare results against a baseline that includes campaign and tracking changes.

Make the proposal describe the sequence

Ask for separate milestones for design readiness, content mapping, development, testing, and approval. Define how late changes affect cost and timing. Reserve time for live validation after the domain switch.

Use the migration budget guide and timeline guide to compare the same scope. Beqi can help you choose a sequence that solves the immediate publishing problem while leaving room for the next stage.