A practical docs migration playbook

Documentation migrations fail in the handover phase more often than in content conversion, and handover is the part nobody scopes.

Teams can usually move content. The hard part is making sure the new system stays healthy after launch.

Use this playbook:

• Define scope: what is being migrated now vs later
• Assign owners: who approves content and who maintains the platform
• Set quality gates: linting, broken-link checks, and content review
• Plan redirects: preserve URLs users and search engines already depend on
• Train contributors: new workflows fail if only one person understands them

Migration is successful when the new platform is easier to run than the old one. That requires governance, not just scripts.