Skip to main content

Free CometWeb ebook

A website migration with clear acceptance criteria.

The new site loads, but old URLs lead nowhere or the form no longer stores enquiries. This guide helps you plan the move and verify more than the appearance of the new website.

25 pages, PDF + HTML, in English

Cover: Website migration under control

In the guide

7 pre-launch decisions and a migration workbook

Explore the guide and materials

Get the ebook and worksheets

We will send a link to verify your email address.

Use your regular mailbox. Temporary email addresses are not supported.

We use these details to provide the materials. No newsletter subscription. Privacy policy.

Materials prepared by CometWeb.edition 1.3

What should you check before a website migration?

Define what changes: the domain, CMS, URL structure, content or several things at once. List important old URLs and record a decision for each. Then choose destination pages and how moved content will be handled.

An HTTP 200 response alone does not prove a successful migration. A URL can show the wrong content, a form can report false success and measurement can stop tracking the same event. Define acceptance criteria, evidence and conditions for stopping or reversing the launch.

Method example
Old URLTarget content
/oferta/uslugi
/kontakt/kontakt
/stary-poradnik/
HTTP 200. But which content?Check the destination, not just the status.
Compare two states

From migration scope to post-launch checks.

Leave with a decision plan for launch and the checks that follow.

Method example
Define the scope
Old URL
Journey starts here

Scope and URL decisions

Separate system changes from content and structure changes. Understand why low traffic alone does not justify removing a page.

Method example
Old URL
Target content
Connect the starting point to the result.

URL mapping and redirects

Choose the content successor before the redirect rule. Work through a five-URL example and a blank map for your own project.

Method example
Before
!Evidence missing
After checking
Result recorded

Launch criteria and recovery

Record who decides to launch, which gaps block the release and when to activate the agreed recovery plan.

Method example
Review the release
✓What was checked
✓Evidence and result
Next action
Ready to share with the team

Acceptance and measurement

Check key journeys, enquiry receipt and old URLs. Distinguish a deployment fault from changes in content visibility.

Page 9: a five-URL map for an example migration.
Page 9: a five-URL map for an example migration.Open the excerpt at full size

Start with five URLs, not an empty spreadsheet.

The excerpt shows a small migration map. The package contains a completed example and a blank file. Give each URL a decision, then define the test result that will confirm it.

  • Choose old URLs important to visitors and the business.
  • Assign target content and expected behaviour.
  • After launch, retain evidence for every acceptance criterion.
Get the free ebook

Read it. Put it to work.

Free materials in English. Verify your email, choose a format and download your files.

PDF guide

25 pages. For reading, saving for later or printing.

Online reading version

HTML for reading in your browser. Revisit the guide on your phone or computer.

Migration workbook, CSV maps and plans

Includes XLSX, blank and sample maps, a seven-decision plan, a launch plan and a recovery plan, plus a demonstrator workshop for technical teams.

Before a CMS, domain or structure change.

For agencies, developers and people reviewing a new website. The guide organises responsibilities and evidence. Backup and cutover procedures still need to match the specific system and infrastructure.

No. The guide organises decisions, URL mapping and release checks. Backup, cutover and recovery details need to match your particular system.

About the publisher: CometWeb

Decide what must work before saying “publish”.

Get the free ebook

Free, no newsletter subscription