We need to import word doc and, most importantly, be able to split by headers so that multiple parties can collaborate on specific parts of the document only and should not have access to edit/comment on other parts.

We need this feature to be enabled at the earliest. Also can you provide the ETA for this.

Regarding this I have raised this support case with Atlassian PCS-344939.

So the confirmation received from Atlassian support team is, as of now we can't import new doc to the existing Confluence page. To add a new word doc, then we need to create a new Confluence page.

This issue is now blocking a large migration project for us - we would like to use Confluence, but because we can't import content as individual topics, we're looking at other products instead.

Having the whole doc as a single page causes performance issue for big documents. Especially for the use case of direct scrolling to an anchor in the doc from the URL: the page is unresponsive for many seconds before scrolling (and the user must avoid to interact with the page or it might end at the wrong place).

I have numerous large Word documents that I need to import into Confluence. Being able to split by headings would remove a huge amount of manual rejigging. Please do reinstate this feature. 

mdolan@atlassian.com

Can you give us an update on the status of the Feature "Split by Heading"?

And a second more general question:
For us it's not just one tiny feature of the Word Import. Instead, it is the only possibility to Import larger amounts of documentation into Confluence.
Are there other (maybe better) ways to import existing documentation?
For my company, it's a lot of content in Word and even more in MS OneNote, which is very much effort to import manually.

-> A good alternative (especially from OneNote) might reduce the importance of the missing Word feature.

(see also CONFCLOUD-30883 Support for Microsoft OneNote - Create and track feature requests for Atlassian products.)

Gathering interest? This feature was available before it was then removed. Surely, this should just be queued for reinstatement.  

We have a massive word document that we would like to migrate to a confluence space. It's a NO-GO without the option to automatically split content by headers. 

We are doing our whole project documentation in Confluence. We work together with external consultants who have documentations in Word and use it for the projects. Documentation often ranges between 50-100 Word pages. We also use documentations from our product development department which is created in Word as a basis for our project documentations. It´s not realistic splitting each imported document manually by headline and documentation is too long to use it in one single Confluence page.

Just to echo previous commenters, but we have lots of documentation that still lives outside of Confluence which will eventually be migrated over.
These are single word documents that potentially have hundreds of pages each with table of contents that span multiple pages, which would ideally end up unpacked across dozens of pages.

This was an easy job on Server, with relatively little clean up required - and is now impossible on Cloud (and is the reason I still maintain a Server instance)