Rules to Better TFS Migration to the Cloud

​​

Hold on a second! How would you like to view this content?
Just the title! A brief blurb! Gimme everything!
  1. Do you know all the ways you can migrate to the cloud?

    The 7 options are:
      • Option 1: Take the latest version
      • Option 2: + Migrate Work Items using Excel
      • Option 3: Convert TFVC to Git
      • Option 4: + Community Tool: VSTS Sync Migrator (includes Work Items)
        by Martin Hinshelwood (ex-SSW)
      • Option 5: OpsHub 
      • Option 6: Timely Migration
      • Option 7: TfsMigrator - Microsoft​​

    Watch the video:​

     

  2. Do you know all steps required when migrating to the Cloud?

    Planning is an important part of your TFS Migration to the cloud therefore it is highly recommended to read the TFS Migration Guide.

    You may also watch Rogan's demo:

    ​​​​

    ​​

  3. Do you keep your TFS Build Server?

    ​​After you migrate to the cloud you will want to keep your TFS Build Server because you Build Definitions are preserved during the migration. All you have to do is to reconnect the Build Controller and Build Agents to the new account.

    Read this rule to learn more about agent limitations.​

  4. What to do with old employees?

    When migrating from TFS to the cloud you will find that a list of historical users may be quite long.
    ​​old-employees-to-the-cloud.jpg​​Figure: TFS Identity Mapping​

    Many of these users are likely to be gone but they are preserved in TFS for historical purposes. What are you going to do with them? 
           A) All account stays active (total 700 in AD) – this is a hard one because you need to bring all accounts in Azure AD and generally you don’t need those users
           B)  Old employees are carried over as phantom  (so only 40 are migrated) – Recommended because you will still see the history but not those accounts are not active anymore
           Eg. If Paul Stovell comes back he needs a new account (because you can't reuse the SID)