AzoftSpotlightAzoft is on Universal VCS Data Migration Solution Development

Azoft is on Universal VCS Data Migration Solution Development

By Emma Brem on September 25, 2009

Using several different Version Control Systems (VCS) is typical for companies of any size and scale.

The reason is that sooner or later any company feels a necessity of a newer VCS. This necessity may be based on different factors varying from low performance and absence of GUI to the price factor and VCS concept (traditional or distributed).

But transition to a newer VCS doesn’t cancel the usage an old one: in case of projects’ transfer to a new system, one won’t be able to work with changes history. This usually results in a situation where all the old projects continue to be supported by an old VCS, while the new system is being used only for new projects.

The disadvantages are obvious:

  • A company has to support several servers for VCS
  • Users have to install several systems on a workstation and learn how to operate them, which leads to time & resources losses.

At the present time there are several data migration solutions available on the market, but they usually work only with specified VCS pairs (i.e. a “source” VCS and a “destination” VCS).

A solution that simplifies
Considering the above mentioned, the team of Azoft is currently working on a universal data migration solution that would replace numerous systems and allows using a single migration tool instead of them.

The solution is supposed to be a standalone J2SE application, and the list of entities to be migrated includes:

  • All the VCS projects
  • Branches of the projects
  • Changes history, including files’ and history attributes (e.g. time & authorship of a commit and comments)
  • Users list, including users’ rights to projects, branches, folders, and files

In case of migration to a VCS that already has a list of users and projects, there will be an opportunity to choose project to be migrated and to set migration rules for particular users. This will eliminate possible conflicts between existing and migrated entities on a “destination” VCS.

Core migration principles are the following:

  • Data migration will be performed “at once” – so a “source” VCS will be no longer used after the migration.
  • Data migration will undergo 2 stages. At first, data is being migrated to an intermediary storage format, and then it is transferred to a “destination” VCS.

We are sure the solution will be able to simplify our customers’ work process and save their time & money.


Comments are closed.