TFS migration tool status

Dec 3, 2008 at 7:04 AM
Edited Dec 3, 2008 at 1:47 PM
This is an update to let everyone know that despite the silence, there is work happening behind the scenes on the TFS migration tools.  Brian Harry's 9/17 blog post outlines our high-level plan for the future of the tools.   We have a small team working to identify the changes needed to support the production use of the TFS migration tools for the internal dogfood-sync scenario that Brian describes.  Design work is taking into account requirements from the internally-focused dogfood-sync scenario as well as broader customer-focused input drawn from our MVP and field communities as well as the comments and experiences posted to the TFS to TFS Migration Tool and TFS Migration and Synchronization Toolkit sites.  Brian summarized the high-level plan to get to a production quality release on CodePlex fairly well back in September: "Once we get the synchronization scenario nailed, we will do another public update to these tools."  We do not have the sync scenario nailed... yet.  The changes being considered at the moment are fairly large and will take some time to implement, but look like the sort of structural changes that will help put some of the most troublesome problems behind us.  We will share more details on the changes being considered once those plans firm up.

In the meantime, it is important to understand the scenarios where the TFS to TFS migration tool is meant to be used and the limitations of the tool before trying to use it (home).  The current version of the tool is at a pre-release quality level (releases).  The rough edges in current drop of the translate in some cases to problems that cost more time in migrating or setting up a sync relationship than should be required.  The only real remedy for that in the short term is to try to avoid using the tool if possible, and if not, to consider that the experience may not be a smooth one and try to plan for that.  We will try to update the pre-release drop of the tool with bug fixes, but the migration experience may not be smooth until we get that larger release out the door next year sometime.  Sorry.

Bill Essary [MSFT]

Updated: 12/3 - Clarified the production quality release vs. interim release plans