You can now bulk import Miro Boards into Confluence as Whiteboards!

[#1]

Hi there! I’m David Olive, a Product Manager focused on our importer tools in Confluence. Today, we’re introducing the bulk Miro Importer in Confluence! Moving from another tool can feel overwhelming—we’re here to make it smooth. With bulk import, you can bring multiple Miro boards into Confluence as editable Confluence whiteboards in one go.

 

Take a look at the GIF below for a visual guide on getting started

 

1. Select the “Import from other Tools” option in the spaces dropdown

2. Select the option to import Miro boards.

3. Follow the on-screen instructions to upload your Miro boards.

4. Confirm the import to complete the process.

You can find the full feature documentation here.

Have questions or feedback? We're all ears! Drop us a comment below, and let's keep the conversation going.

Happy importing! 🚀

[Staffan Redelius]

Love this! It will absolutely help our users to consolidate information to Confluence.

What happens if you try to import more than 3 Miro boards when you are on the Standard plan? Do you get to choose which boards to import?

Best regards,
/Staffan

[Bill Sheboy]

Greetings Atlassian team members!

I respectfully suggest you only post / announce the release of feature changes one time in community posts.  The content described in this article was already announced a few hours earlier here:

https://community.atlassian.com/forums/Confluence-Whiteboards-articles/May-2025-Whiteboard-Updates/ba-p/3040812

This behavior is increasing in frequency, and posting multiple times for the same content creates several challenges, including:

• It gives the impression the Atlassian team is not performing change management well.  We are left wondering if there is a well-considered plan, and if the team members are speaking with a single voice when engaging with your customers.
• It gives the impression the community guidelines do not apply to Atlassian staff.  When someone other than an Atlassian employee "spams" the same content, particularly vendor partners, that content is removed and the community member reminded of the guidelines.
• It creates community confusion by misaligned responses.  Please consider the examples of the sunset of the Epic linking fields toward consistent use of "parent", and of the renaming of "issue" to "work item" (or to just "work" in other threads).  There were multiple announcement / feedback articles for those, often devolving into chaos because questions were either answered differently, incompletely, or just abandoned (in cases where the threads were closed when the authors chose to do so).

Thank you in advance for your help improving your change management!

Kind regards,
Bill

[Em Ditchfield]

Hi @bill

Thank you so much for taking the time to share your feedback with us! We genuinely appreciate your engagement with our community and your attention to how we communicate our updates to our users.

I completely understand your concerns about multiple posts appearing to cover similar content, and I want to clarify the intention behind our recent communications approach. The first post you referenced serves as a comprehensive overview of all our Whiteboard releases specifically for our Whiteboard community members, while this second post is designed as a deeper dive into the specific bulk import feature meant for a broader audience who may want to learn more about the functionality in greater detail!

We absolutely want to ensure that our community engagement reflects thoughtful planning and clear coordination. Your feedback helps us recognize where we can improve our approach to avoid confusion and maintain the high standards we expect from all community members. Your suggestions will be shared with our team as we continue to refine our processes for announcing updates and engaging with the community. To help mitigate this, I'll also add a reference to this post in my initial WBs overview.

Thank you again for your continued participation in making our community better!

Emily
PM - Confluence Whiteboards

[Bill Sheboy]

Hi @Em Ditchfield 

Thanks for your response and the improvement work the team is doing! 

When considering how feature improvements are communicated, perhaps take a look at what the Jira Product Discovery (JPD) team is doing, where there is roadmap, followed by an announcement article which includes links to knowledgebase sources and Loom videos for deeper dives / how-tos, etc.

Kind regards,
Bill