Thank you for your feedback! You can now migrate your old templates to the new editor. For more details, please see: https://community.atlassian.com/t5/Confluence-articles/Convert-your-old-templates-to-the-new-editor/ba-p/1477117

We are also waiting for page template migration to the new editor. Having to recreate them all AND most of all having to update every single page that contains a Create from Template macro for every single template is not an option. 

Thanks for letting us know.

We were very disappointingly told by Atlassian support that there is no way to upgrade the templates to the new editor format. and no plans on adding this functionality. We were told that we can either keep using the old editor for existing templates or recreate our templates from scratch using the new editor. Awful customer support, IMO, and ridiculous that the same functionality used to upgrade any page to the new editor can't be used to upgrade a user created template to the new editor. Oh, well. We are now in process of re-creating our templates. Very disappointing that Atlassian didn't consider this an important feature to roll out with the new editor.

Any news on this? When trying to add the new elements to existing templates, it's still using old editor tools. Thanks.

Any update on the page by page transition will be live?

 Would also like to know when page by page or space by space transition to the new experience is possible in order to streamline my department and not teach everyone two editors. Thanks and stay healthy! 

In discussing this with our confluence admin, this migration option for getting pages moved up to the new editor seems to still be a site-wide choice instead of page-by-page. Is that accurate or is the page-by-page migration option covered by this feature request rolling out now?

It's rolling out to customers now, but hasn't hit my instance yet: https://confluence.atlassian.com/confcloud/confluence-cloud-editor-roadmap-967314556.html#ConfluenceCloudEditorRoadmap-pageconversion

https://confluence.atlassian.com/cloud/blog/2020/02/atlassian-cloud-changes-jan-27-to-feb-3-2020#AtlassianCloudchangesJan27toFeb3,2020-confluence

When will the conversion of a page using the New Editor be available?

I totally agree. The fact that they are forcing migration before having this feature (and hence no real way to test the migrations) is not a palatable solution. I recommend that Atlassian re-think this and delay migrations until they have had this feature for at least a month.

Definitely need this feature - bouncing around from one look/feel to another isn't the best experience.

This getting close to release? Would be great to have a button when editing pages that just allows it to be migrated. Migrating the whole instance seems a bit risky

As stated in the text that was provided with the post above (remove the dot at the end of the link) 
https://community.atlassian.com/t5/Confluence-articles/How-we-roll-out-the-new-editor-in-Confluence/ba-p/1204966
this seems to be planned to release November, so right around the corner for single pages:

Migrations Phase 1 - Users can start to migrate their existing pages*

*As of November 2019 this capability is still in development and will soon start to get rolled out to customers and will also gradually become available to all customers.

We'd really appreciate a feature to convert selected pages to the next experience, converting all pages at once sounds risky. Since you already have a converter, is there an ETA for this? This ticket was opened in March.

Hi all,

Please have a look at our recent related community post here: https://community.atlassian.com/t5/Confluence-articles/How-we-roll-out-the-new-editor-in-Confluence/ba-p/1204966.

Thanks,

Avinoam

Same question as Nithin....

> We're working to offer in the future an option to migrate each page proactively without having to opt in your entire instance.

Do you have a ticket to track this feature?

Hi Avinoam,

> We're working to offer in the future an option to migrate each page proactively without having to opt in your entire instance.

Do you have a ticket to track this feature?

Hi lschumacher1,

Great questions. All the things you mentioned, and more, are either bugs we're working on actively or on our roadmap to add. Our top focus is quality and we're adding more fixes and new features all the time.

Hi Avinoam,

Thank you for your answer. We will need to think about this and decide. One thing I thought of to ask about is whether there will be bug fixes/enhancements to the new editing experience in the near future (and when do you think that will be). These are things I've submitted tickets about before. 1) In an Action Item, if you put tomorrow's date it changes to "today" and if you select the date two days from today it changes to "tomorrow." It was acknowledged that this is a bug and I wonder if it's going to be fixed anytime soon. 2) Tables in the new editing experience don't allow sorting by column. This pretty much makes the tables in the new experience impractical. 

So maybe we want to wait until these are fixed if it's going to be soon. Please advise!

Thanks.

Linda

lschumacher1 - thanks for adding this suggestion! Here's a quick rundown of this:

1. You can opt in your instance to have all your pages migrated to the new editor here https://support.atlassian.com/contact/?_ga=2.81838550.1783106099.1554138526-945426334.1525714588#/. This means every existing page, including templates will be migrated as you edit the page.
2. We're working to offer in the future an option to migrate each page proactively without having to opt in your entire instance.

Any templates that we can migrate will convert to the new editor but if a template has content that isn't supported in the new editor it will remain in the old editor unless you remove the content that is unsupported (i.e. a table nested inside a table for example).

I hope this answer helps!

Thanks,

Avinoam

Senior Product Manager, Confluence Cloud