How can we improve Azure DevOps?

make it possible to move a Team Project between Team Project Collections

This suggestion is migrated to Developer Community. Please use below link to view the current status.
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.

2,382 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Visual Studio ALM Team shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    We are committed to supporting the ability to move projects between collections, however we’ve been unable to make progress on this feature. Unfortunately, the challenges highlighted in earlier posts are still present.
    I don’t foresee us making progress on this feature within the next 6 months. We will provide an update once we start planning for the second half of 2019.

    Whitney Jenkins
    Azure DevOps Program Manager


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      • David commented  ·   ·  Flag as inappropriate

        As a program manager, I need the ability to move or transfer specific 'projects', and all of their associated meta data, such as history, change set history, pull request history, code review request history, comments, discussion history, work items and their history, ect... from a source Azure Dev Ops instance, to an entirely new 'target' azure dev ops instance.
        This would helpful and provide business value, for example, if there is a need to transfer source control and history, when a client matures technically, and is ready to manage their own source control, in house, or in their own Azure Dev Ops instance.
        Please let me know if my acceptance criterion is not clear, as I would be happy to give further specific examples.

      • Kevin Ristow commented  ·   ·  Flag as inappropriate

        The history of updates on this request is not conducive to planning within the enterprise. I would be very helpful to get a commitment in the form of a timeline so that people like myself and other can plan accordingly. This particular enhancement has some fundamental implications on our approach and plans.

        Please provide an update that is more committed than the repeated answer of "Second half of next year". At this point I can only assume that this will just continue to get pushed which is very disappointing.

      • Philippe Moison commented  ·   ·  Flag as inappropriate

        We manage all our customer implementation projects in Azure DevOps. We manage them in our own dedicated implementation tenant. Often, customers want to take the property of the project in their own tenant when it has gone live. This feature is mandatory for us and we look forward for it... Please don't postpone again...

      • Frank commented  ·   ·  Flag as inappropriate

        Please tell me how we (large enterprise) are supposed to archive single projects existing within one collection without this feature.

      • Juanma Feliu commented  ·   ·  Flag as inappropriate

        It would be an amazing feature.
        Migration of a TFVC Team Project to a Git Team Project with dashboards, WI's, Builds, source files and so on) would be amazing too.

      • krishnasai koneru commented  ·   ·  Flag as inappropriate

        Can we move just a folder from one TPC to another without loosing history. Is there any tool to do it. we really need this feature.

      • kevin commented  ·   ·  Flag as inappropriate

        Can we move just a folder from one TPC to another without loosing history. Is there any tool to do it. we really need this feature.

      • Jeff Flager commented  ·   ·  Flag as inappropriate

        Wait a second, I got an email update that there was a notification of an update. We'll let's see here. First planned for second half of 2016 then 2017, then mid 2017, then second half of 2018, and now second half of 2019.

        So let me get this straight. First requested on July 14, 2011 and now 8 years later MSFT might possible be considering this feature? What are you guys doing over there...besides renaming the product multiple times.

      • John Saunders commented  ·   ·  Flag as inappropriate

        I recently read about Azure DevOps being the replacement for VSTS. I didn't see any mention of TFVC. Perhaps that's how they plan to address this problem?

      • Randy in Marin commented  ·   ·  Flag as inappropriate

        Time might be better spent migrating to GIT. We still use TFVC, but I see now that migrations would have been easier if our many team projects used GIT. I want to combine and move them. Looks like GIT is able to do this already. Now, to move to GIT....

      • Anonymous commented  ·   ·  Flag as inappropriate

        We are a large enterprise and urgently need this feature - even if highly compromised. Anything to help. Our situation is complicated by the VSTS instances all being backed with separate Azure AD's.

      • Tim Sexton commented  ·   ·  Flag as inappropriate

        This makes acquisitions very difficult especially when you cannot transfer visual studio developer subscriptions. There is a GIT code migration utility from one account to another, so why not the same for work items???

      • Josh Gerstein commented  ·   ·  Flag as inappropriate

        @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.

        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.

      • JCA commented  ·   ·  Flag as inappropriate

        Any update?, to be able to move a team project with history into another collection would be ideal...
        as per original post request to

      • Michael Bürschgens commented  ·   ·  Flag as inappropriate

        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.

      • Mihai commented  ·   ·  Flag as inappropriate

        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:

      • Brad Riddoch commented  ·   ·  Flag as inappropriate

        This feature is needed by us for archiving old projects. Please spend some time working on this for us.

        Thank you.

      ← Previous 1 3 4 5 6

      Feedback and Knowledge Base