Blog Post

Healthcare and Life Sciences Blog
1 MIN READ

HLS Show Me How - Move Planner Across Teams

MichaelGannotti's avatar
Sep 13, 2018

The other day I was asked by a customer how they could move a plan from one Microsoft Team to another. Over time they wanted to be able to surface an existing Plan that resides in Team and then render it in another but there did not seem to be an easy way.

In this episode of Show Me How I demonstrate how to quickly leverage the Website tab to pull in an existing Planner Plan and add it quickly as a Tab within any given Team.

Learn more about Microsoft Teams and Microsoft Planner with the resources below.

 

Updated Jul 12, 2019
Version 2.0

29 Comments

  • Beverly23's avatar
    Beverly23
    Copper Contributor

    Does Microsoft have this in their roadmap as a needed feature?  If so, when can we expect this?  I have a work around in mind, but it is somewhat ugly.

     

  • @beverly the short answer is there is not really a template. You can share a single plan (not a template) across multiple Teams and if you change it in place will reflect changes elsewhere but also all Teams will see all of the plan in its entirety

  • Beverly23's avatar
    Beverly23
    Copper Contributor

    I want to use one plan as a template plan for several teams.  I then want to allow each of these teams to leverage off of this template and modify and create their own unique plan.  So, my question is, if I use this website method of adding a plan to a team and I then modify that plan within the team, will I also be modifying my template and anyone else who has linked to this plan will also see the changes.  If this is the case, then you have not solved my problem of being able to reuse and leverage off of a template plan - something that many project managers like to do.  I will test this out, but would appreciate any feedback here as well.  Thanks.  

  • EricDavisTech's avatar
    EricDavisTech
    Bronze Contributor

    Michael Sampson I think there are many organizations that are hoping for plan templates, which might help with your concern about copying a plan across groups.  Last year at Ignite the Planner team mentioned they had that on their roadmap, so hopefully in a couple weeks at Ignite we'll get an update on their progress.   https://youtu.be/DKsyIj4vYwM?t=2227

  • Absolutely Michael Sampson. If a non public plan then you would need to set the permissions accordingly for the plan being shared. Not ideal but for now would at least give you access across one or more additional Teams. As to whether the Planner team is looking at ability to migrate across Groups/Teams as there is nothing published I really can't comment on it. If a customer of mine has such questions I could discuss with them what may or may not be being looked at as well as connect them to the team directly to discuss. But not at liberty to comment one way or another in this setting.

     

  • Hi MichaelGannotti, long time no talk. Hope you are well.

     

    I'm glad you mentioned the big proviso to the hack above - that of permissions. If the link is to a public plan, then no great problem. But if it is to a private plan, it could get squishy. What's your recommendation for how to provide permissions to a non-public plan, and do you have a sense if the Planner product team is working on the ability to migrate a plan across Office 365 groups?