How can we improve Team Services?

Import/export data from Visual Studio Online

possibility to export a collection and import it in an on premises installation and the other way

671 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Marco CusinatoMarco Cusinato shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    FabienFabien shared a merged idea: Import a full TFS database on Visual Studio Online  ·   · 
    Steven SpyrkaSteven Spyrka shared a merged idea: Export and Import Feature to Team Foundation 2013 Server  ·   · 
    Anonymous shared a merged idea: Make an export/import to archive function for Visual Studio Online  ·   · 
    Akash KavaAkash Kava shared a merged idea: Migrate Existing TFS Projects to TFS Cloud Service  ·   · 
    Larry CarterLarry Carter shared a merged idea: Migration from On-Premise to Team Foundation Services  ·   · 
    Derek NoonanDerek Noonan shared a merged idea: Provide a means of migrating from on-prem TFS to cloud TFS  ·   · 
    Nicolas LouisNicolas Louis shared a merged idea: Migrate Team projects from private TFS to TFS Azure  ·   · 
    started  ·  Visual Studio TeamAdminVisual Studio Team (Product Team, Microsoft) responded  · 

    I’m happy to announce that we’ve started work on enabling data import to VSTS from TFS. This will enable customers to detach and import a collection into a VSTS account. We’re hoping to have a private preview available in 2016 Q2. We’ll check back and update this item once we have more details to share.

    Rogan Ferguson
    TFS Program Manger

    26 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • LayneLayne commented  ·   ·  Flag as inappropriate

        Why can't I restore my database from backup to the cloud? It's simple in TFS. Should be simple in the cloud.

      • LayneLayne commented  ·   ·  Flag as inappropriate

        I have 1.3 work items along with a lot of source. Original estimates from OpsHub migration was over 50 hours. Since OpsHub has slowed down considerably during the process, and thrown several errors, we're looking at over 300 hours now. THIS WILL NOT CUT IT!!!!!!!!!!!!!!!!!!!!!!!!!!!

      • Visual Studio TeamAdminVisual Studio Team (Product Team, Microsoft) commented  ·   ·  Flag as inappropriate

        Hi Chris,

        Sorry for any confusion that might have been caused. It looks like that item was a duplicate ask for data import. It was archived due to low votes and how long it went without getting any new votes. I have merged the suggestion you linked to into this one. We’ll be using this UserVoice item to convey our status on data import. We’re committed to providing a first class data import solution for Visual Studio Team Services.

        Rogan Ferguson
        TFS Program Manager

      • Chris BailissChris Bailiss commented  ·   ·  Flag as inappropriate

        Lack of import into VSO is a complete blocker for us. OpsHub etc simply not up to the job. Having check in dates, users, etc migrated (into the correct fields is VSO, not as comments) is a key pre-req for us. Until then, you can keep adding all the other features you want, but we won't be migrating. Please add this basic feature soon (I am surprised it hasn't been added yet).

      • Devon HazellDevon Hazell commented  ·   ·  Flag as inappropriate

        I need to move data from one VSO project to another VSO. We are currently using VSO as well as Microsoft Test Manager, so we would need to copy Features, Users Stories, PBI, Tasks, Test Cases and Requirements. We are loving this product, but migration from one VSO to another VSO is something that is sorely needed. Thanks

      • Anonymous commented  ·   ·  Flag as inappropriate

        Hi

        I need to merge two VSO's, enabling export is a posible path. Please enable export againg !

      • Morten ØstergaardMorten Østergaard commented  ·   ·  Flag as inappropriate

        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 AdlerRyan Adler commented  ·   ·  Flag as inappropriate

        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!

      • Anonymous commented  ·   ·  Flag as inappropriate

        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.

      • PhilipPhilip commented  ·   ·  Flag as inappropriate

        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 PaloJussi Palo commented  ·   ·  Flag as inappropriate

        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.

      • Adam PAdam P commented  ·   ·  Flag as inappropriate

        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 PageJeff Page commented  ·   ·  Flag as inappropriate

        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.

      • Akash KavaAkash Kava commented  ·   ·  Flag as inappropriate

        We have TFS server on some dedicated server, we want to migrate our Source code from old server to tfs.visualstudio.com , it would be helpful to migrate source from old to new with user mapping so the history of checkins remain same.

      ← Previous 1

      Feedback and Knowledge Base