Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-82881

Preserve Table Formatting and Width When Migrating from Legacy to Cloud Editor

XMLWordPrintable

    • 1
    • 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.

      Summary

      When migrating pages from the legacy Confluence editor (Fabric) to the new Confluence Cloud editor, tables lose their original formatting, width, and visual fidelity. The new editor enforces a narrower page and table width, which distorts tables and impacts readability and usability.

      Issue Detail:

      • After conversion to the new editor, tables are constrained by a fixed or full-width layout, but neither option matches the original wide format available in the legacy editor.
      • The new editor’s default width is significantly narrower, causing table content to wrap, overflow, or become misaligned, which distorts the intended layout.
      • The more content a table contains, the more formatting issues appear after conversion, making it increasingly difficult for users to read and interpret the information.

      Screenshots

      • The "Legacy Editor" screenshot shows a wide table and proper alignment before migration.
      • The "After Conversion" screenshot shows the same table with loss of formatting making it hard to read.

      Request
      Please enhance the Confluence Cloud editor's migration/conversion process to:

      • Accurately preserve table width, cell formatting (alignment), and multi-line content.
      • Ensure the visual appearance and usability of tables remain consistent with the legacy editor after conversion.
      • Provide an option to retain the original table layout or offer more flexible width settings beyond the current fixed/full-width options, so that tables are not forced into a narrower format.

      Business Impact
      This feature is critical for customers who rely on complex tables for documentation, as loss of formatting and layout fidelity reduces the clarity and effectiveness of migrated content.

        1. After conversion.png
          After conversion.png
          78 kB
        2. Legacy Editor.png
          Legacy Editor.png
          63 kB

              Unassigned Unassigned
              c2d78d0f7204 Amin A.
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: