Developers are requesting to migrate from Harvest to GITHUB.
Release : 12.6
Component : CA HARVEST SCM DATA STORES (DATABASE & MIGRATION)
For porting your data to GIT, Harvest doesn’t have a utility that does it. The easiest will be to checkout the latest versions of all the files in a project and start a new GIT repository from those, but you will lose all your version history and other artifacts associated with your project such as any data entered on forms. However, the newest version of Harvest has a new feature that allows developers to use GIT as a "front-end" to Harvest instead of Workbench, therefore providing the best of both worlds. From the Release Notes:
GIT Front-End for Harvest SCM
Git and Harvest can now be used simultaneously within a software development life cycle:
GIT Front-End for Harvest enables developers to focus mainly on their primary role, that is,‘development’. It decouples the life cycle management and work flow from your development activities. Developers may want to use GIT in their development activity. At times, an organization may mandate the choice of source control tool for compliance requirements, say for example: Harvest. To bridge this need, Harvest provides the Front-End with GIT interface. This unique combination (Harvest along with GIT) enables development activities and project life-cycle management capabilities, deployment, code reviews, etc. by all stake holders in a project.