Last Update: 8/3/2017

The TFS Database Import Service for Visual Studio Team Services (VSTS) is currently in preview.

Post Import

A Visual Studio Team Services (VSTS) account is ready for use once an import has completed successfully. However, there are common tasks that you should perform before opening the account up to all of your users. Below is a list of the most common after import tasks that should be completed. Tasks are listed in recommended order of completion.

Immediately After Import

Immediately after the account becomes available you will want to take a small team and perform spot checks on the account. It's recommended that this team consists of the project collection administrators. This shouldn’t be an in-depth check, but rather making sure that major pieces from your collection were brought over. Did your source code get imported? Are you seeing your build history? Are all of our area paths still present? It's best to confirm these artifacts are present before opening the account to the entirety of your user base.

After spot checking the account you will want to consider if you want to rename it. Renaming a VSTS account is a simple operation, but it has large impacts on users currently using the account. Some examples being Team Explore connections breaking or bookmarks no longer working. Getting a rename out of the way while it's just a small group of users using the account allows the rest of the users to come in and configure their connections once.

Set up Billing

To pay for users or services in VSTS, like hosted build and deployment agents, you'll need to set up billing for your VSTS account. You can do this when you make your first purchase by selecting an Azure subscription that you'd like to use for billing. This links the subscription to your VSTS account, so that all future purchases for your VSTS account will use the same Azure subscription for billing.

Manage Users and Access

Your VSTS account includes 5 free users with Basic access. Basic includes features like Git and Team Foundation version control, tools for agile planning and Java teams, and more. Also, you can add Visual Studio subscribers for free - they get basic features plus additional features, based on their subscription level. Add Stakeholder for free, too—they can access your work items and view your backlogs.

This means that you shouldn't have to take any other import steps if your identity mapping file has just 5 users with Basic access, Visual Studio subscriptions, and Stakeholder access. If you have more than 5 users with Basic access, you'll need to pay for these users in your VSTS account. Just make sure to do this before the end of the calendar month when you import. Otherwise, these users' feature access will change from Basic to Stakeholder on the 1st day of the next calendar month. To find out how many additional users you'll need to pay for, visit your VSTS account (https://{youraccount}.visualstudio.com/_user) so you can find the number of paid users that you've assigned:

User Summary on a VSTS account

Dry run imports do not have their licenses reset on the 1st of the month. Unlike production imports, their grace period extends for the life of the account. So you don't need to worry about purchasing licenses while testing out an import.

Builds

Next, you will want to configure your build agents. As part of the migration, all of your build definitions have been brought over, but agents and pools need to be reconfigured against the new VSTS account. VSTS offers the ability to use a hosted pool of build agents that you can pay to use, or you can connect your private build agent(s). It's important to note that only one private build agent is included for free. After that there is a fee for having additional private build agents. To pay for hosted and private build agents you will need to link a subscription to your VSTS account. See the following resources for details on performing this task:

If you plan on using your existing on-premises private build agents, there is one more recommended step that needs to be taken after registering them to your new account. Clearing their cache will ensure that you don't encounter any build issues related to older TFVC or Git pointers to your on-premises TFS collection. See refreshing caches on client computers for details on how to accomplish this task.

Notifying the Team

After getting your builds running and license subscription configured, it's recommended that the account be opened up to all users for validation. This is when individual users can ensure that all of the content is in place, they have the right access level, and that they can pull code. Be sure to point users to our documentation on connecting to VSTS from all of our supported IDEs and Team Explorer. Users of TFVC with local workspaces will need to remap their workspaces against the new account and Git users will have to reconfigure their remotes to be able to pull code. If anything is reported as missing from the migrated account, please reach out to vstsdataimport@microsoft.com. For other functional issues, please reach out to customer support.