Subversion Data Migration Features and Support

This page describes the major features and data migration support details for the various VCS tools supported by Importer for SVN, our free Subversion migration tool.

Subversion migration from CVS, PVCS, VSS, ClearCase, MKS, StarTeam

Polarion's SVN import tool currently supports migration to Subversion from the following RCS tools:

Migrating to Subversion from CVS

The cvs2svn tool migrates and converts data from CVS to Subversion (SVN).

The Java library javacvs is used for working with a CVS repository
The transformation preserves commits, authors, commit messages and dates of commits
Transformation converts CVS branches and tags to Subversion branches and tags
Commits are grouped as atomic commit (revision) in Subversion
Logging (output to console, logging level) can be tuned in configuration file (using log4j configuration)
Provider can work with remote repositories via CVS 'pserver' protocol
Non critical errors in the repository resolve automatically

TOP

Migrating to Subversion from PVCS

The pvcs2svn tool migrates and converts data from PVCS to Subversion (SVN).

For work with PVCS repository external program pcli is used. (From merant pvcs distribution)
The transformation preserves commits, authors, commit messages and dates of commits
Transformation converts PVCS branches to SVN branches
Transformation converts PVCS labels to SVN tags
Logging (output to console, logging level) can be tuned in configuration file (using log4j configuration)
Provider can work only with local repositories (or mounted to local file system)
Non critical errors in repository resolves automatically

TOP

Migrating to Subversion from Visual SourceSafe™

The vss2svn tool migrates and converts data from MS Visual SourceSafe to Subversion.

External tool ss is used to access the VSS repository (part of VSS client distribution)
The transformation preserves revisions, authors, commit messages and dates of commits
Logging (output to console, logging level) can be tuned in configuration file (using log4j configuration)

TOP

Migrating to Subversion from Rational ClearCase™

The cc2svn tool migrates and converts data from Rational ClearCase to Subversion.

External tool cleartool is used to access the ClearCase repository (part of ClearCase installation)
The transformation preserves revisions, authors, commit messages and dates of commits
Transformation converts ClearCase branches to SVN branches
Transformation converts ClearCase labels to SVN tags
Logging (output to console, logging level) can be tuned in configuration file (using log4j configuration)

TOP

Migrating to Subversion from MKS™

The mks2svn tool migrates and converts data from MKS to Subversion.

Supports MKS2009 and later
Supports both API &/or CLI(si) to access the MKS repository (requires MKS client installation)
Supports the generation of multiple subversion repositories from MKS projects with external linking.
Supports the transformation of MKS “Change Packages” to SVN tags
The transformation preserves revisions, authors, commit messages and dates of commits
Transformation converts MKS branches to SVN branches
Transformation converts MKS revision labels to SVN tags
Logging (output to console, logging level) can be tuned in configuration file (using log4j configuration)

TOP

Migrating to Subversion from StarTeam™

Logging (output to console, logging level) can be tuned in configuration file (using log4j configuration)
Provider can work with remote repositories via CVS 'pserver' protocol
Non critical errors in repository resolve automatically

TOP

Requirements

J2RE/J2SDK 1.4
External tool to access the source repository (for PVCS, VSS, ClearCase and VSS), which is the part of source repository distribution.

TOP