Migration checklist
Track engineering and documentation tasks for a 2.x → 3.x cutover.
Use this checklist when promoting a codebase and its documentation from the 2.x channel to 3.x. Check items only after they are verified in staging.
Engineering
- Bump composer constraints to ^3.0
- Run php atlas upgrade --from=2.x
- Update API clients to /api/v3
- Replace removed Collection helpers
- Enable config caching in production
Documentation
- Rewrite Quickstart for 3.x installers
- Publish a 3.x release snapshot
- Keep 2.x release available for historical URLs
- Add upgrade notes to the Version 3 space
Tip
Mark the documentation release as production only after the engineering checklist is complete. Shipping docs ahead of code breaks trust.
Print this page for war-room upgrades or copy the checklist into your issue tracker.
Updated Aug 5, 2026