Currently there are no straight-up migration features. If you want to use Next-Gen features with existing issues right now, you will need to create a new Next-Gen project and move issues from your current Classic projects.
Several features are not available in Next-Gen projects as of this moment that you might expect from using Classic projects. Things like modifying a workflow - changing validators and post functions. I won't list everything out as this is constantly changing, but instead refer you to the Next-Gen roadmap: https://www.atlassian.com/roadmap/jira-software
If this changes in the near future I'll come back and update this answer.
Edit: We do have another post by one of our product managers which describes some of the features which are not currently available in Next-Gen projects.
Tyler points out in another answer that we have step-by-step documentation for moving issues between Classic and Next-Gen projects.
@Drew McCalmont This was the exact question in my mind when I got to know that there is no clear way of cloning the classic project to Next-Gen.
@Eaniel Deads Thank you for your response! Not having an option to "Copy" is really unfortunate. The first thing most of us would love to do is to migrate (Clone) classic projects to Next-Gen, If there's no option to do that directly in Next-Gen then the minimum expectation would be to be able to bulk copy the work items from classic to next-gen and not to move items. I would love to see Atlassian Team coming up with some solution for this BIG problem.
That or just auto upgrade all classic project to next gen and not tell anyone, kind of like how Atlassian changed our custom permissions so all jira-users can now create next gen projects. All of sudden we had all these new projects getting created by our end users. Not cool.
Same question - seems cruel to tease the new features (especially Roadmap) but not give clear instructions on how to try it out. I see a tutorial for migrating from next-gen to classic, but not the other way around. We're using a classic project and I'd like to give next-gen a spin, but do not want to start a new project from scratch, nor risk not being able to switch back to classic. Any suggestions?
Drew, honestly, some companies need a "swing and a miss" type release, to come to conclusions. Consider Snapchat failed re-design, which they stuck to until it was too late, or companies implementing a Beta feature no one used, and modifying UI in a way that causes strain to millions of existing users.
If you roll out "Roadmaps", you CANNOT just strip down all existing components of Jira for projects that simply want to have a roadmap.
I am biding my time on this one, and honestly, so far I don't like the direction of "flexible" = "nothing is pre-defined".
I rely on Jira as an "works out of the box" type of tool, which is sometimes too complex, but does the core work very well, with decent documentation and nice integrations.
To remove everything for a sleeker UI, not worth it.
From what I understand, the next gen JIRA experience is on a completely new tech stack. Therefore, most of the features and settings in the classic version are non existent in this newer Next Gen version. This leads to multiple discrepancies if you were to only "migrate" from classic to next-gen.
Unless the Atlassian Team implements exactly all the same features than the classic version, this "One-Click" migration will be impossible. That being said, what would be the purpose of creating an exact replica of what is currently the "Classic Version" ? I think the Atlassian Team are moving to a new vision of what JIRA could be, and that all the design changes will be reflected in the Next Gen Projects.
The only solution offered to "migrate" is to move and remap all the issues from a classic project to a next gen project. Keep in mind some advanced configuration could be lost in the process because the new version does not support them at the time.
TL;DR: The Next Gen Projects are currently a "leaned" version of Classic Projects and are partially compatible.
Here’s a link explaining the migration process and it’s pitfalls when going from classic to next-gen.
Does anyone know if this has certain requirements to work?
I tried this with a bunch of different scenarios. First I created a new next-gen project.
Then I tried creating a new classic project with a shared configuration of an existing (complex) one and even creating a new classic project from scratch.
I tried to move issues from any of the classic projects to a next-gen, but when I see the page to select the new project, only classic projects are listed.
Am I missing something? Is there some black magic or hidden settings involved to get things running?
I followed the step-by-step guide.
The Jira Software Cloud Team has been busy working on a simple, secure, and reliable way to integrate your build and deployment information from Jenkins with Jira Software Cloud. This means you don’t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events