Website Migration Plan Template: Timeline, Owners, and SEO Checks
by Michael Santiago, Fullstack Developer & SEO
What Goes in a Website Migration Plan Template
A website migration plan template settles four things before anyone starts building: what is moving, in what order, who owns each step, and what has to be true before the project moves on to the next phase. The template below covers all four in seven parts. Copy it into a spreadsheet or a shared doc and fill it in for your own project.
This is the planning layer, not the technical checklist. The SEO detail lives in our SEO migration checklist. The plan supplies the dates, names and gates that make sure the checklist actually gets followed.
The seven parts:
- A one-page project summary
- The timeline
- An owner for every task
- Sign-off gates
- The SEO checks
- The launch-day runbook
- Rollback and monitoring
Migrations that go badly are rarely short on technical skill. They are short on a named owner for the redirect map, or a rule for what happens when testing fails. Those are planning problems.
Part 1: The One-Page Project Summary
Fill this in first and keep it to one page. Anyone on the project should be able to read it in two minutes and know what they are working on.
| Field | What to write |
|---|---|
| Type of move | Platform, domain, URL structure, design, CRM, or a combination. Most projects are more than one. |
| Reason | The business problem the move solves, in one sentence. |
| In scope | The sections, templates, integrations and content that move. |
| Out of scope | What is deliberately not happening, such as a copy rewrite or a new CRM. |
| Success criteria | What has to be true eight weeks after launch, such as organic leads back at baseline and every form delivering. |
| Launch window | The target week, plus the dates you cannot launch near, such as a seasonal peak or a campaign. |
| Decision maker | One person who can approve scope and content without calling a meeting. |
Not sure which kind of move you are making? Replatforming versus redesign separates the four project types. Give the out of scope row real care: anything not written down gets assumed, and each party assumes something different.
Part 2: The Timeline
Plan backwards from the launch window. The durations below are a planning baseline for a small to mid-sized site: roughly five to fifteen templates, a few hundred URLs or fewer, and a handful of forms and integrations. Revise them after discovery.
| Phase | Planning baseline | Phase ends when |
|---|---|---|
| Discovery and inventory | 1 to 2 weeks | Every URL, form and integration is listed and the baseline data is saved |
| Architecture and URL map | 1 to 2 weeks | The URL map and template list are approved |
| Build | 3 to 6 weeks | Every template works on staging |
| Content and media migration | Runs alongside the build | Every mapped URL has its content on staging |
| Staging QA | 1 to 2 weeks | Every redirect passes its test and every form and tag is verified |
| Launch | 1 day, plus a content freeze | The runbook is complete |
| Monitoring | 8 weeks minimum | The closeout review is signed |
Added up, that is roughly six to twelve weeks to launch, then two months of monitoring. A bundled redesign, content that needs rewriting, a CRM change and slow approvals all stretch it. Add that time to the phase it affects, not to the end of the project, where it gets squeezed.
For the launch date, Google's site move guidance recommends a lower traffic period where possible. In practice: not in your busy season, and early in the week, when the people who built the site are around to fix what turns up.
Part 3: An Owner for Every Task
Every row in the plan gets one name. "The team" is not an owner, and a task with two owners is a task each of them assumes the other one did.
| Role | Owns | Usually |
|---|---|---|
| Project owner | Scope, approvals, the go or no-go call | Someone internal with authority |
| Build lead | Templates, staging, deployment, redirect rules | Developer or agency |
| SEO lead | Inventory, baseline, URL map, redirect testing, monitoring | SEO specialist or agency |
| Content owner | What moves, what retires, content approval | Marketing lead |
| Marketing ops | Forms, CRM routing, analytics, ad pixels, call tracking | Marketing ops or CRM admin |
| DNS and hosting | Registrar, DNS, SSL certificate, the cutover itself | IT, the agency, or the business owner |
Settle two things in week one. Find out who holds the domain registrar login, because sometimes it sits with a former employee or a previous agency, and learning that on launch day stops the launch. Who owns your digital marketing accounts covers how to check. And keep building and testing separate: whoever wrote the redirect rules should not be the only one testing them.
Part 4: Sign-Off Gates
A gate is a point where the project stops until a named person confirms a short list of conditions. Four are enough.
Gate 1, scope. After discovery. The inventory is complete, baseline data is stored outside the website, and the out of scope list is agreed. Approved by the project owner.
Gate 2, URL map. Before the build. Every old URL with traffic, inbound links or conversions has a destination, and the content owner has confirmed which pages retire. Approved by the SEO lead and the content owner.
Gate 3, go or no-go. The day before launch. Every mapped URL passes its redirect test, every form delivers to the right inbox or CRM, tracking fires, and rollback is ready. Approved by the project owner, on sign-off from the SEO and build leads.
Gate 4, closeout. At the end of monitoring. The success criteria are reviewed honestly, including any that were missed. Approved by the project owner.
The rule that makes gates work: if a gate fails, the date moves, not the gate.
Part 5: The SEO Checks
Keep these in the plan as tasks with owners, and use the full checklist for how to do each one.
- Search Console, analytics, crawl and backlink exports saved before the build
- A one-to-one URL map, with no mass redirects to the homepage
- Server-side permanent redirects (Google recommends 301 or 308), kept for as long as possible and generally at least a year
- Titles, descriptions, headings, body copy, internal links and structured data carried over
- robots.txt and noindex checked on the live site within minutes of launch
- A new XML sitemap submitted in Search Console
- If the domain changes, the Change of Address tool, which needs owner access to both properties and is not used for HTTPS or same-domain path changes
Part 6: The Launch-Day Runbook
The order matters, and so does a name next to each line.
| Step | Owner |
|---|---|
| Content freeze on the old site starts the day before | Content owner |
| DNS time to live lowered a day or two ahead, if DNS is changing | DNS and hosting |
| Full backup of the old site, files and database | Build lead |
| Go or no-go call against Gate 3 | Project owner |
| New site deployed with redirects already active | Build lead |
| Staging protection removed, robots.txt and noindex checked live | SEO lead |
| Live crawl, plus a hand check of the top traffic URLs | SEO lead |
| Every form tested into the CRM, analytics confirmed recording | Marketing ops |
| Sitemap submitted, and Change of Address filed if the domain changed | SEO lead |
| Freeze lifted and launch confirmed to the team | Project owner |
Anything not on the runbook waits until tomorrow.
Part 7: Rollback and Monitoring
Write the rollback plan before launch, while everyone is calm: the trigger, who decides, and the mechanism. A sensible trigger is a problem that stops leads or sales and cannot be fixed quickly, such as forms not delivering. The mechanism is usually pointing DNS back at the old site, which only works if the old site and its hosting stay live and untouched until monitoring ends.
Then monitor on a schedule rather than whenever someone gets nervous.
| When | Check | Owner |
|---|---|---|
| Launch day | 404s, redirects, forms, tracking | SEO lead and marketing ops |
| Days 2 to 3 | Search Console errors, crawl activity, lead volume | SEO lead |
| Weekly, weeks 1 to 8 | Organic clicks and leads against the baseline, new 404s | SEO lead |
| Week 8 | Closeout review against the success criteria | Project owner |
Expect some movement. Google says it can take a few weeks or more to show the new URLs in place of the old ones, and that some fluctuation during a move is normal. A dip that recovers is the process working. A decline that keeps going is a specific, findable problem, and the discovery baseline is how you find it.
Frequently Asked Questions
What should a website migration plan include?
A one-page project summary with scope and success criteria, a timeline with an exit condition for each phase, one named owner for every task, sign-off gates, the SEO checks, a launch-day runbook, and a written rollback and monitoring plan. The SEO checks say what must be preserved. The rest of the plan makes sure a specific person is responsible for preserving it.
How long does a website migration take?
For a site with a modest number of templates, URLs and integrations, a reasonable planning baseline is six to twelve weeks from discovery to launch, followed by at least eight weeks of monitoring. A bundled redesign, content that needs rewriting, a CRM change and slow approvals all extend it. Treat any figure as an estimate to revise after discovery, not a commitment.
Who should own a website migration?
One internal project owner with the authority to approve scope and content, supported by named owners for the build, the SEO work, content, forms and tracking, and DNS and hosting. Confirm in the first week who holds the domain registrar login, because the launch cannot happen without it.
Do I need the Change of Address tool in Search Console?
Only if the domain or subdomain is changing. Google says the tool is not needed for a move from HTTP to HTTPS or for path changes within the same domain, and it requires you to be an owner of both the old and new properties. Wherever URLs change, permanent redirects from the old URLs to the new ones are still required.
Get the Plan Checked Before the Build Starts
The cheapest time to fix a migration plan is before anyone writes code. Get a migration scope review and we will check your inventory, URL map and owners against this plan and tell you plainly where the gaps are. For budget, see website migration cost. Book a discovery call or call us at 321-401-7016.