Migration from data center to cloud

This page describes how to migrate configurations from the data center version to the cloud version.

At the moment, there is no automated migration available. Migration must be performed manually by recreating the configuration in the cloud environment.

Migration approach

Since no automated migration exists yet, the migration must be executed step by step.

The general approach is to review the existing configuration in the data center setup and rebuild it in the cloud environment using the available features.

Key differences

When migrating to cloud, consider the following differences:

• The cloud version does not support pre-receive push checks, so commit-level blocking is not possible

• Validation is focused on pull request and merge workflows

• Some features may behave differently due to API limitations in the cloud environment

Manual migration steps

1. Review existing configuration
   Analyze your current rules, checks, and workflows in the data center setup.

2. Configure the Process Guardian
   Recreate the global configuration in the cloud environment.

3. Set up Jira connections
   Configure the required Jira connections using a technical user and API token.

4. Recreate rules
   Rebuild your rules in the cloud version.

   • Use templates as a starting point where possible

   • Recreate checks such as issue key validation, JQL checks, or naming conventions

   • Reapply conditions to match your workflow logic

5. Validate configuration
   Test the setup using pull requests to ensure that rules behave as expected.

Recommendations

• Start with a small subset of rules and validate behavior

• Use templates to speed up migration

• Focus on pull request validation, as this is the primary enforcement point in cloud

Key takeaway

Migration from data center to cloud is currently a manual process, but it can be structured and accelerated using templates and a step-by-step approach. An automated migration solution is planned for the future.