Team Foundation Server Integration Tools (March 2012 Release)The TFS Integration Tools is a project developed by the Team Foundation Server (TFS) product group and the Visual Studio ALM Rangers to integrate Team Foundation Server with third party systems for migration and synchronization of data. |
THIS SOLUTION HAS BEEN DEPRECATED - Please refer to Migration options for other supported migration options. If you’re looking for TFS to VSTS migrations, you can investigate the new TFS Database Import Service for Visual Studio Team Services (VSTS). MICROSOFT SOFTWARE LICENSE TERMS - MICROSOFT TEAM FOUNDATION SERVER INTEGRATION TOOLS TFS Integration Tools were designed to work with Team Foundation Server 2012 and earlier. Use of these integration tools with TFS 2013 and 2015 may cause errors. TFS Integration Tools will not be supported past May 31, 2016. The TFS Integration Tools is a project developed by the Team Foundation Server (TFS) product group and the Visual Studio ALM Rangers to integrate Team Foundation Server with third party systems for migration and synchronization of data. These tools are commonly used during migration to TFS, as well as for copying source control and work item data between servers. Although the tools can be used for many purposes, planning, thorough testing and honest evaluation of extra resources and cost that will be required should precede any decision to use the Integration Tools. The Integration Tools are not intended to replace a server upgrade as a path to TFS 2010 or TFS 11 and this scenario should be avoided if possible. This release (March 2012) is an update to the March 2011 release that adds support for TFS 11 as well as fixes several important bugs that were reported by customers. It includes the ability to synchronize with the hosted Team Foundation Service at http://tfspreview.com. If you are using a prior release, you should upgrade to this release by uninstalling your current tool and installing this version in its place. Migrations are a very involved process and users can expect conflicts. Users must have an intimate knowledge of their source code in order to resolve these conflicts. Upgrade vs. Migration One common area of confusion is around the definition of "migration", especially as to how it compares with the term "upgrade". Below is an explanation of how these concepts differ (also see the aforementioned Migration Guidance Document). Migration - For this project, and for TFS in general, we use the term "migration" to refer to moving data between two different servers. Migration is done through the APIs of TFS, and is a lossy data transfer (see the limitations listed below). Upgrade - We define "upgrade" as the fully supported, in-the-box process of changing to the next version of TFS (e.g. upgrading from TFS 2005 to TFS 2008). Upgrades are done in-place, at the database level, and are full fidelity, meaning there is no data loss. The March 2011 release includes the following features:
Limitations As mentioned above, there are items that are not migrated when using the tool and this should to be taken into consideration when deciding on whether to do a migration or upgrade. What IS NOT migrated by the Toolkit
For any questions or feedback on the tools, please engage with the TFS Integration tools team on the MSDN forums at:http://social.msdn.microsoft.com/Forums/en-US/tfsintegration/threads |