--- title: "Xray's Migration to Atlassian Forge - FAQs" canonical: "https://docs.getxray.app/space/XRAYCLOUD/1690009610/Xray's%20Migration%20to%20Atlassian%20Forge%20-%20FAQs" format: markdown --- # Introduction Xray is migrating to [Atlassian Forge](https://developer.atlassian.com/cloud/confluence/forge/), Atlassian's modern platform for Jira and Confluence apps, ahead of [Atlassian's end-of-support date for Connect apps](https://www.atlassian.com/blog/development/connect-end-of-support-what-it-means-for-custom-apps-and-how-to-migrate-to-forge). This migration ensures Xray remains fully supported and compatible with the latest Atlassian platform capabilities. You will not lose access to Xray during this transition. The migration is designed to be seamless, with no impact on your data, configurations, or day-to-day usage. When the Forge version becomes available, Jira administrators will need to update their Xray app to complete the migration. This migration represents our commitment to keeping Xray modern, secure, and aligned with Atlassian's vision for the future. > ℹ️ This FAQs page covers information about the migration, what to expect, and any actions you may need to take. If you have additional questions, please [contact the Xray Support team](https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2Fcreate%2F28). # FAQs **1 - What's the difference between Forge Remote and Forge Native?** Xray will be a [Forge Remote app](https://developer.atlassian.com/platform/forge/remote/). This means it runs on our own servers but integrates seamlessly with Jira and Confluence through the Forge platform. This approach gives Xray flexibility while maintaining full compatibility with Atlassian's ecosystem. We are not currently building a Forge Native app, which would run entirely within Atlassian's infrastructure. **2 - Does Forge Remote mean Xray is less Jira-native?** No. Forge Native vs. Forge Remote is a backend hosting decision, not a Jira integration decision. Both use the exact same Forge UI modules, extension points, and design system. From inside Jira, a Forge Native app and a Forge Remote app look and behave the same. Your Work Item panels, custom fields, and workflow integrations work identically either way. **3 - Will Xray stop working during the migration?** No. Xray will continue to work normally throughout the entire migration. We're building the Forge version alongside our [current Xray app](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/392921546), and there will be no service interruptions. Your Testing, reporting, and integrations will remain unaffected. **4 - Does this migration affect Xray Server/Data Center?** No. This migration only applies to Xray Cloud. Xray Server/Data Center is a separate product and is not being migrated to Atlassian Forge. If you are using Xray Server or Xray Data Center, no action is required as part of this migration, and your installation, configuration, and workflows will remain unchanged. However, [Atlassian has announced the end of support for Jira Data Center](https://www.atlassian.com/licensing/data-center-end-of-life). If you are planning a move from Data Center to Cloud, we recommend reviewing our Xray Cloud migration documentation. Please note that once the Forge version of Xray Cloud is released, customers migrating from Data Center will migrate directly to the Forge version. New Cloud migrations will not be able to migrate to a non-Forge version of Xray Cloud. **5 - Will anything change for me?** Xray will continue to provide the same functionality and workflows you use today. While you may notice some minor user UI changes due to differences between Atlassian Connect and Forge, the core Xray experience and feature set will remain the same. The primary changes are behind the scenes, in how Xray is built and integrated with the Atlassian platform. **6 - When is this migration happening?** The migration is happening in two phases: Phase 1: released in July 2026. Phase 2: targeted for Fall 2026. **7 - Do I need to do anything?** No action is required from you right now. Once the Forge version is released, you'll need to upgrade your Xray app to the new version. Jira Admins will need to update the Xray version like they would for any new major version. We’ll communicate this out via [release notes](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565795) and marketing communications. **8 - What If I don't upgrade?** We strongly encourage all customers to upgrade to the latest version of Xray. Atlassian will end support for Connect apps in December 2026, so continuing to use the current version of Xray beyond that date is not recommended. Upgrading to the Forge version ensures you have access to ongoing support, security updates, and new features. **9 - Will there be any downtime during the transition?** No planned downtime. We're designing the migration to be seamless. **10 - Will the migration affect my data, configurations, integrations, APIs, or permissions?** No. Your existing Xray data, configurations, custom fields, workflows, [permissions](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/1203503118), and access controls will remain intact after the migration. Your Test cases, Test results, reports, and other Space data will migrate automatically. Existing [integrations](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566611) and API-based connections are expected to continue working as they do today. We are committed to maintaining compatibility with Xray's integration ecosystem and do not anticipate customers needing to make changes to their integrations. If any updates become necessary, they will be documented and communicated well in advance of the Forge release. **11 - Will the Forge version have all the same features?** Yes. The Forge version will have feature parity with the current Xray app version, plus improvements over time. We're not removing or hiding any functionality. We're modernizing how Xray is built. **12 - What if I have problems during or after the migration?** Our [Support team](https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2Fcreate%2F28) will be monitoring closely and ready to help. We'll provide detailed documentation, FAQs, and dedicated support channels during the transition. **13 - Will the migration affect my Xray license or subscription costs?** No. Upgrading to the Forge version of Xray does not require any additional licensing, subscription, or migration fees. Your existing Xray license and subscription will remain unchanged, and the same plan will continue to apply after the upgrade. **14 - Will I need to reinstall Xray?** No. When the Forge version becomes available, Jira admins will need to trigger the upgrade from the Atlassian admin panel, just as you would update any major app version. Step-by-step instructions will be provided ahead of the upgrade. **15 - Will there be any impact on Compliance or ****[Data Residency](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565771)****?** No. Xray will continue to adhere to its existing compliance and security commitments. Any Forge-specific considerations related to data processing or residency will be communicated in advance. **16 - Can I postpone the upgrade?** The current Connect version of Xray will remain available during the transition period. However, because Atlassian is ending support for Connect apps, customers should plan to upgrade to the Forge version within the recommended timeframe. **17 - How will I know when it is time to upgrade?** We will communicate upcoming milestones through product announcements, release notes, documentation, and customer communications. Detailed upgrade instructions will be provided before any action is required. **18 - Does the migration affect Xray Standard, Advanced, or Enterprise Plans differently?** No. The migration to Forge does not change the features, capabilities, or licensing associated with your [Xray subscription tier](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/393183414). And it works the same for all the tiers. Whether you use Xray Standard, Advanced, or Enterprise, your plan will remain the same after upgrading to the Forge version. You will continue to have access to the features included in your current tier, and your subscription and billing will not be affected by the migration. Any future feature releases or tier-specific capabilities will continue to be communicated through the usual Xray release channels. **19 -** **Why do ****[Permissions](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/1203503118)**** need to be updated when upgrading Xray to the Forge version?** The scope of Xray's Permissions has not changed. The Permissions are the same as those available in the previous Connect version of Xray. As part of the migration to Atlassian Forge, Xray now uses the Forge versions of these Permissions instead of the Connect versions. Because the app's Permission definitions have changed technically, a Jira Administrator must upgrade Xray to approve the updated permissions. This change does not grant Xray any additional Permissions or change what Xray can access. It only updates the underlying permission definitions to their Forge equivalents. > Macro (rw-ui-expands-macro) > > > Macro (rw-expand) > > If you have questions or technical issues, please [contact the Support team via the Customer Portal (Jira service management)](https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2Fcreate%2F28) or [send us a message using the in-app chat](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44577312).