Version 4 should have VSS import
Please port the v3 vss import wizard to v4.
The route by vss2git failed big time probably on a binary in vss. The route by svn is also far from flawless (I could not even exportmy error free vss to svn).
![](https://secure.gravatar.com/avatar/88dee61c6eae0c505d1fd46c0b36485b?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
Unfortunately we decided not to support a specific vss importer. But we’ve migrated some teams from vss to plastic using fast-export/import and other third party tools
-
Adminpsantosl (Admin, plasticscm) commented
I appreciate your comments guys.
The "import business" is a really tough one. To say the least!
Our best possible result (a clean import) is your bare minimum expectation and anything else is not even good for you... which I totally understand but puts all importers on a very delicate position... :)
We'll do something to improve the VSS path to plastic... -
SWSBB commented
We came to plastic v4 from VSS, too. But we decided to start with a clear database, because 20 years of version history would pull the performance down, most likely. We still have our VSS archive to lookup old comments, which happens once a month.