How can we make Microsoft Teams better?

← Public

Move a project (channel) from one team to another

We would like to move a project (channel) between groups to keep the information.

28,275 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

3477 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anonymous commented  ·   ·  Flag as inappropriate

    Moving channels around should be a core functionality. I hope this item gets more priority in the backlog.

  • Deb Kilgore commented  ·   ·  Flag as inappropriate

    Adding my vote to make the moving of channels between Teams a priority. This is critical for organizing and scaling.

  • AI commented  ·   ·  Flag as inappropriate

    This really needs to be a priority! Over 4 years since the idea was suggested! Why is this not a priority?

  • [Deleted User] commented  ·   ·  Flag as inappropriate

    This is vital for the effective management of Teams Channels. Please can we look at this as a priority.

  • Anonymous commented  ·   ·  Flag as inappropriate

    This will be a valuable update to provide much needed flexibility in managing content when priject or work strictures change post initial setup

  • Nichola commented  ·   ·  Flag as inappropriate

    Yes please do this as soon as you are able! We use Teams at school and need to be able to move some students channels between class teams.

  • Thomas Leibetseder commented  ·   ·  Flag as inappropriate

    for our business we have either the choice of (A) creating individual teams (and subsequently also sharepoints) for each project OR (B) we use channels (either department or product specific) which can be moved or relocated under a "root directory"as per the actual organizational structure.

    version (A) leads to hundreds of individual sharepoints over time which need to be administred separately.

    version (B) would give us the chance to define a project portfolio organized according to the actual organization structure, top level administration of users and a possibility of re-organization in case of organization changes which occur frequently over the years or re-organize e.g. according to product types or others simply by copying channels and all related data in behind (planner/tasks, sharepoint data, etc.)

    this feature is truly essential for us since we have our project data on network folders which can not effectively be accessed from home office while sharepoint data can be easily accessed from anywhere.

  • Nick Aldridge commented  ·   ·  Flag as inappropriate

    Any update on this? The last update from Microsoft is almost a year ago and like many people below, this is critical for us as a business.

← Previous 1 3 4 5 … 173 174

Forum Home

Reference Information for Teams

Public: Teams and Channels

Categories

Feedback and Knowledge Base

(thinking…)

More Teams Information