Document migration scope including domain, URL, CMS, content, and hosting changes.
- Document migration scope including domain, URL, CMS, content, and hosting changes2 cited sources2 categories
Save for later 0
Use × to move an item here. You can restore it when you’re ready.
Your checks and saved items stay in this browser. Nothing is submitted.
Why this matters
Clearly defining the scope helps trace problems and assign responsibility during website migration.
Hypothetical standard operating procedure
Adapt this example to your site, access, tools, and change process. It is our suggested procedure, informed by the sources below.
- List all elements changing: domain, URL paths, CMS, content, hosting.
- Identify separate unrelated changes for isolated issue tracking.
- Assign responsible individuals for launch approvals, technical ownership, and content review.
- Define workflows needing to remain available during migration.
- Set criteria to pause or reverse launch if issues arise.
Watch for
Treating every migration as a simple file transfer risks missing critical differences.
Definition of done
Comprehensive document detailing every change aspect and assigned roles exists.
Sources & attribution
Original checklist wording and example SOP by Best SEO Checklist, using source-grounded AI assistance. Editorial contact: Ted Kubaitis, @tedkubaitis on Teams. Check current source guidance before implementation.