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.
Great Tool! Initially I had to do quite a lot of R&D and testing before executing this in production environments.
I have used this to migrate all code and work items which huge changesets from TFS versions 2010/2012/2013 (one way and two way sync).
Also, we are running a continuous sync between 2 TFS 2013 servers with multiple projects using this tool. Some level of regular maintenance is needed to make sure that there are no conflicts, resolve them manually if any, else sync gets stopped. There is automatic resolution (I would not prefer), but depends on the specific requirements.
I suggest Microsoft put more efforts like implementing notification functionality (email) to the admin/configured account when there are any conflicts that require resolution. I guess we can ourselves get a copy of this software code from codeplex and write code to improve the software. Not sure though how stable the codeplex version is.
Good Article: http://blogs.msdn.com/b/willy-peter_schaub/archive/2011/05/11/tfs-integration-tools-where-does-one-start-part-1.aspx
A royal mess when trying to migrate 4 years worth of checkins from TFS2012 to TFS2013. Spent the entire weekend watching the migration stumble, fail, start over, re-analyze from scratch, and get stuck. Terrible experience, the tool is buggy, slow and fails to scale. Good to bring over a couple of changesets, not 4,000+.
First we used TfsImport to import a 2008 TFS into a secondary 2012 collection, but noting the database schema of the imported data didn't match the original 2012 we weren't happy to use it going forward so we used TfsIntegration to migrate just the code and comments over to the original 2012 "DefaultCollection". All worked great. We didn't have a need for anything more than the core code and comments.
A nice idea but it tries to migrate all the data at once, storing everything in memory. What that means is that when you try to push a significant amount of data through it, it just explodes with an out of memory exception. It's also x86 so it has a pretty restrictive memory cap as it is.
It has a database which it uses to store migration settings, so it seems as if it could also use this to store the data it's migrating, because at the moment it's not much use.
Running a one way migration and receiving the error:
TfsMigrationShell.exe Information: 0 : VersionControl: Microsoft.TeamFoundation.TeamFoundationServerUnauthorizedException: TF30063: You are not authorized to access Microsoft-IIS/7.5.
I have seen other posts where the issue was running out of space for the IIS logfiles. Logfiles are being written to a drive with 1.2TB free space. I am also running this as an administrator. The change being processed is very large (11000+ Change Actions). Looking for a solution to this issue
I recieve the following message when I try to migrate projects from 2008 to 2012. What does this mean?
The migration DB does not have a valid extended property of 'ReferenceName'. DB schema validation failed.
I found the issue. I had to change the database I was using for the TFS Integration and the tools I used to move the database to a new server did not carry over the extended properties from the original database.
It would be nice to have a utility in the application to change SQL databases.
I have two separate TFS 2013 environment. Each has a separate URL.
Env 1 has collection A
Env 2 has collection B
Can this tool merge CollectionA into CollectionB? Or combine CollectionA and CollectionB into a third collection on Env2?
I used this tool for source sync and workitem sync on TFS 2013 update 2 and it works.
What is your requirement ? are you merging workitems or source ? the best way would be to configure is a Two way sync between the two instances
AngelaB,could you please, help me, after install Team Explorer 2012, I've tried to install Integration Tools, and I get an error message about "Team Explorer 11 dev" is required. Where can I download this versión?
Could you please, send a link.
Thank you, very much.
This error can be resolved by installing Visual Studio 2010 on the machine. This brings with itself the Team Explorer 2010 and necessary object models for the TFS integration platform to be installed :)
I'm trying to run the migration from TFS 2013 to TFS 2013 using the current release of the tool (2012), I can't see how to set the adapter to "TFS11" because the only option I'm getting when I configure the source is "TFS2010 adapter" ! which is, I guess, not compatible with TFS 2013 !
Just putting it out there for those who are stuck like me, the issue can be solved by installing Team Explorer 2012. The strange thing here is even a newer version of Team Explorer (for example 2013) doesn't detect the TFS11 Adapter! just wondering if there's gonna be a newer version of the Platform ? and when ?
Just open their installer in Orca to AppSearch table and look at the what it checks for:
SOFTWARE\Microsoft\VisualStudio\11.0\InstalledProducts\Team System Tools for Developers
now fake the registry keys to get past it :)
I've run into the issue described in The TFS version control item does not exist - "Microsoft.TeamFoundation.Migration.Toolkit.MigrationException: The TFS version control item "___" does not exist." while attempting a TFS Preview to TFS On-premises migration)
I know that a good number of files (>20) have been renamed and I suspect that folders have been renamed too.
Rather than "fix one, restart migration, fix another, restart migration .... " is there a way to identify all of the renamed files and folders so I can attempt to do the **NOMIGRATION** fixes on all of them in order to get thru the migration without another rename issue?
Please note that I asked this at http://social.msdn.microsoft.com/Forums/en-US/tfsintegration/thread/ebf8453e-ffd2-4b45-b5a3-24ff528c45ec/ and it was suggested that I ask in this Q&A area instead.