Madcap Flare Import Issue

[Patrick Kilmartin]

Hi,

We use Madcap Flare 2025 to import a number of Confluence pages to Flare and it works well. 

We have recently hit an issue when importing from a particular Cloud Confluence space. 

Instead of showing an expected nested/hierarchical view of the space, the Flare importer now shows a number of random, unordered sites from the space.

Any idea what the issue might be? 

[Kristian Klima · Accepted solution]

Hi @Patrick Kilmartin and welcome to the Community.

Can you, pls, clarify what do you mean by 'showing unordered sites from the space'?

The hierarchy of Atlassian entities is (top down)

• Atlassian Organization
• Confluence Site
• Confluence Space
• Confluence Page

Presumably, importing individual pages works well, importing an entire space ... not so much.

(we can later talk about Confluence to Madcap as we migrated a ton of content from Madcap to Conluence ;) )

[Patrick Kilmartin]

Hi Kristian,

Apologies for the confusion. We don't import the entire space.

When we import from Confluence to Madcap, we select the space in the importer.

When selected, it displays a nested view of all the pages in the space, organized hierarchically as they would be in Confluence.

This means you can import a page (and all its child pages if required) to Madcap and it will be imported in the correct structure.

For some reason, recently, when we select this space. it shows an incomplete list of pages within the space with no nested structure.

So it should be like this:

APPLICATIONS SPACE

 - PAGE 1

     - page 1-a

     - page 1-b

     - page 1-c

     - page 1-d

     - page 1-e

     - page 1-f

- Page 2

Instead we see a incomplete, flat list of pages like this:

Page 2

page 1-c

page 1-f

Hope that makes sense. 

I suspected it was a permissions issue but we can view and edit all the pages in Confluence itself. 

Please feel free to ask any questions about importing from Confluence to Madcap. 

[Kristian Klima]

Hi Patrick,

Permissions can be a culprit but perhaps not in the most obvious form.

If you can see the page, it doesn't mean that the importer tool can see the page. So I'd check if there are any differences between pages that work and those that don't.

Pages may have specific restrictions applied, they could contain excerpts / pages (via include macros) from other spaces.

The importer might have a problem with that. And, a problematic page is a parent to other pages, it might be excluded from the import, thus breaking any hierarchy that exists in Confluence.

Another possible culprit is content the importer cannot process... 

As a workaround, you can try copying the offending page tree section to a new space, check for any idiosyncracies and verify permissions/restrictions, missing content*, and try importing content from that new space.

*if you find any of those, it can indicite permission/special content.

[Patrick Kilmartin]

Thanks!

Will try this. 

What's strange is that it was working fine until recently so perhaps we need to see if something has changed in Confluence admin. 

[Patrick Kilmartin]

Thanks again, Kristian.

I:

• tried the import as an admin user - no difference
• checked for restricted pages within the space - there wasn't any

What finally seems to have worked is the suggestion of another space.

I copied the content to a new space. Now I can see all of it in the importer, organized in the expected nested structure.

I will just move the content to this space and fingers crossed that this will permanently address the issue.

[Kristian Klima]

Hi @Patrick Kilmartin 

I'm glad you found something that worked.