Azoft is on Universal VCS Data Migration Solution Development

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 solution that simplifies        

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:

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