make it possible to move a Team Project between Team Project Collections
Currently you need to move an existing Team Project to a new Team Project Collection. I would like a feature to move Team Project between Team Project Collections without using TFS Integration Toolkit or other 3rd party tools.
We are still committed to delivering the ability to move projects between collections, however we’ve been unable to make additional progress on this feature. The challenges highlighted in the earlier post are still present and unfortunately this work is still on hold. We recognize this is a highly requested / needed feature, however I don’t foresee us making additional progress on this feature within the next 6 months. We will provide an update once we start planning for the second half of 2018.
TFS & VSTS Program Manager
Josh Gerstein commented
@Whitney Jenkins - I don't mean want this comment to come across as snarky, honestly I just would like more information from you on whether the work to build this feature is still on hold or if this work has made the cut for the planning of the second half of 2018.
I just checked by watch and it's July 8, 2018 so it's been exactly 180 days since your post, that's exactly 26 weeks, and ~ 5 months. http://www.howlongagogo.com/date/2018/january/9
And in looking at my calendar July is the second half of 2018 so I imagine the planning for this feature has already taken place, is that correct? So are the engineering teams plans for the next 6 months to include the work on this feature?
If that's not the case can you please post the promised update and provide more information and a roadmap for when this highly requested feature may be planned to be worked on and then hopefully delivered to us your customers?
You stated "We will provide an update once we start planning for the second half of 2018." so please provide the update and let us know where things stand.
Any update?, to be able to move a team project with history into another collection would be ideal...
as per original post request abc.visualstudio.com to xyz.visualstudio.com
Any updates on this feature
Michael Bürschgens commented
When I started work at my current employer a few years ago I got issued a Visual Studio licence and in the installation process I was asked for my Windows Live credentials.
Now, about 3 years later, tons of my employer's code is stored in my personal Microsoft account.
What if I want to leave the company? The whole, totally broken concept of linking everything to one's personal Microsoft account that Microsoft has been pushing for years now has created a real problem with no solution.
We have many projects in one Collection in TFS. I need to move just one project from TFS to VSTS. The rest of projects must stay in TFS as archived.
I read in comments below that it is not possible to migrate just one project from TFS to VSTS. If I am wrong and things had changed before my comment, please let me know.
I described what we need under this link: https://developercommunity.visualstudio.com/content/problem/252480/how-to-specify-the-project-to-migrate-from-tfs-to.html.
Brad Riddoch commented
This feature is needed by us for archiving old projects. Please spend some time working on this for us.
Almiro Alves commented
I need this!
We need this feature urgently for archiving old TFS projects. Our database is growing too fast.
Their H1Bs can only do so much needful!
Greg Read commented
I have been asking for this feature for years. We were actually hoping to migrate many of our older TFS projects to an archive collection with the idea we would reduce the database footprint of our primary TFS collection. This would allow us to migrate the data to VS online easier over the course of a weekend (decrease migration time).
any update yet?
David M commented
I am with everyone else, we currently have a third party writing code for us and we need to get a copy of their project. Without this I may have to resort to writing my own code to attempt to do this, but not sure that I can get all the date/time entries and all the comments associated to their users in the same way that they are in the current site.
Scott M commented
Please add this feature... We sometimes start projects for Clients using our account. Once the project obtains maturity and approval to proceed, they then want the project moved under their their account. Unfortunately, we have to tell them it will need to be manually done. Neither of us likes that outcome.
Denis Eremenko commented
I've already described cases, where the requested functionality is highly desired:
- Project archiving
- Collection restructuring (i.e. organizational changes, infrastructure changes, isolation of fast growing projects)
These cases are not a consequence of somebody's mistakes,this is a normal project\orgstructure lifecycle, which is not supported by TFS.
It has always been the case that projects cannot be moved this way. If this is ever delivered, most of the people will use it once and never again. It seems this feature is requiring a lot of resources that could be spent elsewhere. If you laid out your team projects wrong, deal with it. If you need to split it, clone it and delete; let it run over holidays if need to be. Keep them separate instead of merging it. It's annoying, yes, but you are already doing all of this for years. How is it even a reasonable investment from business perspective? You are already customers if you have this problem, and switching to a competitor will not help you move your current projects either.
Please add this feature
It would be really helpful feature rather than taking backup and doing other process. Thanks
Joao Barbosa commented
Please add this feature
Denis Eremenko commented
Our company works in perhaps the biggest instance of TFS in Europe. And we've been waiting for this feature for 5 years.
It's critical for us to keep archived projects, so we never delete data from TFS. That's why we have to invest to hardware and increasing environment complexity to keep it working with appropriate performance. The list of our projects is more than 400 and keeps increasing.
If you would bring the ability to move projects between collections, it would solve our problem of storing archived projects and keeping production collection clean.
Also we're unable to isolate workload of heavy projects, so we have to deal with one huge 5TB collection. Suggested workaround to clone this huge collection and then cleanup unnecessary projects in it will disable ability to work with the project during this operation, which can take more than 1 week.
So, if we could move some heavy projects into separate collection, that would relieve the load from primary collection.
I really hope that the given scenarios will help you to make correct decision about this feature, highly desired by many people worldwide.
David M commented
Really would like to see this feature and @WhitneyJenkins it would be really nice to see a DETAILED blog post that describes the plan and the technical implementation\architecture when you start planning for this feature. My company has been waiting for over 6 years (since TFS 2012) for this feature and it'd be really appreciated to understand how you will approach fixing this critical shortcoming. Thank you! Hope springs eternal for this feature.
Don't push it off again.