Migrate from Data Center to Cloud
Feature Bundle doesn’t support automated migration with the Jira Cloud Migration Assistant (JCMA). The app is built on configuration, not on its own data or objects, so JCMA has nothing to transfer. To migrate, you recreate your Data Center configuration in Jira Cloud.
This is also a good moment to review your configuration, because Cloud offers more than Data Center in several areas.
Before you start
- You use Feature Bundle on Jira Data Center.
- You have a Jira Cloud site with Jira Service Management, and a sandbox or test site if possible.
- You are a Jira administrator on both sites.
What is not migrated
JCMA transfers none of your Feature Bundle configuration. You rebuild everything in Cloud. In Cloud, you find the configuration in two places: Space settings > Apps > Feature Bundle for each space, and the Apps page of the Jira settings for global settings and banners. See Global configuration.
| Feature | Data Center | Cloud | What this means for migration |
|---|---|---|---|
| Additional Fields (called Request View Enhancer in Data Center) | Limited field support | Many more supported fields | Check which fields you use now and whether new ones are worth adding. |
| Customer Actions (called Edit Request in Data Center) | One edit form per request type | Several forms per request type, each with its own conditions | One Data Center setup can become several more targeted forms in Cloud. |
| Ticket Journey (called Request Steps in Data Center) | Configurable | Configurable | Rebuild the configuration in Cloud. |
| Announcement Banners | Limited scope | Shown on chosen pages of the customer side, with a schedule and conditions for who sees them | Redesign the banners instead of copying them. |
| Request Access | Fully configurable. See Access Configuration | Not available | No migration path. See below. |
| Time Tracking for Non-Agents | Fully configurable | Not available | No Cloud equivalent. |
| Bulk Add Holidays to SLA Calendars | Fully configurable | Not available | No Cloud equivalent. |
| Export and Import Request Types | Fully configurable | Not available | No Cloud equivalent. |
| Rename SLAs | Fully configurable | Not available | No Cloud equivalent. |
Request Access
Jira Service Management Cloud supports basic access restrictions. See Atlassian’s docs on adding or removing restrictions on request types.
The advanced version from Data Center is blocked by a platform limitation, and no app on the Atlassian Marketplace offers it. We have an open backlog item with Atlassian about it.
Features with no Cloud equivalent
Time Tracking for Non-Agents, Bulk Add Holidays to SLA Calendars, Export and Import Request Types, and Rename SLAs have no Cloud equivalent and no migration path. If your team relies on one of them, include that in your plan. If it is essential, contact our support team and we advise on workarounds.
Steps
- Document your Data Center configuration. For each Feature Bundle feature you use, write down the business rules and conditions behind it. Screenshots or notes are enough, because there is no export.
- Compare it with Cloud. For each feature, decide whether to copy the current behavior or redesign it with the Cloud options in the table. If you use Request Access, plan without it and check whether the access restrictions of Jira Service Management Cloud cover your basic needs.
- Design the target Cloud configuration around what you need now, not as a one-to-one copy.
- Build and validate it in a sandbox. Install Feature Bundle on a Cloud test site (see Install Feature Bundle), configure it there, and check each feature against the rules from step 1.
- Migrate your Jira spaces to Cloud with JCMA or your usual process. This moves your Jira data, not the Feature Bundle configuration.
- Recreate the validated configuration in production when the migration of the spaces is complete.
- Test every configured feature end to end, as an agent and as a customer.
- Review the newer Cloud options: several forms per request type, more fields in Additional Fields, and banner schedules and conditions. Refine your configuration where it helps.
- Tell your agents and customers what changed, especially that Request Access isn’t available in Cloud.
Result
Feature Bundle runs in Jira Cloud with a configuration that you checked end to end, and your agents and customers know what changed.
Need help?
If you have a problem during the migration, write to us through the support portal.