As of Jul 20, 2021, 3rd party macros don’t work within other macros at all. This is due to a change in Atlassian’s security policy and has nothing to do with the Navitabs app.
We strongly recommend that you address the following points before starting the migration:
Are you using any other macros (standard or 3rd party) within Navitabs macros?
Are you going to use the old (Legacy) editor or switch to the new Cloud editor in the future?
Based on this assessment, you might have to rework the content on your Server/DC instance. Try to use as few “exotic” macros as possible on your pages. Also, use the remaining macros separately on the page instead of nesting them within Navitabs macros.
Migrating Navitabs content
Completing the macro usage assessment and carrying out the changes necessary in your Confluence instance are the hard parts of the migration.
The process of migrating Navitabs Server/DC to Confluence Cloud is easy from a technical standpoint.
Migrating from Server/DC to the Legacy Cloud Editor
When migrating pages from Server/DC to Cloud, all content is transferred to the Legacy Cloud editor.
After the migration, all tabs are displayed and work properly in the frontend. No data is lost. There is one special case: the “Tab (Deprecated)” macro.
Tab (Deprecated): This appears on two occasions:
If you migrated old Localtab macros.
If you try to insert more tab macros on a migrated page that still uses the legacy editor.
The macro itself works fine and can also be edited, new content can be added, etc. However, the macro will not work in the new editor (read below).
Switching from Legacy to New Cloud Editor
If you want to change to the new cloud editor, you will have to replace all occurrences of the macro “Tab (Deprecated)” with the macro “Tab”. Otherwise, the data in the tabs will get lost during the transition.
As an alternative, you can get rid of the macros “Tab Group” and only work with the new Tabs macro with its own editor.