How to migrate automation rules

When migrating to cloud using the Jira Cloud Migration Assistant, you can migrate your automation rules along with other project components. This page explains what automation rules you can migrate and how they work after migration.

Before you begin

Ensure the Automation for Jira plugin (version 7.2.6 or later) or Automation for Jira Lite plugin (version 7.3.3 or later) is enabled in your Data Center instance.
Review your automation rules, especially those with cross-project dependencies
Understand that some components may need reconfiguration after migration
The following features are not included in migration:
- Rule actors
- Automation audit logs
- Performance insights
- Global configuration settings

Understanding automation rules

Before migration, it's important to understand two types of automation rules:

Project rules: Specific to individual projects
Global rules: Apply across multiple projects

Migration options

When migrating automation rules, you have three options:

Migrates rules specific to your selected projects
Does not include global rules
Includes option to include or exclude disabled rules

Option 2: All automation rules

Migrates both project-specific and global rules
Only option that includes global automation rules

Option 3 : None

No automation rules will be migrated

Note: When re-migrating automation rules, your Data Center rules will always replace the existing Cloud rules. Any customizations or changes made to these rules in Cloud will be overwritten by your Data Center version.

Key migration behaviors

Rules referencing multiple projects will work partially until all referenced projects are migrated
Users and groups mentioned in rules are automatically included in migration
All migrated automation rules are disabled on the cloud by default post migration

Automation components supported in migration

When migrating automation rules, components have different levels of support in cloud. Here's what each status means:

Supported components: Migrate completely and work the same way in cloud
Partially supported components: Migrate but may have some limitations or behave differently in cloud
Unsupported components: Don't migrate and need to be recreated in cloud

Review your automation rules before migration to identify any using partially supported or unsupported components.

Fully supported components

These components migrate with complete functionality and work as expected in cloud:

Component type	Supported items
Triggers	Service limit breached SLA threshold breached Sprint created Sprint started Sprint completed Version created Version released Version unreleased Version updated Work logged
Actions	Assign work item Clone work item Create work item Create subtasks Create variable Delete comment Delete attachments Edit issue Log action Log work Lookup work items Manage watchers
Branches/Conditions	Advanced compare condition Issue attachments JQL condition User condition If-else block Work item fields condition

Partially supported components

Partially supported components migrate to the cloud but might exhibit differences in functionality due to feature parity between Jira on-premise and cloud environments. This means that certain features or settings available on-premise may not exist or behave differently in the cloud, resulting in a slightly altered user experience.

It's important to verify each component post-migration to ensure it functions as expected. If you notice any discrepancies, you can manually adjust settings to align with your original setup.

What You Can Do:

Review and test: After migration, review all partially supported components and test their functionality in the cloud environment.
Manual adjustments: For any differences observed, manually reconfigure the components to match your needs.

Component	Partially supported components
Triggers	Field value changes Incoming webhook Manual Trigger Multiple work item events Scheduled Work item assigned Work item commented Work item created Work item deleted Work item link deleted Work item linked Work item moved Work item transitioned Work item updated
Actions	Add Service Management customer Comment on issue Create Service Management request Create version Delete issue Delete work item links Link work items Re-fetch issue data Release version Send email Set entity property Transition work item Unrelease version
Branches/Conditions	Branch rule/related work item Related work item condition

Unsupported components

These components won't migrate and need to be recreated in cloud if needed:

Component	Unsupported components
Triggers	Issue Archived Issue Property Updated Issue Restored
Actions	Archive Issue Outgoing webhook Publish Event Send Twilio notification Send Microsoft Teams Message Send Slack Message Send Web Request
Branches/Conditions	--

More information and support

We have a number of channels available to help you with your migration.

For more migration planning information and FAQs, visit the Atlassian Cloud Migration Center.
Have a technical issue or need more support with strategy and best practices? Get in touch.
Looking for peer advice? Ask the Atlassian Community.
Want expert guidance? Work with an Atlassian Partner.

Was this helpful?

It wasn't accurateIt wasn't clearIt wasn't relevant

Still need help?

The Atlassian Community is here for you.

Ask the Community