Davide BenvegnùInternational Development Manager – Aruba.it

DotNetToscana Staff Member

davide.benvegnu@gmail.com - blog.dbtek.it

www.davidebenvegnu.com -

@davidebenvegnu

Migrate from TFS to Visual Studio Online

ALM Deep dive with TFS 2013

 #vsalmdeep

Session Lineup

About OpsHub Visual Studio Online Migration UtilityFunctionalities & LimitationsRequirementsLet’s migrate!

 #vsalmdeep

Event Sponsor

 #vsalmdeep

About OpsHub

 #vsalmdeep

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.

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

Functionalities &

Limitations

 #vsalmdeep

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.

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.

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.

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.

Custom WITs

 #vsalmdeep

Important:

Migration will fail if the utility detects any

customization of the Work Item Types.

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]

Requirements

 #vsalmdeep

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)

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)

DEMOLet’s migrate!

 #vsalmdeep

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