Skip to main content

We have a number of ‘master’ boards that have been designed and created in different projects.  The masters will be managed in our methodology team and then copied to other teams & projects for each customer that we have Miro workshops with. 

At present there are at least 70 ish boards which means a lot of moving & copying if we dont have a bulk transfer capability, especially inefficient if we have to move projects, board by board, customer by customer,  so any bulk move we can make would be very valuable.

It would be a great enhancement to Miro to be able to perform the following functions in bulk for multiple selected boards:

  • Copy / Duplicate
  • Move to new Account
  • Move to new Project
  • Download Backup

I also vote for this… Please, please integrate this feature...


Thanks so much for taking the time to comment about this feature. We understand the frustration and appreciate your patience. Our team is reviewing this idea as it continues to be open for votes and comments.

 

For those coming across this idea, if you feel this would be helpful for you or your business, please be sure to vote for it and leave a comment about your use case to help our team scope this request!
 

Thank you,

Miro Community Team


Consultant setting up and administering this for a client.  I moved the client from LucidSpark to Miro, return the favour and help make my life easier!


Same here. Great product but loosing a lot of time on workshop prep… Would love to have project templates as you have board templates !


Thunderously upvoting this wishlist item. I am in the process of a long-delayed (long-procrastinated) migration from a Single-Team, Multi-Project structure to a much cleaner Multi-Team structure, and the absence of bulk management is rough. Individually obtaining Board Ownership, Moving to a Team, waiting, Moving to a Project, waiting, and repeating, is exhausting and unnecessary.

Elegance around batch management of boards is the design principle at play here

Thank you for initiating this thread four years ago @Ron Wedderburn 


Thanks so much for taking the time to comment about this feature. We understand the frustration and appreciate your patience. Our team is reviewing this idea as it continues to be open for votes and comments.

 

For those coming across this idea, if you feel this would be helpful for you or your business, please be sure to vote for it and leave a comment about your use case to help our team scope this request!
 

Thank you,

Miro Community Team


Quoting this response to give a little extra oomph and, hopefully, get this to the eyes of the product team for inclusion on a roadmap. Obliged :)


Hi @Kyle Chipman and everyone,

 

Thank you all for your continued feedback and patience. 

 

I want to assure you that our product team has reviewed this request. We’ll keep monitoring the thread and will make sure to inform you as soon as we have an update or further developments to share.

 

In the meantime, please feel free to continue voting and sharing your use cases to help the team scope the request more effectively.

 

Thank you for being part of the Miro community!


Awesome, thanks for the follow-up @Eca. I can compile use cases, or would even be down to jump on a quick call to share my experience if helpful for the team.

Good vibes everyone’s way ahead of Canvas 24 :)


Hi, I was going to create this as a new idea and I’m checking that it has been proposed 4 years ago!! 

It seems like a logical and basic necessary function in order to be available for an Enterprise level account.

Thanks


@Eca Any forward motion on this effort? I’m staring down the transfer of a looottttttt of boards, and would love to be able to manage them across Teams and Projects at a batch level as opposed to a Board level. To highlight a few points of consideration for the team in the interest of being helpful:​​

  • Resolution of Friction around Board Ownership (a Provisional Transfer upon Ownership Approval would be clutch, with the opportunity to automate repeated Ownership Approval requests until an answer is provided)
  • Focus on Batch Action at the Project Level (merging with another Project, separating from a Project, moving across Teams; batch action at the Team level is more about permissions and slightly less about batch board management)
  • Selection Mechanics / Haptics (I have always liked the click-and-drag fluidity of selecting visibility on Adobe’s layering system; applying that to a checkbox column in List View, possibly even adding in filtration)

I’m pretty sure I had one more bullet point, but it occurred to me mid-list and I lost it. if I miss the edit message window and it’s helpful I might reply again. Thanks to the product team defining the path forward.

---

Oh yeah! I remembered the additional bullet point an hour later, though it’s only tangentially related to this thread; clearer visibility around Users shared at the Space level, and Users shared at the Team level. Space permissions are two-clicks deep, featured as an Overlay, while Team permissions take the user to an entirely new screen. It would be so helpful if Usernames were easily visible via the main console as an expandable / collapsible tray. Usernames could even grey out at the Space level if the users are not shared, and remaining black when shared.