Make a migration register, not just a file count.
Combine the current CMS export, sitemaps and available traffic or server records to identify important entry points. Include documents, images that carry useful information, forms, department links and URLs used in printed materials. A crawl alone may miss unlinked attachments and pages used only during a seasonal program.
Record the old URL, content owner, proposed action, proposed destination, dependencies, reviewer and test result. Keep uncertainty visible. Use the audit workbook and migration map checker for the initial record; the checker assesses entered rows and does not create redirects.
Use the format decision guide to review document destinations and the meeting-record model for archive boundaries.
Decide what each old path should do.
| Content decision | Expected visitor path | Review before release |
|---|---|---|
| Keep at the same URL | The existing address serves the approved page. | Content, links and canonical address are correct. |
| Move or combine | The old address redirects to the relevant replacement. | The replacement actually answers the old task. |
| Retain an historical record | A clearly labeled record remains available under the agreed policy. | Dates, document context and current-service links are clear. |
| Remove with no replacement | The URL returns a deliberate not-found or gone response. | The authorized owner agrees that no relevant replacement is required. |
On a small screen, scroll the table sideways to see every column.
A broken-path response can be correct for a deliberately removed item. A successful HTTP response is not enough if it displays an unrelated page. Document the agency’s content and records decisions separately from the technical URL mapping.

Treat documents as part of the resident task.
Check whether an attachment is current, who owns it and where the new service page will link to it. Preserve descriptive labels and any necessary historical context. If a PDF is replaced by an HTML page, confirm that the new page contains the information people need before assigning the redirect.
Do not discard older records simply because a newer version exists. The responsible agency team should decide the retention and access treatment. Include document remediation or conversion work explicitly in the scope rather than assuming every file can be copied unchanged.
Use a redirect test matrix with expected outcomes.
For each priority old URL, record the expected first response, final destination and final page title. Test representative pattern-based redirects as well as individually mapped URLs. Check the actual host and scheme people use, including an old document URL reached from an outside website.
- A moved page reaches a relevant final destination through the intended permanent redirect.
- The final page returns the expected response and uses the intended canonical URL.
- New navigation and contextual links use final URLs rather than relying on redirects.
- Important query parameters still reach the intended service; fragments point to sections that exist.
- Redirect rules do not create loops, chains or catch-all paths to an unrelated homepage.
Google’s site move guidance (opens in a new tab) covers URL mapping, permanent redirects, internal links and monitoring. Search visibility can fluctuate during a move; a migration checklist cannot promise unchanged rankings.
Control the final change window.
Agree on a content freeze or a change log while the final copy is prepared. Name the person who reconciles late updates. Test the release on the actual deployment before changing the public destination, including important forms and supported external-service links.
Record who can approve launch, which unresolved issues prevent it, how the previous version can be restored and which content changes would need reconciliation after a rollback. Keep private previews protected. Confirm public indexing settings for the intended pages when the release is approved.
Define access and rollback responsibility through the ownership and maintenance record. A new CMS should support the content and URL plan you have actually accepted.

Review the paths after launch, not just the homepage.
Check priority services, changed URLs, downloads and outside-system handoffs. Review not-found responses and Search Console reports where available. Distinguish a deliberately removed URL from a broken destination. Record the issue, affected task, owner and correction before closing it.
Choose a monitoring period that covers the agency’s important service cycles. A short quiet window does not prove that annual or seasonal pages are correct. Keep the migration map available for later questions and newly discovered inbound links.
For budgeting, include the inventory, rewriting, document work, redirect configuration, testing and final change reconciliation. A page count alone does not describe that effort. The website cost and scope guide explains how to separate implementation from recurring responsibilities without assuming a universal migration price.
For the full project sequence, follow the redesign process guide. For implementation support, explore local government website design and redesign.

