Say Hello to HTML Importer: Bulk Import Your HTML Content into Confluence!

[#1]

Hi Atlassian Community,

I’m Tiffany Chung, a Product Manager on the Confluence Cloud team. We’re thrilled to introduce a new feature that addresses a long-standing request: the ability to move HTML content to Confluence more seamlessly.

Until now, bulk migration of HTML docs to Confluence has been a challenge. We’ve listened to your feedback and are excited to announce the launch of the HTML Importer (Beta) for Confluence.

Confluence: your central knowledge hub

It remains the go-to destination for users to create, find and organize their content. The HTML importer is instrumental in this process, assisting users in consolidating their tools and facilitating a smooth transition of their content into Confluence. This functionality ensures a more seamless experience as users integrate their information into one place.

How to Import HTML Content

1. Access Import Options: As a site or org admin, go to the spaces dropdown menu and select “Import from other tools.”

2. Follow the Import Flow: Proceed through the import process by uploading your HTML content, configuring spaces, and reviewing your selections.

3. Completion Notification: You will receive an email once your import is complete.

For more details, check out these support articles:

• Import data from HTML to Confluence https://support.atlassian.com/confluence-cloud/docs/import-data-from-html-to-confluence/

• FAQCreate and organize work in Confluence Cloud | Confluence Cloud | Atlassian Support

• Troubleshooting guide https://support.atlassian.com/confluence-cloud/docs/troubleshooting-import-data-from-html-to-confluence/

We are pleased to have you continue utilizing Confluence as your knowledge base. Please note that this feature is currently in Beta and will undergo further enhancements in future releases. We welcome any feedback you may have regarding the importer. Thank you!

[Kristian Klima]

This is seriously cool... my team have imported content from 4 HTML sites to Confluence over the last 12 months (sites that originated in MadCap Flare, Paligo, and Zendesk) - with good old fashioned copy-paste, page by page, method.

If this works as advertised, it will be a game changer because 'how do I migrated my docs from N to Confluence is a regular question on these fora.

Example from today: https://community.atlassian.com/t5/Confluence-questions/Export-DokuWiki-to-Confluence/qaq-p/2896180#U2896914

[Shawn Doyle - ReleaseTEAM]

If this works it changes 50% of all the Confluence Questions I've answered.

[David at David Simpson Apps]

Aaah, it's like the Universal Wiki Converter lives again :)

[Kristian Klima]

@Shawn Doyle - ReleaseTEAM True that :D

[SOLBERG Jonas]

Would love this for data center!

[Kristian Klima]

@SOLBERG Jonas 

Maybe that's not needed. If it's supported in Confluence Free, you can import HTML there, do the necessary content cleanup and sanity checks, then export the space as XML and import it to you DC.

(I find Cloud editor better equipped to deal with imported idiosyncrasies than the Server editor).

[Chihara]

@Tiffany Chung 

Is ths Beta ended/closed?

[Annelotte]

Hi, 

This is a great feature! Hopefully, it will expand in the future to allow re-importing/updating previously imported pages, too! 

I wonder how linking between imported pages works?

That way tools like MadCap Flare and Paligo can finally publish to Confluence and the documentation tools can be integrated!

Grtz,

Annelotte

PS: please allow separate permissions to be assigned to users for features like this, not everybody can become site admin!

[Bri]

@Tiffany Chung 
Will this always require you to create a new space for each upload? 

[Markus]

Hi everyone, we also use MadCap Flare. What would your process look like for displaying the documentation in Confluence? Just export to HTML and import HTML? Thanks!

[Kristian Klima]

Hi @Markus Ernst 

At Emplifi, we migrated two doc sets from MadCap Flare to Confluence - before the HTML importer was available - and not just to display it, but to abandon Flare completely and use Confluence and apps as a much better, all in one solution - as a writing, CMS, and a life-cycle management tool. 

We really found Confluence, customized with apps, a superior solution (and cheaper too :) )

We did it the old way, manually copy/pasting content from a static website (generated from MadCap). Our intern moved 400 pages in about 10 weeks working part time, including fixing links and doing the sanity check of the imported content.

This is the site https://agent-docs.emplifi.io/home/Production/ the content of which came from MadCap's site. The content is now authored in Confluence and we use Scroll Viewport to built our docs site.

If you only want to display your docs in Confluence (without using Confluence as CMS), you would have to reimport your content with each update - or create a complex workflow for partial updates.

Having said that - as a temporary solution, we simply used iframe macro to display Flare-originating site in Confluence. Of course, there were limitations, but as a temporary solution it won't hurt.

Anyway, I'll be more than happy to share my MadCap to Confluence experience. I created a high level summary is in this Community article.

(This is main docs site - https://docs.emplifi.io/platform/latest/home/)

[Markus]

@Kristian Klima Thank you very much for your feedback. And also for the community article. That's really great. I'll keep it in mind. Currently we would continue to work with Madcap Flare. We use the export on the web for the customers as a manual. But since we also use Confluence in our customer portal, i thought it would be a nice additional integration for our customers without media discontinuity.

[Kristian Klima]

@Markus Ernst Thank you! Of course, migrating documentation is always a varying degree of PITA so there must be a strong business case AND resources...