Guide · Jira Cloud
Move workflows from sandbox to production
Jira Cloud still has no native company-managed workflow export/import between sites. Here is a safe path: portable JSON, validate first, then import — with backups if something goes wrong.
30-day trial · Free for teams ≤10 · then about USD 2/user/mo
Related: rollback after bad import Related: Standard plan (no Premium deploy) Related: vs Workflow Wizard Easy Workflows app page01 — The gap
Why sandbox → prod is hard on Cloud
On Data Center you could move workflow XML. On Cloud, company-managed workflows live in the site. Copying a project does not cleanly copy the workflow definition you tuned in sandbox. Admins usually rebuild by hand or lean on full config-manager tools when they only needed the workflow slice.
02 — Safe sequence
A validate-before-write approach
- Export the source workflow (or scheme) as portable JSON from the sandbox site.
- Scan for what will not survive (statuses, custom fields, third-party validators/conditions/post-functions).
- Validate on the target site in read-only mode — see create/update/reuse plan and blocking errors before anything writes.
- Import only when the verdict is Ready. Keep a snapshot so you can restore in one click.
- Compare sandbox vs production when you need a visual diff before promoting again.
03 — Tooling
Easy Workflows for Jira
Easy Workflows for Jira is a Forge app built for that workflow-only path. It runs on Atlassian infrastructure: workflow definitions, snapshots, and history stay in your site. It is not a full Configuration Manager replacement for screens, fields, and schemes.
Marketplace listing: Easy Workflows for Jira. Support: info@berkly.nl.