Thank you guys.

I'm migrating content from another tool.
The content of these documents is of the same type: tons of small tables with reference data (command-value-example)...no images or special text, no lists, no links...the table sizes vary are between 2-3 columns and 4-15 rows. Each table comes with a Heading as section title that would become page title in wiki, no table caption and no text (paragraph) longer than a few sentences (and that only in a very few places).

What I usually do is the following:
1. Open the FM file, and 'Save As' rtf.
2. Open the rtf file in Word and 'Save as' docx.
3. Remove all Headers & Footers.
4. Line by line reformat the whole docx and apply the MS Word's built-in default styles. All text will be formatted to Normal, all Headings formatted using the built-in heading styles...
5. Import the docx to wiki

Ususally I have no problem with the execution... cca 750 pages of the 905 pages long reference document I've been working on has been successfuly migrated this way, and today morning I continued with a few, 10-50 pages long document, again, with success regarding importing.

Then about noon (CET) it started to throw bugs at me...

• first the imports were succesful but the content disappeared (not visible in Reorder or Hidden, Orphan, etc - nowhere).
• Then I imported again, this time I got the message that 'a page with the same title already exists in this workspace, choose another title for this page' (not exactly this, but sg like this).
• Then all exports failed, whatever I tried...e.g. splitting the content to chapters, making the content less 'deep' so we have less Heading levels (I only allow 3 usually, this time I restricted this to 2 Heading levels), also tried to create a doc file with 'Save As' from the docx, or create new word files from scratch, etc.

Nothing worked (and we can't access the logs, so I only have the error message to show you - pls find attached).

A few of my trial-error couplings ended up with me creating a separate space for the Buggy imports, because in spite the error message, pages started to show up and they were WEIRD, I mean it didn't make sense: the import created one page per CELL. I have 69 tables in that part of the document, so since mass deletion is not really possible for me, I added these to the same parent and then move the parent and its hundreds of children to the buggy imports space.

I'm not sure if any of these unsuccessful imports will show up in the page tree tomorrow, but I really hope they won't because it's simply impossible to clean the whole thing up again (the Table of Contents for this 905 pages long documents is 27 pages long. That's 400 wiki pages approximately).

This evening, after working hours I tried again. First, I created brand new docx files from scratch, empty, and pasted the content. Did the usual reformatting to make sure no 'external' or hidden formatting contaminate the file...I got 20+ files this way (each between 10-20 pages long).
This worked, they were imported with a success message, and look ok to me (the usual raw format we get after importing tables from word).

I wonder if the problem was that there was insufficient cloud server capacity for processing all imports...

It's been a while, but I believe the issue we saw was that any documents with a header from older versions of microsoft word would fail, our solution was importing them into pages, then exporting them as word docs.

Hi everyone,

This is Anna from the Confluence team. Thank you for raising this bug and bringing it to our attention. After our investigation into this issue, we weren’t able to reproduce the behaviorwithin our instances: we tried to reproduce this issue on Windows 10, 11+ Chrome, Edge, Firefox and import processes were successful.  
We would like to get to the root cause of what you’re experiencing. Could you provide some more details or a screenshot to help us narrow down this case?

We will keep this issue open for another 14 days, but if we don’t hear back by then we will need to close this out to focus on our upcoming roadmap for all Confluence users.

Best,

Anna

I tried everything but it does not work today with any word documents. Can you please check?

Probably not Joe.

Although there's probably an add-in you can subscribe to for $200 a month.

Is any work being done on this ticket that has been open since 2017?

This bug is from 2017.  Are there any updates on if this ever be resolved.  I'm trying to Export OneNote knowledge base into Confluence Cloud.  

This isn't working in Chrome OS either...

Same problem here.