TFS to TFS Migration Tool v1.1 (Prerelease)

Rating:        Based on 7 ratings
Reviewed:  7 reviews
Downloads: 1396
Released: Sep 16, 2008
Updated: Sep 16, 2008 by mmitrik
Dev status: -not yet defined by owner-

Recommended Download

Application TfsToTfsMigrationTool(v1.1).zip
application, 1198K, uploaded Sep 16, 2008 - 1396 downloads

Release Notes

TFS to TFS Migration Tool v1.1 (Prerelease)

The purpose of this release is to fix many of the issues in the previous release of the tool, and to leverage the Migration and Synchronization Toolkit v1.1.


  • It is recommended that the latest client and server bits are used wherever possible. Also, the TFC version used should be greater than or equal to the highest TFS version (i.e. for a migration from 2005 SP1 to a 2008 server, use 2008 or 2008 SP1 client).
  • TFS 2005 Service Pack 1 is the minimum version for both the server and the client machines
  • A SQL Server 2005 database must be deployed

Uninstalling the tool

  • When uninstalling the TFS to TFS Migration Tool v1.1, one of the databases created by the Migration Toolkit (tfsmigration) will not be deleted by the uninstall wizard. The database must be removed manually for subsequent installations to work correctly.

Improvements in this Release

  • See the improvements of the Migration and Synchronization Toolkit v1.1
  • "The key is not present in the dictionary" exception is no longer thrown by the tool.
  • Pressing the connect button no longer repopulates the Team Projects in the combo box.
  • Duplicate Team Projects are no longer shown when the source and target are the same server.
  • Timestamps have been added to the session name. This keeps the names unique after subsequent migration runs where the session name is not manually updated.
  • Permissions are validated before migration sessions are started.
  • Work item tracking linking is enabled by default.

Known Issues/Limitations

  • Remote installation is not supported.
  • 64-bit operating systems are not supported by this tool.
  • Credentials must match on both the source and target server.
  • Connecting to the TFS server in the GUI may result in a TF30076 error.
  • Following a failed migration, subsequent migrations may be unsuccessful.
  • The source and target of a migration are named incorrectly - items are actually migrated from the target to the source.
  • Workspaces used by the migration tool are left behind after migrations, even if sessions are deleted.
  • Only folders that currently exist in the target server can be used as targets for migration.

Reviews for this release

good release, we can migrate source code, but WIT is not good enough.
by siyo_wang on Nov 28, 2008 at 4:37 AM
I'm trying to move a single branch from one Team Project on one TFS server(TFSServer1) to another Team Project on a second TFS server (TFSServer2). I've tried creating the same Team project with the exact same name "WCW" but I can't get the source code to move over. Maybe this functionality isn't available yet....please add it soon.
by CharlesZimerman on Oct 6, 2008 at 4:36 PM
I tried this tool again against out TFS instance that has been upgraded to TFS2008 and while initially it looked like it was working to migrate the source respository, it failed. I've deleted the migration database, unistalled the tool, and reinstalled the tool, and the migration continues to fail. The tool has improved from the previous version but it just doesn't work yet. Maybe the next version
by RayK on Oct 2, 2008 at 1:39 PM
New Release (Sept 08) is much better in terms of migration of version control and WI. With this I migrated TFS 2005 to TFS 2008 with 100% source code. But I have few suggestions (may be included in future release) - Migration utility required both the src and destination TFS must be in the same domain. - Installation need named instance both of these were there in previous release(March 08).
by vikkuu on Sep 24, 2008 at 2:45 PM
The install was a challenge but the program runs 100% better than the last release. I don't know if its the toolkit update but its definatly working. The old database file may need to be deleted before running the install. Also found I was required to install sql express on the server due to the hardcoded named sql instance during the install.
by dburrell on Sep 19, 2008 at 2:05 AM
Installation not working. Previous release at least install fine and connect to database. -Updated - After some workarounds, I got it connecting into the database. The problem now is that it dont run right the migration jobs. It just show lots of Session Abort messages. Still running by 16 hours and dont migrate a project with few changesets.
by ironmala on Sep 17, 2008 at 2:57 PM
The installation was already bad. Now it is really worse than ever. 1. The new install requires the service account to be the local admin. 2. Still fails with 1001 error if it cannot find sqlcmd (I guess that is what it does after installing the windows service). 3. In my testing the migration errors at the first change it encounters with the error event 'SessionAborted' and it continues.
by Yogudada on Sep 17, 2008 at 5:46 AM