Migrate from Aura Content Formatting

You can migrate from the Aura Content Formatting app to Capable.


#Cards

The Aura Cards macro (aura-cards) is migrated to Capable Cards.

#What the migrator does

  • Converts Aura classic cards to Capable Cards

  • Card titles, descriptions, and background colours are preserved

  • Page links and URL links are mapped to Capable link types

#What is not migrated

  • Card images are not included (Aura cards support images, Capable Cards do not show images for this migration)

  • Flip card and hover card variants are not supported — only classic cards are migrated

  • Custom icon settings are not preserved

#Support level

Partial — Classic card content and links are migrated. Images and advanced card types (flip, hover) are not carried over.

Follow the instructions on Using the migration assistant to run the migrator.


#Buttons

The Aura Button macro (aura-inline-button) is migrated to Capable Button.

#What the migrator does

  • Converts inline Aura buttons to a Capable Buttons macro

  • Button labels are preserved

  • Page links and URL links are mapped correctly

  • Consecutive buttons in the same paragraph are grouped into a single Capable Buttons macro

#What is not migrated

  • Button colours, hover effects, and shadow styles are not preserved

  • Icon choices are not carried over

  • Button size and shape (rounded, square) are not preserved

#Support level

Partial — Button text and links are migrated. Visual styling is not carried over.

Follow the instructions on Using the migration assistant to run the migrator.


#Background / Hero Section

The Aura Background macro (aura-background-image) is migrated to Capable Background or a native Confluence panel.

#What the migrator does

  • When a background image is present, the macro is converted to a Capable Background macro with the image URL, positioning, and height settings preserved

  • When no background image is present, the macro is converted to a native Confluence panel with the background colour

  • Body content inside the background is fully preserved

#What is not migrated

  • Exact padding and spacing values may differ slightly

  • Background colour overlay opacity is set to a default value

  • Custom alignment combinations may not map precisely

#Support level

Partial — Image backgrounds and body content are migrated. Some visual fine-tuning options are not carried over.

Follow the instructions on Using the migration assistant to run the migrator.


#Panel

The Aura Panel macro (aura-panel) is migrated to native Confluence panels.

#What the migrator does

  • Maps the Aura panel icon to a Confluence panel type:

    • Error icon (faTimesCircle) becomes an error panel

    • Check icon (faCheckCircle) becomes a success panel

    • Info icon (faInfoCircle) becomes an info panel

    • Warning icon (faExclamationTriangle) becomes a warning panel

    • Panels without a recognised icon become a custom panel with the border colour preserved

  • The panel headline text is added as a bold heading inside the panel

  • Body content is fully preserved

#What is not migrated

  • Custom panel background colours and shadow effects

  • Font size and weight customisations in the headline

  • Border radius and width settings

#Support level

Partial — Panel type and content are migrated. Exact visual styling is not carried over.

Follow the instructions on Using the migration assistant to run the migrator.


#Tabs

The Aura Tab Group macro (aura-tab-collection with child aura-tab) is migrated to Capable Tabs.

#What the migrator does

  • Converts the Aura tab group into a Capable Tabs macro

  • Each Aura tab title is preserved as a Capable tab title

  • Content between tab markers is placed inside the corresponding tab

#What is not migrated

  • Tab styling (active colour, hover colour, font settings) is not preserved

  • Tab direction (vertical/horizontal) defaults to horizontal

#Support level

Full — All tab content and titles are migrated.

Follow the instructions on Using the migration assistant to run the migrator.


#Expand

The Aura Expand Group macro (aura-expand-group with child aura-expand) is migrated to native Confluence expand blocks.

#What the migrator does

  • Each expand section becomes a native Confluence expand block

  • Expand titles are preserved

  • Content between expand markers is placed inside the corresponding expand

#What is not migrated

  • Expand group styling (shadow, design theme, highlight colour, icon variant) is not preserved

#Support level

Full — All expand content and titles are migrated.

Follow the instructions on Using the migration assistant to run the migrator.


#Title

The Aura Title macro (aura-pretty-title) is migrated to a native Confluence heading.

#What the migrator does

  • Converts the title text to a native heading element

  • Maps the Aura font size to a heading level:

    • 36px or larger becomes h1

    • 28px or larger becomes h2

    • 22px or larger becomes h3

    • Smaller sizes become h4

#What is not migrated

  • Exact font sizes, colours, and line heights

  • Text alignment and font weight customisations

  • Custom light/dark mode colours

#Support level

Partial — Title text is migrated. The heading level is approximated from the font size; exact visual styling is not preserved.

Follow the instructions on Using the migration assistant to run the migrator.


#Divider

The Aura Divider macro (aura-divider) is migrated to a native Confluence horizontal rule.

#What the migrator does

  • Replaces the Aura divider with a standard Confluence horizontal rule

#What is not migrated

  • Divider text labels, icon decorations, and border styling

  • Custom colours and border width

#Support level

Full — The divider is fully replaced with a native horizontal rule.

Follow the instructions on Using the migration assistant to run the migrator.


#Status

The Aura Status macro (aura-status) is migrated to a native Confluence status lozenge.

#What the migrator does

  • Finds the active status row and converts it to a native Confluence status lozenge

  • Maps the background colour to the closest Confluence status colour (neutral, blue, red, green, yellow, purple)

#What is not migrated

  • Multiple status rows — only the active row is migrated

  • Exact custom colours are approximated to the nearest Confluence status colour

  • Status size and uppercase settings

#Support level

Partial — The active status is migrated. Multiple rows are reduced to a single lozenge; exact colours are approximated.

Follow the instructions on Using the migration assistant to run the migrator.


#Progress Bar

The Aura Progress macro (aura-progress) is migrated to one or more Capable Progress Bar macros.

#What the migrator does

  • Each progress bar in the Aura macro becomes a separate Capable Progress Bar

  • Progress percentage and bar colour are preserved

  • A bold label is added above each bar if a label was set

#What is not migrated

  • The grouped visual layout of multiple bars in a single container

  • The overall progress summary bar

  • Bar shadow and rounded style settings

  • Background track colour customisations

#Support level

Partial — Individual progress bars are migrated. Bar grouping and the overall progress indicator are not preserved.

Follow the instructions on Using the migration assistant to run the migrator.


#LaTeX

The Aura LaTeX Math macro is migrated to Capable LaTeX.

#What the migrator does

  • Extracts the LaTeX expression from the Aura Forge macro

  • Converts the inline LaTeX to a Capable LaTeX block macro

#What is not migrated

  • Inline rendering (the Capable LaTeX macro renders as a block element)

  • Anchor display settings

#Support level

Full — LaTeX expressions are fully migrated.

Follow the instructions on Using the migration assistant to run the migrator.


#Unsupported macros

The following Aura macros are not currently supported for migration. If you use any of these macros, they will remain as-is on your pages after migration:

Macro

Notes

Child Tabs

Nested tab structure; requires sample data to implement

Countdown

Timer/countdown functionality; no Capable equivalent

Embed

External content embedding; requires sample data to implement

HTML

Custom HTML rendering; requires sample data to implement

Numbered Headings

Auto-numbered heading hierarchy; requires sample data to implement

Dynamic Content

Dynamic data display; requires sample data to implement

If you need migration support for any of these macros, please contact support with a sample page containing the macro so we can evaluate adding support.