Differences between revisions 39 and 40
Revision 39 as of 2007-07-26 21:34:05
Size: 4128
Editor: BrendanCully
Comment: a little publicity for the convert extension
Revision 40 as of 2007-10-06 07:08:09
Size: 4217
Comment: Add link to CvsconvertExtension
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
 * [http://hg.beekhof.net/hg/cvs-import hg-cvs-import] (need info)  * [http://hg.beekhof.net/hg/cvs-import hg-cvs-import] - (need info)

You can also convert from Mercurial to CVS:

 * CvsconvertExtension - (need info)


Your first option should probably be the ConvertExtension recently bundled with mercurial. It supports branches, incremental imports, and a few other nice features, and is maintained by the Mercurial authors. It currently only understands CVS, subversion and git. Otherwise, the following tools may be useful.

Arch / TLA / Baz 1.5

Tools for Arch conversion can be found at ArchConversion.


  • ["Tailor"] - a generic conversion tool.


Multiple convertors exist for converting from CVS to Mercurial:

  • ["convert-repo"] - the development version of Mercurial includes a CVS converter
  • ["Tailor"] - a generic conversion tool
  • ["fromcvs"] - a fast, incremental CVS to Mercurial converter
  • [http://hg.beekhof.net/hg/cvs-import hg-cvs-import] - (need info)

You can also convert from Mercurial to CVS:


A sample Darcs conversion script is available in the contrib/ directory of the Mercurial source.

For a more accurate conversion, which preserves Darcs information on renames and some information on tags, use ["Tailor"].


See GitConversion (incremental).


The development version of Mercurial includes a version of the convert extension that can import Subversion trees. It uses the Subversion API, so it can speak any Subversion repository access protocol. This support is under active development.

Converters that work on local repositories or data (faster, if this is an option for you):

Converters that work on remote repositories:

Syncing tools:

  • [http://cheeseshop.python.org/pypi/hgsvn hgsvn] allows you to work on SVN checkouts using Mercurial (mirroring all SVN history in a local Mercurial repository on which you can also do local development). It is useful for managing private branches, submitting patches to project maintainers, have fast local operations instead of slow remote "svn up/log/blame", etc. Also useful as "one-shot" conversion tool if you just remove all the svn directories ("find . -name '.svn' |xargs rm -r") afterwards.

  • SubversionToMercurialSync (like hgsvn, but more primitive)


[http://hg.omnifarious.org/~hopper/p4_to_hg p4_to_hg]

This utility can actually keep two repositories in sync.

Currently, it's slapped together and built to serve my particular needs, but it could probably be modified into something more general. It currently makes no attempt to do anything with Perforce's ability to track branches or the movement of changesets from branch to branch. -- EricHopper 2005-09-27 06:31:03


Because of the threatening behavior of Bitmover, no Bitkeeper conversion tools have been made publically available. See GenericConversion for details on building your own repository conversion tool.

Other systems

["Tailor"] is a conversion tool that can do simple conversions from a variety of systems. See GenericConversion for details on building your own repository conversion tool.

RepositoryConversion (last edited 2020-07-05 13:34:51 by MarcinKasperski)