Move a project collection – Azure DevOps

Move a project collection – Azure DevOps

Azure DevOps Server 2022|Azure DevOps Server 2020|Azure DevOps Server 2019|TFS 2018

You can move a task collection from one implementation of Azure DevOps Server to another. :

  • You have more than one implementation of Azure DevOps Server in your company, and you desire to move a collection to another release to much better line up with your organization requirements.
  • You wish to move the collection to a remote workplace that has its own implementation of Azure DevOps Server.
  • You wish to broaden your release of Azure DevOps Server by including another circumstances of SQL Server to it, and you wish to disperse existing collections in between the circumstances.
  • You require to incrementally update your release by removing a specific job collection from an implementation of Azure DevOps Server running an earlier variation, and after that move it to a server running the present variation of Azure DevOps Server. (One typical factor for this is some groups might require to move to a more recent variation of Azure DevOps Server, while others should stay on an older variation for tools or jobs factors.) In this circumstance, you should likewise then update each job within the collection by utilizing the Configure Features wizard. For more details, see Configure functions after an Azure DevOps Server upgrade The Configure Features wizard has actually been deprecated for Azure DevOps Server2019 You can just run the wizard on TFS 2018 and earlier variations. Projects specified on Azure DevOps Services upgrade immediately with each service upgrade.

The actions to move a collection will depend upon the specific setup of the release that hosted the collection and the implementation to which you move it. If you move a collection to a brand-new domain, you will require to include users from that domain to the proper groups at the collection level and the job level.

Here’s how to move a whole task collection. To move part of a collection, see Split a task collection


Before you begin your relocation, make certain that you’re an administrator on the servers and in the software application utilized by both the implementation you’re moving from, and the one you’re transferring to. If you’re not an administrator, get included as one

1. Remove the collection

Before you move a collection, very first remove it from the implementation of Azure DevOps Server on which it is running. It’s extremely crucial to not avoid this action. When you remove a collection, all tasks and services are stopped, and after that the collection database is stopped. In addition, the detach procedure copies over the collection-specific information from the setup database and waits as part of the job collection database. This setup information is what enables the collection database to be connected to a various implementation of Azure DevOps Server. If that information is not present, you can not connect the collection to any implementation of Azure DevOps Server other than the one from which it stemmed.


Detaching a collection avoids users from accessing any jobs because collection.

  1. Open the administration console for Azure DevOps on the server that hosts the collection to move, and in Project Collections, emphasize that collection.
  2. On the General tab, choose Detach Collection
    Detach project collections
    On the General tab, select then detach

    The Detach Project Collection Wizard opens.

  3. ( Optional) On the Provide a maintenance message for the task collection page, in Servicing Message, offer a message for users who might attempt to link to tasks in this collection.
  4. Select Next
  5. On the Review settings that will be utilized to remove task collection page, evaluate the information.
  6. To alter any settings, choose Previous If they seem right, choose Verify
  7. When all the preparedness checks have actually finished effectively, choose Detach
  8. On the Monitor the task collection remove development page, when all procedures have actually finished, choose Next

    The wizard shows you progress

  9. ( Optional) On the Review extra details for this job collection page, either choose or keep in mind the place of the log file.
  10. Select Close

    The task collection no longer appears in the list of collections in the administration console.

    TFS admin console doesn't show detached

2. Back up the collection database

After you have actually removed the collection, back up its database to move it to the other server. To perform this job, utilize the tools that are offered with SQL Server.

ic738721 Tfs_TestProjects > Tasks > Back Up.” data-linktype=” relative-path” >


You can just bring back a database to the very same variation or a more current variation of SQL Server. You can’t bring back a SQL Server database to an earlier variation of the item
If your initial implementation utilized the Enterprise or Datacenter editions of SQL Server, and you wish to bring back databases to a server running Standard edition, you need to utilize a backup set that was made with SQL Server compression handicapped. Unless you disable information compression, you will not have the ability to bring back Enterprise or Datacenter edition databases to a server running Standard edition. To shut off compression, follow the actions in Disable SQL Server information compression in Azure DevOps databases

3. Move the collection database

As part of moving the collection, you should bring back, copy, or otherwise move the collection database to a circumstances of SQL Server that is set up to support the release of Azure DevOps Server to which you’re moving the collection. You can pick whichever technique you choose to move the database.

Screenshot of the welcome page of Copy Database Wizard.

For more info about moving a database to another circumstances of SQL Server, see:

4. Connect the collection

After you bring back the collection database, you can connect the collection to the favored implementation of Azure DevOps Server. If the implementation you’re relocating to usages reporting, a reporting folder and default reports are constructed for the collection you’re connecting as part of the procedure.

  1. Open the administration console for Azure DevOps on the server that hosts the application tier for the release to which you’re moving the collection.
  2. Select Project Collections, and after that choose Attach Collection
    Azure DevOps Server Administration console, Team Project Collections
    TFS Administration console, Team Project Collections

    The Attach Project Collection Wizard opens.

  3. On the Select the task collection database to connect page, in SQL Server Instance, offer the name of the server and the circumstances that hosts the collection database, if it is not currently noted.

    Make sure the SQL Server instance is correct

  4. In the Databases list, choose the collection database to connect, and after that choose Next
Like this post? Please share to your friends:
Leave a Reply

;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: