Migrate to Cloud
- 1 Recommended Processing Flow
- 2 Before You Export
- 3 Common Entry: Open The Migration Export Page
- 4 Choose Export Type
- 5 Path A: Approval Rule Configuration Export
- 6 Path B: Approval History Export
- 7 What Migration Packages Carry
- 8 Cloud-Side Follow-Up
- 9 FAQ
- 9.1 Can configuration packages and history packages be exported together?
- 9.2 Why were some rules not exported?
- 9.3 Do all skipped rules need to be fixed first?
- 9.4 Why can approval history select only one project?
- 9.5 Can I still export when preview shows Above recommended default?
- 9.6 What should I do when preview shows Export blocked?
- 9.7 Why was the Slack token not exported?
- 9.8 Can I import the ZIP directly after downloading it?
- 10 Recommended Checklist
This guide is for Jira Data Center administrators. It explains how to export migration ZIP packages from WorkflowWise - Parallel Approval and Workflow Extension (Jira Data Center), then upload them to WorkflowWise - Parallel Approval and Workflow Extension (Jira Cloud) / Workflow Parallel Approval (Jira Cloud) for precheck and import.
There are two export types: approval rule configuration export and approval history export. In an actual migration, you can export both ZIP packages first. On the Cloud side, the two package types do not have a strict import order; upload, precheck, and import them according to your migration plan.
Recommended Processing Flow
Order | Package type | Page option | When to use |
|---|---|---|---|
1 | Approval rule configuration package | Configuration package | Migrates approval rule configuration. It is usually prepared first so rule precheck can be completed early. |
2 | Approval history package | Approval history package | Migrates completed approval history. It can be prechecked and imported separately according to your migration plan. |
If you only need to migrate rule configuration, complete the first export type. If you also need to migrate historical approval records, continue with the second export type.
Before You Export
Check | Description |
|---|---|
Current user is a Jira administrator | Only Jira administrators can export migration packages. |
The Data Center app version meets the requirement | Upgrade the DC app to version 2.10.3 or later for Jira Data Center 8.0.0 - 9.17.5, or version 2.11.4 or later for Jira Data Center 10.x. Older versions may not show the Migrate to Cloud entry. |
Migration scope is decided | Configuration packages can be exported by project or globally; history packages export one project at a time. |
PENDING approvals are understood to be excluded | In-progress approvals and unfinished votes are not included in migration packages. |
Cloud-side mappings are expected | Users, projects, statuses, fields, and related objects need to be checked in Cloud precheck. |
Credentials are ready to be reconfigured | Slack tokens, mail servers, WeCom settings, and other sensitive or DC-only settings are not exported. |
Common Entry: Open The Migration Export Page
In Jira administration, open Manage apps, then click Migrate to Cloud in the left-side WorkflowWise menu.
You do not need to select approval rules one by one from the rule list. The system reads data automatically based on the package type and scope you choose later, then tells you during preview which items can be exported and which items will be skipped.
Notes:
Exporting a migration package does not modify, delete, or disable approval rules in Data Center.
If Migrate to Cloud is not visible, check the current user's permissions, whether the app is enabled, whether the license is valid, and whether the DC app has been upgraded to version 2.10.3 or later for Jira Data Center 8.0.0 - 9.17.5, or version 2.11.4 or later for Jira Data Center 10.x.
Choose Export Type
The page provides two options:
Option | Meaning | Purpose |
|---|---|---|
Configuration package | Approval rule configuration package | Exports Cloud-supported approval rule configuration plus optional Email/Slack templates. |
Approval history package | Approval history package | Exports completed approval nodes and vote records for one project and a selected time range. |
The two export paths are described below.
Path A: Approval Rule Configuration Export
The approval rule configuration package is used to bring migratable approval rule configuration from Data Center to Cloud.
A1. Select Configuration Package
Select Configuration package, then click Next.
The key message on this page is that only rules Cloud can fully express are exported. The system does not remove unsupported fields and continue exporting a rule, because doing so could change the rule's actual approval behavior.
Rules commonly skipped include:
Rules using Groovy script conditions
Rules using JQL conditions
Rules using project roles as approvers
Rules using project leads as approvers
Rules requiring full approval
Workflow-scoped rules that cannot be losslessly expanded to specific projects, issue types, and statuses
A2. Select Configuration Export Scope
On the Scope and range page, choose the configuration export scope.
Scope | When to choose | Result |
|---|---|---|
Project | Migrate configuration for selected projects only | Exports migratable approval rules under the selected projects. |
Global | Migrate the full configuration set | Exports migratable approval rules across the whole instance. |
If you choose Project, select the projects to export in Projects.
Shared settings recommendations:
Keep the default Do not include shared Email/Slack templates to avoid letting a project configuration package affect Cloud global notification templates.
Select Include shared Email/Slack templates only when you explicitly need to migrate shared Email/Slack templates.
Even when Slack templates are included, the Slack token is not exported. Reconfigure the token in Cloud.
After confirming the settings, click Continue to preview.
A3. Run Configuration Package Preview
After opening Preview package, click Run preview.
Preview is required before export. The system calculates record counts, package size, Cloud import limits, and rules that will be skipped. Without a valid preview, the ZIP cannot be exported.
A4. Review Configuration Package Preview
After preview completes, focus on these items:
Area | How to check |
|---|---|
Top status | Within limits means you can continue; Export blocked means issues must be resolved first. |
Summary | Confirm the file name, package type, and Ready to export status. |
Records | Confirm that project, user, status, and rule counts match expectations. |
Skipped rules | Review which rules will be skipped and why. |
If Skipped rules are listed, click Export CSV to download the list for offline review or support. The CSV is only for human analysis. It is not a migration package and cannot be uploaded to Cloud for import.
Common skip reasons:
Reason | Description | Recommendation |
|---|---|---|
Scope or transition cannot be resolved | The project, issue type, status, or transition cannot be resolved. | Check whether the objects referenced by the rule still exist. |
Full approval is not supported | Cloud cannot safely preserve the semantics of requiring every approver to approve. | Modify the rule, or accept that the rule will not be migrated. |
Workflow scope cannot be expanded losslessly | The workflow scope cannot be losslessly converted into Cloud project, issue type, and status scope. | Prefer converting it to a concrete project scope, then run preview again. |
Project-role approver has no Cloud equivalent | Project role approvers do not have an equivalent import behavior in Cloud. | Change the approver source to fixed users, groups, or another Cloud-supported approver source. |
After confirming the package can be exported, click Continue to export.
A5. Download The Configuration Migration Package
On the Export ZIP page, confirm the file name, then click Export ZIP.
The browser downloads a .zip file, for example:
workflowwise-configuration-global-20260608-095636.zip
Upload this ZIP to Cloud precheck.
If export reports that the preview expired, the request changed, or preview must be run first, return to the Preview page, click Run preview again, and then continue with export.
A6. Confirm Configuration Package Download
When ZIP downloaded appears, the ZIP has been generated and downloaded from Data Center.
Next steps in Cloud:
Upload the configuration migration package for precheck.
Resolve mappings for users, projects, issue types, statuses, groups, custom fields, and related objects.
Resolve conflicts or missing items reported by precheck.
Import the configuration package according to your migration plan after precheck passes.
A successful download does not mean the package has already been imported into Cloud. It only means the Data Center migration package is ready.
Path B: Approval History Export
Approval history packages migrate completed approval history. You can export a history package in advance, then precheck and import it separately in Cloud.
Approval history packages have two important limits:
One package exports one project only.
Only completed approval nodes and votes within the selected time range are exported.
B1. Select Approval History Package
On the package type page, select Approval history package, then click Next.
This package does not export rule configuration and does not continue in-progress approvals from Data Center. It only brings completed approval history to Cloud.
B2. Select Project And History Range
On the Scope and range page, choose:
Field | Description |
|---|---|
Project | Select the project whose approval history should be exported. A history package can select only one project. |
History range | Select the history time range. Available options include All time, Last 3 months, Last 6 months, and Custom range. |
Time range recommendations:
If the project has little history data, you can choose All time.
If the project has a lot of history data, choose Last 3 months, Last 6 months, or Custom range and export in batches.
If preview reports that the history package is too large, shorten the time range and run preview again.
After confirming the settings, click Continue to preview.
B3. Review Approval History Preview
Approval history preview is similar to configuration package preview, but the focus is different.
Focus on these items:
Area | How to check |
|---|---|
Top status | Above recommended default means the package exceeds the recommended value but can still be exported; Export blocked means the scope must be reduced. |
Summary | Confirm that the package type is Approval history package and the status is Ready to export. |
Skipped pending nodes | Number of PENDING approvals excluded from the package. The screenshot shows 3. |
Records | Focus on Issues, Nodes, and Votes. |
Package size estimate | Review means reducing scope is recommended; Blocked means the scope must be reduced. |
Warnings | Review split or scope reduction suggestions from the system. |
In the screenshot, the result is Above recommended default and the status is still Ready to export. This means you can continue, but reducing the time range is recommended to reduce Cloud import pressure.
If Skipped pending nodes is not 0, those in-progress approvals are not included in the history package. If their final results also need to be migrated, complete or cancel them in Data Center first, then run preview and export again.
Approval history package preview status:
Status | Meaning | Recommendation |
|---|---|---|
Within limits | The package is within limits. | Continue with export. |
Above recommended default | The package exceeds the recommended default but stays below the hard limit. | You can continue, but splitting by time range is recommended. |
Export blocked | The package exceeds a hard limit or has a blocking issue. | Reduce the time range and run preview again. |
After confirming the package can be exported, click Continue to export.
B4. Download The Approval History Package
The approval history package download process is the same as the configuration package: open Export ZIP, then click Export ZIP.
The downloaded file name usually contains history and the project key, for example:
workflowwise-history-WWTB-20260608-103127.zip
If export reports that the preview expired, the request changed, or preview must be run first, return to the Preview page, click Run preview again, and then continue with export.
B5. Confirm Approval History Package Download
When ZIP downloaded appears, the approval history package has been downloaded.
Next steps in Cloud:
Upload the approval history package for precheck.
Resolve identity mappings or missing items reported by Cloud precheck.
Import approval history after precheck passes.
Notes:
Approval history packages do not automatically move Jira workflow statuses in Cloud.
Approval history packages do not send notifications.
Approval history packages do not continue unfinished approvals from Data Center.
If one project has a lot of history data, split it into multiple history packages by time range and process them one by one.
What Migration Packages Carry
Users generally do not need to know the internal ZIP file structure. They only need to understand which business data is carried by the migration package and which items need to be handled again in Cloud.
Configuration Packages Carry
Approval rule configuration supported by Cloud.
Mapping information referenced by those rules, such as projects, issue types, statuses, users, groups, and custom fields.
Migratable Email/Slack template content and switches, if shared settings are included.
Approval History Packages Carry
Completed approval nodes for the selected project and time range.
Vote records under completed approval nodes.
Mapping information referenced by those history records, such as users, issues, and statuses.
Not Carried
In-progress PENDING approvals.
Unfinished votes.
Slack tokens, mail servers, WeCom settings, repeat reminders, variable lists, and other credentials or DC-only settings.
Approval rules that Cloud cannot fully express.
Any action that continues approvals, moves Jira workflow statuses, sends notifications, or runs validators.
Cloud-Side Follow-Up
After downloading ZIP files, follow the Cloud import guide to complete precheck and import:
Cloud import guide: Migration from Data Center
FAQ
Can configuration packages and history packages be exported together?
No. The two package types must be generated, uploaded, and imported separately. There is no strict import order on the Cloud side; handle them according to your migration plan.
Why were some rules not exported?
Those rules cannot be fully expressed in Cloud. To avoid changing approval behavior, the system skips the whole rule and shows the reason in preview.
Do all skipped rules need to be fixed first?
Not necessarily. If those rules must be migrated, modify them in Data Center and run preview again. If you can accept that they will not be included in Cloud, you can continue exporting.
Why can approval history select only one project?
Approval history is usually much larger than configuration data. Exporting by single project and time range reduces package size and Cloud import pressure, and makes troubleshooting easier.
Can I still export when preview shows Above recommended default?
Yes, as long as the status is still Ready to export. However, reducing the history time range or splitting the package is recommended, especially when node and vote counts are large.
What should I do when preview shows Export blocked?
Adjust the scope and run preview again. For configuration packages, check project scope and rules. For history packages, shorten the time range or split into smaller time windows.
Why was the Slack token not exported?
Slack tokens are sensitive credentials. They are not written to the ZIP, preview, CSV, or error logs. Reconfigure them in Cloud.
Can I import the ZIP directly after downloading it?
Uploading it to Cloud precheck first is recommended. Precheck validates mappings, conflicts, and limits before import.
Recommended Checklist
Before exporting a configuration package:
Confirm that you are a Jira administrator.
Confirm whether this export uses Project scope or Global scope.
If Project scope is selected, confirm the selected projects.
Confirm whether shared Email/Slack templates need to be included.
After configuration package preview:
The top status is not Export blocked.
The package type and file name in Summary match expectations.
Record counts do not look obviously abnormal.
Skipped rules have been reviewed, and CSV has been exported if needed.
Before exporting an approval history package:
Confirm the Cloud import plan for configuration and history packages.
Select only one project at a time.
Select an appropriate history time range.
If there is a lot of history data, prefer splitting by time range.
After history package preview:
The status is Ready to export.
If Above recommended default appears, evaluate whether the time range should be shortened.
If Export blocked appears, reduce the scope and run preview again.
Confirm that Issues, Nodes, and Votes counts match expectations.
After download:
Keep the ZIP file.
Upload it to Cloud precheck.
Resolve identity mappings and conflicts.
Reconfigure the Slack token in Cloud.
Import configuration and approval history packages according to your migration plan.