• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      Currently, if we want to convert a number of pages from the legacy editor to the new one, we must do it manually page by page.

      Suggested Solution

      Make it possible for the users to convert pages in bulk.

      Workaround

      Manually convert page by page.

            [CONFCLOUD-70955] Bulk convert pages to the new editor

            Steven Bao added a comment -

            Hey everyone, the space option has been rolled out to all tenants and we are in the middle of rolling out the site option which should be available to all tenants by early August.

             

            As a result we will close this ticket as done.

             

            Thanks for your patience on this feature and check our our community post! https://community.atlassian.com/t5/Confluence-articles/Migrators-you-can-now-bulk-convert-legacy-editor-pages-to-the/ba-p/2432943

            Steven Bao added a comment - Hey everyone, the space option has been rolled out to all tenants and we are in the middle of rolling out the site option which should be available to all tenants by early August.   As a result we will close this ticket as done.   Thanks for your patience on this feature and check our our community post! https://community.atlassian.com/t5/Confluence-articles/Migrators-you-can-now-bulk-convert-legacy-editor-pages-to-the/ba-p/2432943

            Steven Bao added a comment -

            Hey everyone, we've begun rollout of the ability to convert eligible pages on a space level. You'll be able to find this in your space settings under Manage space -> Convert pages.

            Don't panic if you don't see this yet, as we are progressively rolling out through the rest of July. Site level conversion will also be available later in July.

            Cheers,

            Steven

             

            Steven Bao added a comment - Hey everyone, we've begun rollout of the ability to convert eligible pages on a  space level. You'll be able to find this in your space settings under Manage space -> Convert pages. Don't panic if you don't see this yet, as we are progressively rolling out through the rest of July. Site level conversion will also be available later in July. Cheers, Steven  

            Steven Bao added a comment -

            Hey all, this is a feature that is committed on our public roadmap and wrapping up development: https://www.atlassian.com/wac/roadmap/cloud/Bulk-legacy-to-new-editor-conversion?search=bulk&p=0e3e7a65-61

            We are preparing to start rolling out both space and site level functionality by end of July - look out for a further community post and update to this ticket.

            Cheers,

            Steven

            Steven Bao added a comment - Hey all, this is a feature that is committed on our public roadmap and wrapping up development: https://www.atlassian.com/wac/roadmap/cloud/Bulk-legacy-to-new-editor-conversion?search=bulk&p=0e3e7a65-61 We are preparing to start rolling out both space and site level functionality by end of July - look out for a further community post and update to this ticket. Cheers, Steven

            I can't believe this is not standard functionality. 

            Dimitri Cools added a comment - I can't believe this is not standard functionality. 

            Shivkumar Kachapur added a comment - https://getsupport.atlassian.com/browse/CES-16005

            Dear Atlassian

            Please could you action this - it's costing us a lot of time and trouble, and hampering our cloud take up (users don't get the benefits of the cloud page editor).

            Thank you

            Danielle Green added a comment - Dear Atlassian Please could you action this - it's costing us a lot of time and trouble, and hampering our cloud take up (users don't get the benefits of the cloud page editor). Thank you

            Dear Atlassian Team:

            This is very important, we are conducting a large DC to Cloud migration with around 500,000 pages and getting this done on a page by page basis is just not doable. I want to share propose that we can do this at space level, by selecting the spaces that are not converted.

            Please do not wait that much to implement this. 

            Cheers

            Claudio

            Claudio Ombrella | Digilac - Gold Solution Partner added a comment - Dear Atlassian Team: This is very important, we are conducting a large DC to Cloud migration with around 500,000 pages and getting this done on a page by page basis is just not doable. I want to share propose that we can do this at space level, by selecting the spaces that are not converted. Please do not wait that much to implement this.  Cheers Claudio

            Matt added a comment -

            My pages created through v2 API are being created using the old editor. Is there a markup I need to make to ensure it uses the new editor?

            Matt added a comment - My pages created through v2 API are being created using the old editor. Is there a markup I need to make to ensure it uses the new editor?

            Elisha Ritcey added a comment - - edited

            I'd prefer space by space, or page tree by page tree.

            We tend to have several docs in one space, so it would be useful to do one document at a time (i.e., a page tree).

            Site-wide honestly sounds scary to me because generally, we have a lot of formatting problems to work out after converting anything to the new editor. Converting hundreds of docs to the new editor at once would mean thousands of pages that would need manual editing to repair bad formatting.

            For additional context, we have to export our documents to PDF, often at a moment's notice, so the potential for a bottleneck is huge. If a document needs to be exported immediately but has been converted to the new editor as a result of a site-wide conversion, and we didn't have time to fix the formatting, it would be a huge problem.

            Space by space or page tree by page tree allows a greater level of control, while offering a massive improvement to page by page.

            Elisha Ritcey added a comment - - edited I'd prefer space by space, or page tree by page tree. We tend to have several docs in one space, so it would be useful to do one document at a time (i.e., a page tree). Site-wide honestly sounds scary to me because generally, we have a lot of formatting problems to work out after converting anything to the new editor. Converting hundreds of docs to the new editor at once would mean thousands of pages that would need manual editing to repair bad formatting. For additional context, we have to export our documents to PDF, often at a moment's notice, so the potential for a bottleneck is huge. If a document needs to be exported immediately but has been converted to the new editor as a result of a site-wide conversion, and we didn't have time to fix the formatting, it would be a huge problem. Space by space or page tree by page tree allows a greater level of control, while offering a massive improvement to page by page.

            Banupriya Jayakumar added a comment - https://getsupport.atlassian.com/browse/MOVE-113055  

              sbao Steven Bao
              gtworkowski Guilherme T (Inactive)
              Votes:
              234 Vote for this issue
              Watchers:
              153 Start watching this issue

                Created:
                Updated:
                Resolved: