Guide · Jira Cloud
Copy workflows from one Cloud site to another
Jira Cloud has no native “clone this company-managed workflow onto that site.” Copying a project does not cleanly copy the workflow you tuned. Here is a workflow-only path: export JSON, validate, then import. Free for teams ≤10.
Free for teams ≤10 · 30-day trial · then about USD 2/user/mo
Related: sandbox → production Related: back up workflows Easy Workflows app page01 — What Cloud will not do
No file import between sites
You can export a workflow in places. You cannot import that file on another Cloud site without a Marketplace app or API work. XML died with the old editor. Atlassian Copy product data moves issues and projects, not a single company-managed workflow.
02 — Workflow-only copy
Export, validate, import
- Export the company-managed workflow or scheme as portable JSON on the source site.
- Scan statuses, custom fields, and third-party conditions/validators/post-functions that will not exist on the target.
- Validate on the target in read-only mode. Stop on blockers.
- Import only when Ready. Snapshot first so a bad copy is a one-click restore.
03 — Honest no
Not a full site clone
Easy Workflows does not copy issues, screens, fields, team-managed workflows, or Data Center XML. For those, use Copy product data or a configuration manager. For sandbox → prod on Standard (no Premium deploy): this guide.
Easy Workflows for Jira is Forge-hosted. Try free: Easy Workflows for Jira. Support: info@berkly.nl.