- Global Availability.
- Immediate Access to updates as soon as they’re available.
- Higher Security.
- Easy Deployment to Azure.
Note: Using Excel and/or Microsoft Project has limitations for images, attachment, history, and other things.
I’ll demonstrate another tool, which is TFS Integration Platform. Using TFS Integration Platform requires SQL Server 2012 first, as the tool is a little bit old. This tool migrates everything except the relations between work items.
Note: This tool is deprecated, but you can still use it at your own risk.
Migration with TFS Integration Tool is very easy, but again, we have a limitation that relations between work items can’t be migrated.
Before getting into the real work, you should have access to both TFS & VSTS with full administrative privileges. TFS Integration Platform is only helpful when You want only to migrate work items, with no need to migrate links & relations between them.
Understanding TFS Artifacts Association and Relations
TFS doesn’t only provide work items or test cases, TFS is simply everything needed to manage work, The following diagram provides some general explanation for that:
It’s clearly shown that relations in TFS make the logic for work, therefore it’s very important to maintain the relations between work items, not only the work items itself.
Step 1: Getting Environment Ready
Before getting started, we will need to install Microsoft SQL Server 2012. Additional help for SQL Server 2012 installation is available here. Please note SQL Server 2012 is essential for compatibility, as the TFS Integration tool is deprecated and are is supported for the newer version. So, make sure that you have connected to the SQL Server 2012. You can do this using a later version of SQL Server Management Studio.
- Make sure you’ve selected SQL Server 2012.
- Click on Connect.
- Download & Install Visual Studio 2010 (Required to provide Object Model for the tool) and Visual Studio 2012 (Required to provide TFS Connectivity for the tool).
- Download & Install TFS Integration Platform.
Note: TFS Integration Platform must be installed after SQL Server 2012 and Visual Studio 2010 and Visual Studio 2012, otherwise it won’t work.
Step 2: Migrate
1. Open TFS Integration Platform Tool and Click Create New
2. Click on Team Foundation Server Folder
3. Choose Migration Options, you can Migrate Source Control, Work Items or Both, I choose Work Items Only.
4. Click Open
5. As a workflow type, from drop down menu select One Way Migration
6. Click on Configure
7. In a drop down menu, select TFS 11 Migration WIT Provider.
8. Select the right TFS Server to connect to the original TFS.
9. Under Team Project Collection, select the Team Project Collection which you want to use for this migration.
10. Under Team Projects, navigate to the Team Project that you will use and click on it.
11. Click on Connect to connect to TFS.
12. Click on Configure to configure the targeted Source and select TFS 11 Migration WIT Provider again.
13. Under menu Select the Team Foundation Server to select the targeted VSTS to connect to it.
14. Under Team Project Collection, select the Team Project Collection which you want to use for this migration.
15. Under Team Projects, navigate to the Team Project that you will use and click on it.
16. Click on Connect to connect to VSTS.
17. Click Save to Database
18. Click Start Migration
19. Set back and relax, Migration can take few hours if you have thousands of work items. When the migration will be finished, you’ll be able to see the notification in the window of TFS Integration tool.
20. Additional Note, here is how your SQL Server 2012 Database looks like for Migration
The TFS Integration Platform Tool is a pretty straight forward tool to use for migrating items from TFS to VSTS. The tool enables the migration of everything, including the acceptance criteria, discussions, history, and attachments, but not the links between the work items.
However, as already mentioned in the beginning of this post, the tool is deprecated, which means that no further development will be performed and there is no current support available for it. The previous documentation for the tool is currently still available on the Codeplex.