GitHub has announced plans to retire Projects (classic), the company's original project management tool. The deprecation will occur on different schedules depending on the deployment platform—GitHub.com, GitHub Enterprise Server, and the REST API will each follow their own timeline.
The company introduced an overhauled Projects experience in July 2022, built on top of GitHub Issues. Since its launch, the modernized version has gained capabilities including roadmaps, mobile access, organization-level templates, status updates, and support for unlimited work items.
Users with existing classic projects can initiate migration by selecting the Start migration option displayed in a banner at the top of their classic project page.
GitHub.com Timeline
- May 23, 2024: Migration banner appears on classic projects with migration tools available; creation of new classic projects becomes unavailable
- August 23, 2024: Projects (classic) officially sunset; unmigrated projects automatically convert to new projects
Several important caveats apply to the August 23, 2024 migration event. If an organization has disabled Projects at the organizational level, classic projects within that organization will not be migrated. The migration process will only transfer cards that have been modified within the preceding year. Webhooks for Projects v2 will not trigger during the migration of newly created projects. Following the August 23 sunset date, the REST and GraphQL APIs will technically still allow updates to classic Projects, though GitHub strongly advises against this approach since changes will not synchronize with the migrated v2 Projects.
GitHub Enterprise Server Timeline
- August 27, 2024: Projects (classic) marked for deprecation in version 3.14; migration banner and tooling made available
- June 3, 2025: Projects (classic) removed in version 3.17