Sample Migration Tools

Published 07 November 06 12:23 AM | mmitrik 
 

As expected, the first questions about the Migration Toolkit concern the tools that will be developed on top of it.  Right now, we are planning to release two different tools (1 version control, 1 WIT) along with the toolkit itself.  These first tools will serve as examples on how to write toolkit based tools, and will provide full migration functionality for the respective systems.

 

For version control, our plan is to develop a tool to migrate files from WSS to TFS.  At this time, WSS lists will not be migrated into work-items, but we do recognize this as desirable tool for WIT.  The first tool are planning to develop for WIT will migrate data between an open source bug tracking system and TFS.  Although we considered developing the WSS list tool, bug tracking systems are typically more complex than the WSS list feature, and providing a tool to convert WSS lists would not illustrate many of the interesting parts of a WIT migration tool.

 

Are there any suggestions for migration tools that we should be targeting for the future?

Filed under:

Comments

# mmitrik said on November 6, 2006 7:34 PM:

One of the comments on my previous blog entry concerned a TFS to TFS tool, so I'll address that here.  We do recognize the need for this tool, but felt that it was a fairly uninteresting tool to provide initially (much like the WSS list tool).

The second part of that comment brought up the idea of merging two databases into one.  One feature of the toolkit is the concept of a session.  Using sessions, one could migrate data from multiple sources into TFS, and sources could be within a single server or from multiple servers.

# Vilx- said on November 7, 2006 11:09 AM:

But I understand then, that such a feat (merging two TFS servers) will not be possible with just the out-of-the-box product, right?

Vilx-

# RobertHorvick said on November 7, 2006 4:39 PM:

You are correct that TFS to TFS migration is not a scenario we are providing out of the box.  The goal of the toolkit is to provide a foundation on which migration tools can be written.  This should enable others, such as yourself, to create the migration tools you need without having to reinvent so many wheels.

For many reasons that have been debated at length the decision to create the WSS solution is the current plan.

# juvander said on November 15, 2006 1:28 PM:

Why only migrate, why not enable synchronization as well?

Bug tracking systems are one part for the migration, but systems like test management have valuable data that different teams need to keep in sync. Plain simple tester does not (need) to use tool like TFS, but test management UI and vice versa.

Not all the testers have capabilities to use tool like TFS. I have seen many business users who do not have very deep understanding of tools like TFS...

# EdGarrity said on November 20, 2006 1:23 PM:

Any plans to provide migration tools for exchanging work items with Mercury Test Director?

# juvander said on November 30, 2006 12:34 AM:

For Mercury - TFS sync, see this: http://onroad.juvander.fi/community/blogs/news/archive/2006/11/20/tfs-bug-item-synchronizer-1-1-for-mercury-quality-center-is-now-available.aspx

# Robert Horvick's Weblog said on December 29, 2006 10:28 PM:

As Matt has mentioned on the TFS Migration blog we’re working on a migration toolkit and, specifically,

Anonymous comments are disabled

Search

This Blog

Syndication

Page view tracker