Migration Plan

Where This Sits

7

Components in the finished document

2

Measured directly, not asserted

4

Pieces that carry my judgment

This is a Direction deliverable, which means it turns findings into a sequence. It is the unit of scope: it can be commissioned on its own, priced on its own, and accepted on its own, whether or not anything else is bought alongside it.

It is not a package and not a retainer. It is one document with 7 components, and the list below is the whole of it.

What Is Scoped Inside It

These are separately scopable pieces of work. They are normally bought as part of the whole, but any one of them can be commissioned on its own if that is all you need.

Migration risk audit. A pre-launch account of everything the planned change could break, sized by what each break would cost.
IA and URL architecture plan. The structure the site should have, the URL rules that express it, and the path from here to there.
Redirect map. A complete, tested mapping of every existing URL to its destination, so nothing that earns traffic or links is lost at launch.

What Is Inside It

Every component is listed with the one sentence that says what it is. They are grouped by how each one is produced, because the difference between a number a tool gave me and a number I decided matters more than most reports admit.

Measured

Pulled straight from tools and logs. No interpretation, so you can re-run any of it yourself and get the same numbers.

Old URL inventory: Every URL that currently exists and earns traffic, links, or both.
Owner assignment table: The named person accountable for each item, on the client's side and mine.

Computed

Built by combining the measurements above. Every figure states the inputs it came from.

Template parity matrix: Which elements exist on the old template and whether they survive on the new one.

Judged

My reading of the evidence. This is the part you are actually paying for, and the part you are entitled to argue with.

IA diff: The old and new site structure side by side, with every moved, merged and removed node marked.
Launch gate criteria: What must be true before the release is allowed to proceed.
Rollback trigger definitions: The specific conditions under which the change should be reversed, agreed in advance.
Dependency map: What must happen before what, so the sequence cannot be reshuffled by accident.