.png&w=64&q=75){kind=small}
Migration
The Migrate tab moves HTML content from other HTML macro apps, and from legacy Server/Data Center macros, into HTML Macro+ for Confluence across a whole space. Each matching macro is replaced with an HTML Macro+ macro that holds the same HTML and opens in the editor.
To migrate a single page, or one macro, use the hover bar on the page instead. See Legacy Server/DC Macros.
Supported Sources
| Source app | Macros |
|---|---|
| Legacy HTML (Server/DC to Cloud) | html |
| Macro Toolbox for Cloud (Appfusions) | HTML Macro |
| Appfire – HTML Macro for Confluence | HTML Macro |
| Narva Software – HTML Tools | HTML & Iframe Embed, Advanced HTML & Iframe Embed (Live Preview), HTML from Page Attachment |
| Other | Any macro, by its key, on the Advanced tab |
The Advanced tab also lets you narrow the search to pages containing specific text.
Running a Migration
- Open the app settings and select the Migrate tab.
- Choose the Source App (and the macro, if the app has several).
- Choose the Space.
- Click Search Pages. A dialog lists every page in the space that uses the macro.
- Select the pages to migrate.
- Click Preview Changes (recommended). This is a dry run that saves nothing. The Changes column shows how many macros each page will get.
- Click Migrate Selected Pages. Progress is shown while each page is saved.
Each migrated page gets a new version labelled Migrated to HTML Macro for Confluence, so any page can be restored from Page history.
Skipped and Failed Pages
Unpublished changes. A page where someone has unpublished edits is skipped and shown as Unpublished changes in the preview. The draft still contains the old macro, so publishing it later would undo the migration. Ask the editor to publish or discard their draft, then run the migration again for that page.
Failed. A page fails when none of its macros can be converted safely, or when Confluence refuses the save. A common reason is page restrictions you aren't covered by. Remove the restriction or run the migration as a user who can edit the page.
The summary at the end shows how many pages were migrated, skipped and failed.
Requirements
- You must be a Confluence site administrator to open the app settings.
- The app needs permission to read and update pages and blog posts. The read permissions were added in v1.2.0: until a site administrator approves the app update under Settings → Apps → Manage apps, the tab explains that the migration is waiting for approval.