Import/export data from Visual Studio Online
possibility to export a collection and import it in an on premises installation and the other way
Import a full TFS database on Visual Studio Online. I don't want to have to use a migration tool that takes a week (and bug at the middle of the process) to redo all the commits. I would love to see a feature that would allow me to generate an archive from my on-premise TFS and import it into Visual Studio Online.
Please create a feature to switch from tfs/visual studio online to a local installation of tfs and vice versa.
Please provide a way to import and export full Projects or the hole Account in Visual Studio Online. With this you can give Projects away, remove Projects from you account, restore them and make a Backup of your account.
Would like the ability to migrate TFS On-Premise to TFS Cloud Services. We have been using TFS for years now and want to keep our customizations and history.
Nothing would suit me better than to migrate all of my source to the cloud as I’d be able to work remotely then without needing to VPN into my home office but I cannot see a way to migrate such that I can bring all my history with me
First step, to move sources from a team project on a private TFS server to a team project in TFSPreview/Azure
Second, to migrate the structure of the team project and data depending on the amount to transfer
We have included both import and export from Visual Studio Online on our product backlog. Brian has some more information about data export available here: http://blogs.msdn.com/b/bharry/archive/2014/02/21/vs-online-early-adopter-program-extended-to-may-7-2014.aspx
Additionally, this week at TechEd North America we have announced that we have partnered with OpsHub to create a free migration utility to move the most requested data including history from TFS to VSO. You can find out more details on this migration utility that was released here: http://bit.ly/OpsHubBlogPost. We will also continue to include proper import support on our backlog for future investments.
Ed Blankenship, Ewald Hofman, and Andrea Scripa
Visual Studio Online Team
Seyyed Soroosh Hosseinalipour commented
Why disable export tab in VSO?! migrate a project collection from VSO to on-premise TFS is very much needed.
Morten Østergaard commented
I have tried both the OpsHub tool as well as the older "TFS Integration" tools, and have yet to succeed on transfering my (rather large) project from TFS to VSO. And even if I did succeed it seems it would run for several days to get data over and in that time we would not have a version control system... If there was a more "native" way of doing this, it would make the decision to move from TFS to VSO much easier. If we have to still keep running our old TFS server to get old file history, then I loose some of my arguments to migrate to VSO.
Ideally make it so that you can simply point VSO to a SQL database file from an on-prem TFS server and import that to VSO. I know this is a huge upload, but it could get it from Azure blob storage or something. The TFS management client on the server has migration tools like this already, so maybe this could be used with a small web front-end.
Ryan Adler commented
While OpsHub's tool is good for a basic case, without first-level support to import in the VSO API, we cannot use this. What I mean by this is, it needs to be possible to import date fields (created, updated, etc) as well as usernames to VSO from on-premises TFS. Without support to import dates, we cannot migrate - all our custom queries and reports would be useless. Please offer full support to import historical items into the API!
OpsHub sucks - tired of seeing the "Could not find a part of the path o:\......". I would rather have Microsoft create a sanctioned tool that can take an existing TFS environment, spit out the history to a GIT server, TFS Online, etc and be done with it. Just note that whatever I shove in to TFS Online, I want the ability to get it back out easily.
My management won't be completely comfortable with using VSO over an on-premises TFS setup until I can describe to them what contingency plan we have in the event of Microsoft discontinuing the service, either deliberately or as a result of a catastrophic failure. If I could take regular backups using an export of all VSO data (including work items, backlog, etc.) that could be used to recreate our project in such a situation, that would be sufficient.
Jussi Palo commented
VSO to VSO would be very much needed. World is full of company merges for example, that will require code to be moved from VSO to another VSO.
Ishita Rughani commented
May be you can try out this: http://visualstudiogallery.msdn.microsoft.com/28a90a17-d00c-4660-b7ae-42d58315ccf2
Adam P commented
So wait, I can't import my existing TFS repository into VSO? That's a no-go for me then. I need my history, plus I wouldn't feel comfortable putting my code in a repository that I can't export later on down the line. Until importing AND exporting my history exists, VSO is off the table for me.
Jeff Page commented
We also have a requirement to migrate a project collection from VSO to on-premise TFS. We were unable to complete a migration using TFS Integration Tools.
Rudi Larno commented
I attempted to use the TFS Integration Tools, but struck out due to several inexplainable issues.
Chris Lively commented
All we need as part of a migration is the check in notes.
Eddie Magadan commented
I agree, there should be an easy way to migrate your existing TFS configuration to the cloud.
John Hartwell commented
I'm seriously looking at moving to TFService as an option to migrate from our current internal TFS 2010 solution to TFS 2012. The ability to import our source and WI history is a significant factor. Is there a likely date for this yet?
Chris Patterson MSFT commented
Currently this is not possible. It is something we are planning to enable in the future.
Chris Patterson MSFT commented
We have plans to offer the ability to migrate from local TFS Server to a TFS Azure account in the future.
Marco Cusinato commented
I mean obviously from a menu action, not a command line (I didn't try, but I trust it works)