Import data from TFS on-prem into VS Team Services
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.
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.
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
I wanted to provide a long overdue update regarding our progress on enabling data import to Team Services from TFS. Imports will be handled by taking a detached collection and migrating it into a brand new Team Services account. Imports done using this feature bring along full work item and source control history. We’ve been working with a limited set of customers during the private preview to increase the amount of automation in this process. Our next target is to get a private preview of full self-service, customers queuing their own imports, sometime this fall.
In the next week or two we’ll be releasing documentation on the entire import process which should answer a lot of your questions. We’ll be updating this announcement with a link to that documentation once it’s live.
Note, this UserVoice suggestion doesn’t not include exporting data from Team Services to TFS. If you’re interested in that scenario, please vote for the following suggestion:
Would love to join this preview. We're porting over several projects in Q4 that this would greatly help. Will start working now to ensure we're on the latest per Ed's comments below.
Is it possible to join preview? We plan to migrate from TFS to Team Services in the near future.
Mikael Sundstrom commented
Any news on this? I really would like to retire our old TFS...
Brad Hager commented
If I could be part of the preview that would be great. I'm trying to migrate our whole on premise TFS 2015 environment to VSTS but the OpsHub utility is just too limiting in that it loses far too much history in the migration process.
"Our next target is to get a private preview of full self-service, customers queuing their own imports, sometime this fall." - so does this mean general usage is still a ways off? Disappointing!
lack of this tool prevents consideration of VSTS...
Nate Boettcher commented
I would like to be included in the preview. This issue is very important for us.
I would like to be part of this preview.
Adam Londero commented
Rogan - How can we express an interest to be involved in the trial?
Ed Blankenship commented
@Ali Se: That's a really good question. If there are team projects that you no longer need or want to import into your Visual Studio Team Services account, you can consider either deleting the team projects or splitting those old team projects into a separate collection. You could even call the collection the "Archive Collection." Be careful if you do choose to split your collection, you won't be able to "merge" the collections in the future so it's a one-way process. Here is some more documentation about how to split your team project collection: https://msdn.microsoft.com/en-us/library/dd936158(v=vs.120).aspx
Ali Se commented
I really have a lot of old (closed) projects in the same collection with new and current projects.
I don't want these projects to be migrated, Do you have a tip or workaround for this situation?
Thanks in advance.
Any news on the release of this?
Chris C commented
My team is VERY interested in this! How can we get in on the preview once it is released?
Ed Blankenship commented
I'll ask Rogan to come update this User Voice item but we've been making some good progress. I wanted to share a few tips to help everyone be as prepared as possible.
1) My first tip for everyone who want to import their data from VSTS: You'll want to make sure you are on the latest update of Team Foundation Server whenever you're ready to import. I would get that process started now since for many teams that may take some time: https://www.visualstudio.com/en-us/news/releasenotes/tfs2015-update3-vs
2) My second tip is if you have really old team projects, you'll want to make sure that you have used the "Configure Features" tool on every one of your team projects and make sure you are successful: https://www.visualstudio.com/en-us/docs/work/customize/configure-features-after-upgrade. This can potentially take some time so go ahead and be prepared.
Alan T commented
Rogan, I am interested. Can you publish an update as to when its scheduled to release, since we are out of the 2nd Q now?
Ali Se commented
If the preview is available, I'm very interested, and like to move my company from on-prem to Team Foundation Services.
Greg Read commented
I am very interested in the preview when it is available.
Julian Cook commented
Have i missed the update on this ?
Mike Branstein commented
Rogan, I have several customers VERY interested in moving from on-premises TFS 2015 to VSTS. Some could be good cases, as they have TPCs originating from TFS 2010 and earlier. One is actively using Build and Release vNext. Is there any chance to get into the private preview?
Can this feature move projects between different VSTS account?
Phillip Larsen commented
Would like to be part of the preview when it is available