Has anyone ever performed bulk import of Requirements and their links from ADO to confluence.

[Belinda Pereira]

We are in the midst of transitioning Requirements from ADO to Confluence. We'd like to maintain the same tree structure as is in ADO. Epic, Features, Requirements, Tasks. 
Links need to be maintained in the hierarchy. 

We already have created a new conf space for it. 

How do we import the .html files (each requirement will be a separate file) to appear under the requirement section in Confluence? 

[Shivam Sharma - Optimizory · Accepted solution]

Hi @Belinda Pereira ,

Welcome to the Atlassian Community!

Importing HTML files one by one will technically work, but you'll lose the tree structure and the links between requirements, which sounds like the main thing you're trying to preserve.

A better path is to export from ADO as CSV instead of HTML; I believe ADO supports this natively and then import that into a requirements tool inside Confluence. I can refer you to RMsis - Requirement Management tool, and it handles this exact case. There's an "Indentation Level" column in the CSV that rebuilds your Epic → Feature → Requirement → Task hierarchy on import, and it preserves cross-references and traceability links too.

Walkthrough of the hierarchy import: https://optimizory.atlassian.net/wiki/spaces/faq/pages/264668/Importing+hierarchy+of+requirements+in+RMsis

If it's possible for you, you can share a small sample of your ADO export, and I can tell you exactly how to shape the CSV before you run the full migration. Saves a lot of cleanup later.

You can reach out to me here: https://www.linkedin.com/in/shivam-sharma72/