A New and Better Way to Migrate from Subversion
Migrating from one SCM system to another is never a trivial decision, so I’m always impressed by the steady stream of sites making the switch from Subversion to Perforce. The reasons vary, although the need for better performance and branching/merging usually top the list.
In any case, we always try to make the migration process as easy as possible. That means having a lot of migration expertise on our Support and Consulting teams. They can provide deep technical advice and, when a Perforce consultant is engaged, project planning and guidance.
We also develop some migration tools to make the mechanical aspects of migration – actually moving data from the legacy system to Perforce – as seamless as possible. We recently finished a major update for our Subversion migration tool. It is based on years of field experience helping customers move data into Perforce, and offers a lot of improvements over the older tool.
- Support for incremental migrations in some scenarios. This mode is useful when a migration must proceed in stages.
- Support for faster all-at-once migrations when a clean break is desired. This mode can be up to 100 times faster than the older tool.
- Written in Java for speed and portability.
- Support for Unicode content.
- Can import Subversion directory properties as versioned files.
- Preserves RCS keywords (subject to differences in how these are interpreted in Perforce).
- Keeps an import log for data verification.
- Consumes less disk space during migration.
Are you planning a migration from Subversion soon? We have a lot of resources available to help.
- The new migration tool
- Subversion migration webinar
- Consulting and Support
- Knowledge Base article describing differences between Subversion and Perforce.
Still thinking about whether to switch? Have a look at our latest Subversion comparison paper.