11-26-2018 01:18 AM
11-26-2018 01:18 AM
Good day, I am sure this has been asked before but I can not find anything on the web or Forum.
I have Channels that I want to move to another team. Eg. Team Name: Tender
Channel name in this team: ABC Pty
Other team: RFQ
I want to move the complete Channel ABC Pty from Tenders to RFQ?
How do i do this?
11-26-2018 01:56 AMSolution
03-03-2019 10:48 AM
07-17-2019 12:09 PM - edited 07-17-2019 12:09 PM
I hope Microsoft moves on this, because this is the most in demand feature in my org. Use cases keep popping up. People are reluctant to adopt and create teams, because they fear they will have to manually migrate channels when our fast growing business changes. @HerculesConsen I created an account just to bring this up.
07-17-2019 10:28 PM
Good day, all.
Jip no movement yet on this feature. I hope they make this a priority. I can understand from a development aspect why this is a challenge.
But they have added other features that we have requested, at least that is a positive.
have a great day. @3lizabuttons
07-26-2019 01:45 PM
@HerculesConsen What can we do to get this pushed to development? I'm trying to convince my users to utilize this tool but not being able to move channels is a hard stop for me as the team I'm piloting with asked that specific question when reviewing the product. This should also be disclosed in the training videos as well so orgs know what the limitations are before they get started with implementation.
07-27-2019 04:17 AM
@Jay26 the more votes it gets on UserVoice, the more resource gets assigned at Microsoft. To my knowledge it's something that will be looked at after Private Channels which has been a focus for some time, and technically becomes a pre-cursor to moving channels.
Creating some planned structure for your Teams up front should really remove too much issue here. For example pre-creating major departments or other structures in your business would allow users to choose the right space for their channels to exist, moving would only be required if something was in the wrong place the first time round.
07-27-2019 10:04 PM
I'd like to second this idea, and would love to see support for this added. As much as we'd like to pre-define a structure, things can change, and requirements can evolve when starting a new organization. In these cases, having the ability to move entire channels between Teams would be fantastic.
11-14-2019 08:12 AM
I just want to add another vote for this feature. We would need it as well. It's a pain to move channels manually
11-19-2019 12:49 AM
@kspoelker yes, stupid simple copy and paste. Fortunately, we don't have too much in this specific channel. Just some hours of work to move it. Other channels we were maintaining for years already. There we had no chance to do it manually without getting crazy...
11-19-2019 06:53 AM
@HerculesConsen - MS should have rolled out this feature with Private Channels. It is reasonable to assume that customers will want to migrate existing content to newly created private channels. The other option would be to convert an existing channel to private but I do not think that is possible yet.
11-19-2019 09:05 AM
@montagePBSC neither is possible, but would people want to wait even longer for private channels to become available for this to be developed? It is far from simple to achieve, what should happen if a member of the source channel isn't then part of the destination team or private channel, should they be prevented from seeing what they previously posted, should it disappear?
Keep voting on UserVoice, the product team are thinking about this requirement and the more popular it is the sooner we will get it.
12-03-2019 06:16 AM
Agree this is much needed. Teams is rapidly becoming another difficult to navigate repository. Yes, planning is important, but in a large organization it is difficult to propagate and enforce best practices. Please add this capability.l
12-04-2019 02:28 AM
Move, Archive and Export channels in MS Teams is possible with a third party solution of SphereShield:
01-13-2020 12:59 PM
01-15-2020 10:21 PM
I have posted this issue on so many platforms and was disappointing when they revealed the updates to Teams and did no see this included.
01-20-2020 12:01 AM
01-23-2020 05:39 AM
@Dean_Russell It's a conundrum that's now compounded by this sec model update, because it's now the reason why we want to move stuff around! So if 200 posts wasn't enough (probably representing 20,000 businesses), this just became a priority for 10x the number of customers.
I also understand the underlying complexity of a request like this. I actually feel that now that new features are implemented, especially private channels, this will drive the urgency on this like us.
We built teams with only 1 channel per team because of a lack of permission customisation within the team. Now that we can do this, we want to change the structure of our teams and channels to enable external access and tighten security within our organisation. Now having used teams for 2+ years, it's a lot harder for us than our clients who are recent adopters to Teams and no issue for future adopters; but given Teams is presumably the fastest adopted product in Microsoft's history, there will be millions of customers now wanting to restructure their teams as a result of the security model change.
I accept that they would need to consider not just the OOTB Teams channel features but any other MS apps that plug in like Dynamics, Planner, Bookings, etc. Therefore couldn't Microsoft offer a staged roll-out of this feature via early release channel that would allow SharePoint and Exchange Specific connectors to be done first? Next, do all the CDM PowerApps like Bookings, Planner etc., then look at the 3rd party integrations which would probably be easier to remove and re-add as they provide feeds rather than in-app data.
01-27-2020 12:14 AM
It is possible with a 3rd party solution from AGAT
02-11-2020 12:55 PM
We are relatively new users to the TEAMS / SLACK thing and part of the wave deciding to give TEAMS a try. We generally like it, but as we get into it, things like this are giving us second thoughts and not being able to move channels is pretty close to fatal for us. I really need a timeline on if/when this will be addressed. Otherwise, we will be forced to assume that this not a priority for TEAMS and we will riding the wave out to SLACK. Would be a shame for MS to convince us to try this platform out, only to push hard and fast to a competitor. Given that this thread is 2 years old, I think some sort of concrete timeline is due.
02-12-2020 03:47 PM
@HerculesConsenWe agree. This capability, a "nice to have" prior to private channels, is now a "must have". We need to align groups and channels and the ability to move channels (and their existing content) between groups is extremely important. We have convinced the organization to abandon Slack and use Teams (with its better integration with O365), but this obvious limitation is deeply unfortunate. The existence of a 3rd party solution (via Spherespace AGAT) is nice but doesn't help, as the main competitor (Slack) allows channels to migration among workspaces with ease.
Please elevate this on the development priority list and provide an estimate of when it will become available. This is a serious competitive deficiency.
02-14-2020 02:26 AM
Totally on the same page here. When we started using Teams we did what we thought back then would make sense given the constraints within Teams (before the days o secure channels) resulting in organized chaos with Teams all over the place with often just one channel per Team.
Then came secure channels, that MS should have had from day one really, making it possible organize the Teams and Channels properly, but if we cannot move existing channels we are stuck with the mess. MS need to address this sooner rather than later. I see there is a third party solution, but we would ideally not want to do patchwork on this and stick to the ecosystem.