Visual Source Safe Upgrade Tool for Team Foundation Server

Free

The official upgrade tool to move your Visual Source Safe repositories into Team Foundation Server

(21) Review
Visual Studio
2012, 2010
Download (52,030)
6/19/2014
1.1
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (21)
Sign in to write a review
Sort by:

by kio07 | June 22 2015

Hello,
This tool work fine to upgrade to VSO or on-premise TFS.
But how can i specify a "usermap" with the wizard ?
I can specify a "usermap" with the command-line but in command-line i can't migrate to VSO, i can just migrate to a on-premise TFS.
Otherwise, how can i migrate to VSO in command-line ?

Thank you

by SQLPilot747 | May 27 2015

Is there a way to prevent duplication directory names when migrating with the tool from VSS to NFS 2013. For example on the VSS side $\ProjectDemo but when I migrate that over to TFS 2013 it carries over the project name from VSS under the new project name in TFS 2013 which looks like this after the migration is complete: ServerName\DefailtCollection\ProjectDemo\ProjectDemo

by Brettney | May 19 2015

Have to say I was very pleasantly surprised that this tool worked so smoothly. Upgraded from Visual SourceSafe to Visual Studio Online. All different types of projects, C#, VB.Net, VB6, database, all handled without issue.

by PaulWesterman | April 22 2015

The import went smoothly except for a few issues with paths being too long. We also appear to have lost some history in the import, we only have history for the current year.

by peter715 | September 15 2014

hi,

Is there a way to change the workspace. I am running into max character for path is reached. so I want to change the workspace to e: instead of c:\converse
. or is there is a way to bypass max character for path error?

Regards,
Man

by Russell.robinson | April 29 2014

Hello. Trying to install the latest version on 2012 server to upgrade my VSS to tfs. I am getting compatibility mode error.Is it possible to provide a timeline for a fix?

Thanks

by Claudio77 | April 22 2014

having the same issue
Unable to install on Win8.1.
get the error: Windows Program Compatibility mode is on. Turn it off and then try Setup again.
No matter what I do, unable to continue.
Any solution?
I tried to turn off compatibility and tried with all compatibility options
with no success.

EdH - MSFT June 19 2014
| Edit |
Delete

Just updated to run on Windows 8.1

by Miami486a | March 19 2014

Unable to install on Win8.1.
get the error: Windows Program Compatibility mode is on. Turn it off and then try Setup again.
No matter what I do, unable to continue.
Any Ideas?

EdH - MSFT June 19 2014
| Edit |
Delete

Just updated to run on Windows 8.1

by Pawel Luczak | March 18 2014

Hi,
we have the same problem as Talksocke.
We installed TFS 2013 in basic configuration with SQL Server Express 2012 on a Windows Server 2008 R2 machine.
Teamproject "SubProject" was created wit TFS VC in DefaultCollection.
Analyze runs fine.
But the migration fails with
ERROR: Object reference not set to an instance of an object".

Our settings.xml:
<?xml version="1.0" encoding="utf-8"?>
<SourceControlConverter>
<ConverterSpecificSetting>
<Source name="VSS">
<VSSDatabase name="C:\Users\Administrator\Desktop\vss2005\vss2005\database"></VSSDatabase>
<SQL Server="192.168.200.45\SqlExpress"></SQL>
</Source>
<ProjectMap>
<Project Source="$/MainProject/Thrunk/SubProject" Destination="$/Project"></Project>
</ProjectMap>
</ConverterSpecificSetting>
<Settings>
<TeamFoundationServer name="192.168.200.45" port="8080" protocol="http" collection="tfs/DefaultCollection"></TeamFoundationServer>
</Settings>
</SourceControlConverter>

Regards
Pawel

by Michael Lohss | January 10 2014

We upgraded from SS 8.0 into TFS 2012 with the databases hosted on Sql 2012 SP1 cumulative update 7. We found when converting projects with history, we always got the error "Migration failed due to "TF60086: Unable to read or write to the intermediate database on Microsoft SQL Server <Instance Name>. A trigger returned a resultset and/or was running with SET NOCOUNT OFF while another outstanding result set was active." When we pointed the VSS upgrade tool to a 2008R2 instance for the temporary database it creates, we loaded the full history into our TFS repository in SQL 2012 without error.

by Boris2000 | December 23 2013

At the first glance, every looked OK, but then we discovered that only this year history was migrated to TFS 2013.

Has anyone experienced this problem and do you know how to fix it?

We have 7 years of data and history in VSS 6. We upgraded the repository to VSS 2005, run the analyser and then used this Wizard to migrate the data to TFS 2013. Everything completed successfully, but looking at the history in TFS, it only contain the history for this year, nothing for the previous 6 years. I am in the UK so I wonder if this is some date format issue (US months mixed up with UK days).

by Warren R | November 08 2013

I'm having problems installing this on my Windows 8.1 OS. I keep getting the error message "Another setup is already running. Please wait for it to finish before trying again.". I've already checked the compatibility settings on the tfs_VssUpgrade.exe file and it does not have any settings turned on. This product worked fine on Windows 8 but after upgrading to Windows 8.1 it will no longer install.

by TNJMAN | September 08 2013

Nice. Wish I had this 5 years ago - needed to do exactly this type of thing. Thanks.

by michelk | August 19 2013

2 words: works good

thanks for publishing this tool!

by vincentw56 | July 26 2013

It works with TFS 2013 but only if you are using the TFS version and not GIT.

by Sergio Parra | April 27 2013

It helps me to upgrade my old visual source vb6 projects to tfs

by A. Coonce | April 15 2013

I had no problem at all migrating our TFS databases with this tool. This is a dramatic improvement over earlier releases.

by DEW4242 | April 14 2013

this is so complicated there has to be video tutorials for this its a must

by Talksocke | March 22 2013

I am agree with BHPatel. The wizard is not very flexible. But after all it worked.
Because I want to migrate only some selected subprojects, I tried out the command line tool...
The analyze step worked fine. After that I added all information that are needed for the migration into the settings.xml.
But the migration did not work. I got the following error:

> VssUpgrade migrate settings.xml

Microsoft (R) Visual SourceSafe Upgrade version 11.0.0.0
for Microsoft (R) Visual Studio 2012
Copyright (c) Microsoft Corporation. All rights reserved.

ERROR: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.

The english translation of the error is
"Object reference not set to an instance of an object".

I don't know how to get more error information. Any idea or bugfix?

by BHPatel | December 26 2012

The tool is not flexible at all. The tool does not let me pick VSS database below roots level project. In my case I did not wanted to migrate all my applications to TFS. I only wanted to migrate one application out of 10 application. The tool did not let me pick one application.

I did not want to physically log in to VSS server to run the tool. I should be able to use this tool from Client machine and pull the code out of VSS and commit the code to TFS.

I disagree with the approch of the migration used by this tool.

EdH - MSFT April 30 2013
| Edit |
Delete

You can choose a specific folder, and you don't need to run it on your VSS machine

1 - 20 of 21 Items