Yes. You can migrate your existing Projects (classic) to the new GitHub Projects through a new feature preview.

How it works:

• We?ll create a new project and copy all of the data from your existing project (classic) board to the new one.
• Once the data is copied, you can use the new project with all the new capabilities.
• Once the new project is ready, we will prompt you to close your ?old? project, as the old project is not kept in sync.

As teams and projects grow, how we work evolves. Tools that hard-code a methodology are too specific and rigid to adapt to any moment. Often, we find ourselves creating a spreadsheet or pulling out a notepad to have the space to think. Then our planning is disconnected from where the work happens.

The new Projects connect your planning directly to the work your teams are doing and flexibly adapt to whatever your team needs at any point. Built like a spreadsheet, project tables give you a live canvas to filter, sort, and group issues and pull requests. You can use it, or the accompanying project board, along with custom fields, to track a sprint, plan a feature, or manage a large-scale release.

We all need a way to plan our work, track issues, and discuss the things we build. Our answer to this universal question is GitHub Issues, and it?s built-in to every repository. GitHub?s issue tracking is unique because of our focus on simplicity, references, and elegant formatting.

With GitHub Issues, you can express ideas with GitHub Flavored Markdown, assign and mention contributors, react with emojis, clarify with attachments and videos, plus reference code like commits, pull requests, and deploys. With task lists, you can break big issues into tasks, further organize your work with milestones and labels, and track relationships and dependencies.

We built GitHub Issues for developers. It is simple, adaptable, and powerful.

All users have access to the free tier of GitHub Issues and Projects. For more information about paid tiers, see our pricing page.

Historical charts are available for all Enterprise organizations and are currently in Preview for organizations on Team plans.**

**Subject to change as we add future capabilities.

Yes! GitHub Enterprise Server (GHES) support follows our regular cadence of one to two quarters before enabling the on-premises functionality.