How to migrate automation flows

When migrating to cloud using the Jira Cloud Migration Assistant, you can migrate your automation flows along with other project components. This page explains what automation flows 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 flows, especially those with cross-project dependencies
Understand that some steps may need reconfiguration after migration
The following features are not included in migration:
- Flow actors
- Automation audit logs
- Performance insights
- Global configuration settings

Understanding automation flows

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

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

Migration options

When migrating automation flows, you have three options:

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

Option 2: All automation flows

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

Option 3 : None

No automation flows will be migrated

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

Key migration behaviors

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

Automation steps supported in migration

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

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

Review your automation flows before migration to identify any using partially supported or unsupported steps.

Fully supported steps

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

Step 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 work item Log action Log work Lookup work items Manage watchers
Branches/Conditions	Advanced compare condition Work item attachments JQL condition User condition If-else block Work item fields condition

Partially supported steps

Partially supported steps 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 step 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 steps and test their functionality in the cloud environment.
Manual adjustments: For any differences observed, manually reconfigure the steps to match your needs.

Step	Partially supported steps
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 work item Create Service Management request Create version Delete work item Delete work item links Link work items Re-fetch work item data Release version Send email Set entity property Transition work item Unrelease version
Branches/Conditions	Branch flow/related work item Related work item condition

Unsupported steps

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

Step	Unsupported steps
Triggers	Work item Archived Work item Property Updated Work item Restored
Actions	Archive work item 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