Migrate from TFS 2013 to Visual Studio Online
-
Upload
davide-benvegnu -
Category
Technology
-
view
348 -
download
2
description
Transcript of Migrate from TFS 2013 to Visual Studio Online
![Page 1: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/1.jpg)
Davide BenvegnùInternational Development Manager – Aruba.it
DotNetToscana Staff Member
[email protected] - blog.dbtek.it
www.davidebenvegnu.com -
@davidebenvegnu
Migrate from TFS to Visual Studio Online
ALM Deep dive with TFS 2013
#vsalmdeep
![Page 2: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/2.jpg)
Session Lineup
About OpsHub Visual Studio Online Migration UtilityFunctionalities & LimitationsRequirementsLet’s migrate!
#vsalmdeep
![Page 3: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/3.jpg)
Event Sponsor
#vsalmdeep
![Page 4: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/4.jpg)
About OpsHub
#vsalmdeep
![Page 5: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/5.jpg)
What is it?
#vsalmdeep
From OpsHub website:
OpsHub Visual Studio Online Migration utility helps customers wanting to migrate the most commonly requested data from an on-premises Team Foundation Server to their Visual Studio Online account.
It is designed for basic migration scenarios.
![Page 6: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/6.jpg)
How does it work?
#vsalmdeep
It supports a one-time one-way migration It supports migration from TFS 2010, TFS 2012, and TFS
2013 It uses the “normal” TFS endpoint connection to export
data from TFS It uses the new Open API (REST based) to import data
to VSO
![Page 7: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/7.jpg)
Functionalities &
Limitations
#vsalmdeep
![Page 8: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/8.jpg)
Data the tool will migrate
#vsalmdeep
Source code under TFVC (including changesets, labels and version control history)
Work items, including links, tags, and attachments. (Excludes any customizations and data associated with customizations, such as custom fields, custom workflow, and custom forms.)
Images in work items as attachments to the work item. Test cases and previously saved test results. Each history action on behalf of the original user so as
to preserve as much history as possible.
![Page 9: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/9.jpg)
Data the tool will migrate
#vsalmdeep
Important:
During migration, the following field values are set to a default user and current system time: Person name fields: Created By, Closed By, Activated By,
Resolved By. Date fields: Closed Date, Activated Date, State Change
Date, Accepted Date, Resolved Date, Called Date, Revised Date, Changed Date, Created Date.
![Page 10: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/10.jpg)
Data the tool won’t migrate
#vsalmdeep
Git repositories. Data associated with builds, test plans, test suites,
releases, and lab environments. Source code date stamps and labels created at the
team project collection level. If there are revisions, which are across projects, and
some of the projects are not selected, the revisions will not be processed.
Customization of all work tracking objects: fields, forms, link types, categories, or process configuration.
![Page 11: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/11.jpg)
Data the tool won’t migrate
#vsalmdeep
Comments and dates associated with Attachments. Customization of Kanban boards. Alerts, queries, and event history. Teams, team memberships, team alerts, personal and
team favorites, and team room archives. Accounts, group memberships, and user permissions.
![Page 12: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/12.jpg)
Custom WITs
#vsalmdeep
Important:
Migration will fail if the utility detects any
customization of the Work Item Types.
![Page 13: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/13.jpg)
Custom WITs
#vsalmdeep
If you have customized any of your work item types, you will need to remove these customizations.
The easiest way to remove the customizations is to download the original process template used to create your team project and import the WIT XML definition files using witadmin importwitd.
witadmin importwitd /collection:CollectionURL [/p:ProjectName] /f:FileName [/v]
![Page 14: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/14.jpg)
Requirements
#vsalmdeep
![Page 15: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/15.jpg)
Installation pre-requisites
#vsalmdeep
OpsHub tool requires a 64bit Windows OS
Ideally on your application-tier server that hosts TFS
It needs a valid email address (for verification code)
![Page 16: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/16.jpg)
Migration pre-requisites
#vsalmdeep
VSO account used for migration must be member of the Project Collection Service Accounts group.
On VSO you must create projects with exactly the same name of TFS projects to import.
On VSO you have to create as many users as been contributors to your TFS team project(s) (you’ll have to map them)
![Page 17: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/17.jpg)
DEMOLet’s migrate!
#vsalmdeep
![Page 18: Migrate from TFS 2013 to Visual Studio Online](https://reader036.fdocuments.us/reader036/viewer/2022083001/557ab0ffd8b42a79378b503b/html5/thumbnails/18.jpg)
Recap It’s easy to migrate from TFS to VSO At the moment not all data are imported, only the
“majority” of them Customization cannot be imported
#vsalmdeep