It has never been a better time to migrate from TFS to VSTS!
From the day Visual Studio Team Services (VSTS) first went live, customers wanted a path to migrate their existing on-premises Team Foundation Server (TFS) data. For a long time, only low-fidelity paths existed – migrating a subset of resources at their “tip” values, using tools to preserve a bit more history, and so forth.
Just over a year ago, we announced the preview of our TFS Database Import Service, which enabled a much higher fidelity migration path – all work items with full history and existing IDs, all TFVC data with full history, and much more. Since then, hundreds of companies of all sizes have used the service to migrate their TFS data into VSTS. And with their migrations, these companies have started enjoying the many benefits of being in VSTS – access to the latest and greatest features with updates every three weeks, availability guaranteed by a financially backed SLA, single sign-on with Azure Active Directory, and lots more.
Over the past year we have been focused on making the import process faster, more reliable, and easier to use. With all these improvements in place, I’m proud to announce the general availability of the TFS Database Import Service. No more import codes required, no more limitations on when imports can be queued, and a greatly simplified import experience.
If this is the first you’ve heard of the TFS Database Import Service, see it in action in our Channel 9 Video.
If you are thinking about performing an import, download the Migration Guide and get started today.
If you’ve previously reviewed our documentation, it’s worth noting that the identity import experience has changed. The identity mapping file is no longer a required input. Instead, the identity map becomes a log that can help you understand how identities will be imported. Checkout our documentation to learn more about these changes.
There has never been a better time to migrate. We’re looking forward to seeing you in VSTS soon!
Program Manger, TFS/VSTS