FAQ: レガシー エディターの廃止について
主な廃止日
Atlassian is taking a phased approach to deprecating the legacy editor to ensure a smooth and successful transition for all customers. The top priorities are to remove blockers from the conversion process—so your content remains intact—and to close key gaps between the legacy and cloud editors before the deprecation is complete.
Phase 1 (January 21, 2026): New pages can't be created in the legacy editor, including copying legacy pages or creating new pages from legacy editor templates.
Phase 2 (rolling out from January 21 - February 18, 2026): Viewing or editing a legacy page will automatically convert it to the cloud editor.
Phase 3 (April 1, 2026): The legacy editor is fully deprecated; all content is viewed and edited in the cloud editor and pages can't be reverted back to legacy editor.
よくあるご質問
質問 | レスポンス |
|---|---|
Converting pages to cloud editor | |
変換前にページが対象かどうかはどうすればわかりますか。 | Eligible pages are those that can be converted to the cloud editor without displaying any "unsupported" content after conversion. These pages are fully compatible with the cloud editor, allowing users to view and edit them seamlessly. The introduction of the legacy content macro has made a lot more pages eligible and we’re actively expanding support for additional use cases over the next quarter. 対象ページを特定する
対象外のページ: 従来のエディター ページに変換できないコンテンツがある場合、クラウド エディターに変換するプロンプトは表示されません。それでも変換を試みる場合は、コンテンツが失われる可能性があるという警告が表示されます。 詳細については、ページをクラウド エディターに変換する方法に関するページをご覧ください。 |
レガシー エディターからクラウド エディターにページ変換できるユーザーを管理する方法はありますか? | ページを編集する権限を持つユーザーなら誰でも、レガシー エディターから新しいクラウド エディターに変換できます。現時点では、このアクションを特定のユーザーに制限する方法はありません。 |
Can you disable the “Time to convert your page” prompt that encourages users to “Convert page” to get the latest editor experience? | This prompt cannot be disabled. This prompt only appears on pages eligible for conversion to Cloud, where no "unsupported" content will be displayed after conversion. These pages are fully compatible with the cloud editor, allowing users to view and edit them seamlessly. he prompt serves two important purposes: it informs users which pages can be converted and it reminds them about the upcoming deprecation of the legacy editor. |
当社のコンテンツはサードパーティ マクロに大きく依存しています。レガシー エディターが廃止された後も、これらのマクロは引き続き正常に機能しますか。
| Many third-party macros on legacy pages, including those with nested macros, will be converted automatically to the cloud editor using our Legacy Content Macro. However, because the third-party ecosystem is so broad, there may be some edge cases that are not fully addressed by our solutions. If you encounter issues with a specific third-party macro, we recommend reaching out directly to the app developer and also providing feedback to us. |
Deprecation timeline and phases | |
当社には多くのレガシー ページがあり、廃止のタイムラインが心配です。ページをクラウド エディターに変換するうえで有利なスタートを切るにはどうすればよいですか。 | Site and space admins can enable auto-conversion settings at any time to help streamline the transition for their teams. Auto-conversion applies to eligible pages—those that can be converted to the cloud editor without unsupported content. Once converted, these pages can be seamlessly viewed and edited in the cloud editor. サポート対象外のコンテンツを含むページは、サポートが提供されるまでレガシー エディターに残り、サポートが提供された時点で変換の対象となります。自動変換がすでに有効になっている場合は、それ以上のアクションは必要ありません。追加のユース ケースにサポートが拡大されるまでお待ちください。 To learn more about converting pages, visit: |
What is happening in phase 1 of the deprecation? (January 21, 2026) | What changes You will no longer be able to create new pages in the legacy editor. This includes:
What you’ll see
|
What is happening in phase 2 of the deprecation? (rolling out from January 21 to February 18, 2026) | What changes
Please note: If your organization has multiple sites, auto-convert may be enabled at different times. You can manually enable auto-convert earlier if you wish. Please refer to the question above: “How can I get a head start on converting our pages to the cloud editor?” What you’ll see
Recommended action: Use phase 2 as your final window to review and adjust any especially complex or critical content. |
What is happening in phase 3 of the deprecation? (April 1, 2026) | What changes
What you’ll see
|
What is the difference between phase 2 and phase 3 of the deprecation? | When phase 2 begins, viewing or editing pages will occur in the cloud editor. You will see an in-product modal displayed when phase 2 is enabled for your site. From that point forward:
The main change in phase 3 is that the legacy editor will be fully retired:
While individual pages can still be reverted if necessary until phase 3, we strongly encourage teams to fully adopt the cloud editor in phase 2 to avoid last‑minute disruption and to take advantage of ongoing improvements and support in the cloud editor. |
Can we get an extension or delay the deprecation? | We’re unable to offer individual extensions or delays for the deprecation, as this is a global change that applies to all customers according to the published timeline. We recognize this is a significant change and we’re here to support you with any questions or concerns as you prepare for the transition. |
クラウド エディターで一部のページに機能の差異があることが判明した場合、それらのページをレガシー エディターに残すことはできますか? | In phase 2, pages will be automatically converted, but you’ll still have the option to individually revert them to legacy editor if needed. You can do so by clicking on More actions (•••) menu and selecting Revert to legacy editor. Once phase 3 begins, all pages will transition to the cloud editor, and reverting will no longer be possible. While individual pages can still be reverted if necessary until phase 3, we strongly encourage teams to fully adopt the cloud editor in phase 2 to avoid last‑minute disruption and to take advantage of ongoing improvements and support in the cloud editor. |
What happens to templates that use the legacy editor? | We’re committed to making the transition as smooth as possible for customers with legacy editor templates. By the start of Phase 1 of the deprecation, templates that use the legacy editor will be convertible to the cloud editor. Once Phase 1 begins:
|
Auto-conversion | |
当社には多くのレガシー ページがあり、廃止のタイムラインが心配です。レガシー エディターの廃止に備えて、何かアクションを講じる必要はありますか。 | You are not required to take specific action for this deprecation, as our solutions are designed to enable a smooth, automatic conversion. We’re focused on ensuring the transition to the cloud editor is as straightforward and smooth as possible. Eligible legacy pages will be automatically converted to the cloud editor according to our deprecation timeline. Your content will remain viewable and editable after the deprecation, even without manual intervention. While no action is required for most customers, if you have especially complex legacy pages, we encourage you to convert eligible pages early and share feedback—your input helps us refine our solutions and support you better. |
How does auto-convert work with users who have view-only access? | When auto-convert is enabled, pages will be viewed and edited the cloud editor. Viewing a page, even with view-only access, will view the page in the cloud editor. |
How does reverting pages work in phase 2? Will it auto-convert again the next time the page is viewed? | You can revert an auto-converted page clicking on More actions (•••) menu and selecting Revert to legacy editor. Pages that are reverted to the legacy editor during phase 2 will remain in the legacy editor and will not be auto-converted again until phase 3. At the start of phase 3, all remaining legacy pages will be automatically converted to the cloud editor. If you revert an auto-converted page back to the legacy editor during phase 2, you’ll need to manually convert it to the cloud editor again if you want to convert before phase 3. While individual pages can still be reverted if necessary until phase 3, we strongly encourage teams to fully adopt the cloud editor in phase 2 to avoid last‑minute disruption and to take advantage of ongoing improvements and support in the cloud editor. |
Identifying legacy pages (space admin tool) | |
スペースまたはサイト内のページのうち何ページがレガシー エディターを使用しているか、またはサポート対象外のコンテンツを含んでいるかを確認するにはどうすればよいですか。 | Space admins can now quickly view and export a CSV list of all legacy pages and templates in their space. This makes it easier to plan for the upcoming deprecation of the legacy editor. This addresses two feature suggestions: This report is designed to help you understand the scope of remaining legacy content. The export is a reporting tool only, it does not convert any pages by itself. For more details, visit our page on exporting a list of legacy pages. |
What do the statuses in the legacy content space admin tool mean? What does ‘Unsupported’ or ‘Error’ mean? |
We are continuing to address unsupported use cases to ensure that, by the time deprecation begins in January, nearly all content will be eligible for conversion. For the small number of pages that remain unsupported, please note that the unsupported portions of these pages will still be viewable (but not editable) after the legacy editor is deprecated. For more details, visit our page on exporting a list of legacy pages. |
We have auto-convert enabled, why does it still show ‘Supported’ pages in the CSV report? | If auto-convert is enabled, users will view these pages in the cloud editor. In the backend, they’re still marked as legacy until edited and published. These auto-converted pages will still appear in this report. If auto-convert is enabled, you can treat pages with the "supported" status as auto-converted. There is no need to manually re-publish every page. |
How can I get a report of legacy pages across my entire site, instead of for an individual space? | While we are committed to addressing bugs that impact the usage of the tool, we do not have plans to implement additional feature suggestions to the legacy content admin tool at this time. We prioritized based on customer feedback, particularly through jira.atlassian.com feature suggestions. While we recognize that a site-level tool would be helpful for some, the majority of requests focused on space-level reporting. At this time, we do not plan to build a site-wide version of the tool. |
Feature suggestions and feedback | |
フィードバックや懸念事項を共有するにはどうすればよいですか。 | フィードバックは次の方法で共有できます。
|
Which legacy editor features will be supported in the cloud editor and which ones will not be supported? | Please refer to the published community post to better understand which features gaps will be supported, which will not, and which are still under evaluation. Not every feature of the legacy editor will exist in exactly the same form in the new cloud editor. To provide some clarity, we’ve grouped items into three categories:
Where a gap is known and tracked, we provide public Jira issues or documentation so you can follow progress. In other cases, there may be workarounds in the new editor, but they are not always one‑to‑one replacements for legacy behavior. |
クラウド エディターでは使用できないレガシー機能 Why are some features from the legacy editor not available in the cloud editor, and when will missing features be added?
| We’re actively working to address the most critical gaps between the Legacy and cloud editor so that, by the time of deprecation, nearly all pages can be converted seamlessly with minimal manual effort. Some features from the cloud editor have intentionally not been replicated in the cloud editor due to technical limitations and our focus on building a modern, scalable editing experience for the cloud. ワークフローにおいて特定の機能が重要となる場合は、jira.atlassian.com の Confluence Cloud の提案で検索してください。提案に対する投票とコメントは、お客様にとって最も重要な改善をアトラシアンが優先順位付けするのに役立ちます。 |
Legacy content macro | |
Do you have plans to deprecate the legacy content macro? | No, the legacy content macro is a long-term solution designed to support legacy content that isn’t natively supported in Confluence Cloud. It plays a critical role for users working with the legacy editor in Cloud, as well as for customers migrating from Data Center to Cloud. At this time, we do not have plans to deprecate the legacy content macro, as it remains essential for bridging the gap between Data Center and Cloud experiences. In the future, when we release native support for features that currently use the legacy content macro, the legacy content macro will automatically update to use those new native features, without any manual action needed. |
Can I view a list of pages using the legacy content macro? | Currently, there isn’t a built-in way to view a list of pages that use the legacy content macro. If this feature would be valuable to you, please vote for the related feature suggestion. Adding your vote and comments helps us understand your needs and prioritize improvements. |
What are limitations of working with the legacy content macro? | The legacy content macro was designed to ensure content could be migrated and edited, but does not replicate the exact experience of the legacy editor or native editing in the cloud editor. There are some important limitations to be aware of when editing content within the legacy content macro (LCM):
また、独自のレガシー コンテンツ マクロをクラウド エディターに追加することもできません。これは Confluence の自動ページ変換プロセスでのみ使用されます。 共同編集: 新しいページはクラウド エディター ページのため、複数のユーザーが同時に編集できます。ただし、従来のコンテンツ マクロと共同編集を使用すると、データの損失など、予期しない結果が生じる可能性があります。公開前に、編集するユーザーが 1 人だけであることを確認してください。 |
この内容はお役に立ちましたか?