Overview

To adopt JadeGit for an existing system, a migration process is required. This involves establishing new code repositories and transitioning everyone involved in the development lifecycle to new ways of working.

For some teams, this transition may be relatively straightforward. For others, it may become a longer journey depending on several factors, including but not limited to:

• The size of the team and the number of people needing to adopt new practices.

• Moving from a patch-based workflow to a branching strategy.

• The volume of active changes in the current development pipeline.

• Entrenched processes tightly coupled to existing tools that will need to be adapted or phased out.

• The ability to use automation pipelines to support migration, deployment, and related processes.

• The organisation’s risk appetite for completing the transition quickly.

To accommodate these differences, JadeGit supports multiple migration strategies. Teams can select an approach suited to their technical constraints, team size, and risk tolerance.