|
| 1 | +--- |
| 2 | +id: one-click-migration-from-xray |
| 3 | +title: One Click Migration from X-Ray |
| 4 | +hide_title: true |
| 5 | +sidebar_label: One Click Migration from X-Ray |
| 6 | +description: Migrate your test cases, attachments, and custom fields from X-Ray (Jira Cloud) to TestMu AI Test Manager in a single click. |
| 7 | +keywords: |
| 8 | + - xray |
| 9 | + - xray migration |
| 10 | + - import data from xray |
| 11 | + - import data |
| 12 | + - jira xray |
| 13 | + - test migration |
| 14 | +url: https://www.testmuai.com/support/docs/one-click-migration-from-xray/ |
| 15 | +site_name: LambdaTest |
| 16 | +slug: one-click-migration-from-xray/ |
| 17 | +canonical: https://www.testmuai.com/support/docs/one-click-migration-from-xray/ |
| 18 | +--- |
| 19 | + |
| 20 | +import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; |
| 21 | + |
| 22 | +<script type="application/ld+json" |
| 23 | + dangerouslySetInnerHTML={{ __html: JSON.stringify({ |
| 24 | + "@context": "https://schema.org", |
| 25 | + "@type": "BreadcrumbList", |
| 26 | + "itemListElement": [{ |
| 27 | + "@type": "ListItem", |
| 28 | + "position": 1, |
| 29 | + "name": "TestMu AI", |
| 30 | + "item": BRAND_URL |
| 31 | + },{ |
| 32 | + "@type": "ListItem", |
| 33 | + "position": 2, |
| 34 | + "name": "Support", |
| 35 | + "item": `${BRAND_URL}/support/docs/` |
| 36 | + },{ |
| 37 | + "@type": "ListItem", |
| 38 | + "position": 3, |
| 39 | + "name": "One Click Migration from X-Ray", |
| 40 | + "item": `${BRAND_URL}/support/docs/one-click-migration-from-xray/` |
| 41 | + }] |
| 42 | + }) |
| 43 | + }} |
| 44 | +></script> |
| 45 | + |
| 46 | +# One Click Migration from X-Ray |
| 47 | + |
| 48 | +<BrandName /> Test Manager supports one-click migration from **X-Ray (Jira Cloud)**, allowing you to import your entire test library — including projects, test cases, folder structures, attachments, custom fields, and linked requirements — directly into Test Manager without manual data entry. |
| 49 | + |
| 50 | +## Key Benefits |
| 51 | + |
| 52 | +- **Zero manual effort** — All test cases, steps, attachments, and folder structures are automatically migrated. |
| 53 | +- **Handles both Manual and BDD tests** — Manual step definitions and Gherkin/BDD scenarios are both fully supported. |
| 54 | +- **Custom fields carried over** — Custom fields in your X-Ray tests are automatically detected and created in Test Manager. |
| 55 | +- **Attachments included** — File attachments are downloaded from Jira and re-uploaded to Test Manager, including step-level references. |
| 56 | +- **Real-time progress tracking** — A progress bar shows migration status so you know exactly where things stand. |
| 57 | + |
| 58 | +:::note |
| 59 | +This migration supports **X-Ray Cloud (Jira Cloud)** only. X-Ray Server and Data Center are not supported at this time. |
| 60 | +::: |
| 61 | + |
| 62 | +## Prerequisites |
| 63 | + |
| 64 | +Before starting the migration, ensure you have the following ready. |
| 65 | + |
| 66 | +#### <BrandName /> Account |
| 67 | +- An active <BrandName /> account with access to **Test Manager**. |
| 68 | + |
| 69 | +#### X-Ray Cloud Credentials |
| 70 | + |
| 71 | +You need your X-Ray Cloud API credentials (Client ID and Client Secret). Refer to the [X-Ray Global Settings - API Keys](https://docs.getxray.app/space/XRAYCLOUD/44568019/Global+Settings+-+API+Keys) documentation for detailed instructions. To obtain these: |
| 72 | + |
| 73 | +1. Log in to your Jira Cloud instance. |
| 74 | +2. Navigate to **Apps > Manage your apps > X-Ray** (or go to X-Ray Settings). |
| 75 | +3. Under **API Keys**, generate a new API key pair if you do not already have one. |
| 76 | +4. Copy the **Client ID** and **Client Secret**. |
| 77 | + |
| 78 | +:::warning |
| 79 | +The Client Secret is shown only once. Store it securely before proceeding. |
| 80 | +::: |
| 81 | + |
| 82 | +#### Jira Cloud Credentials |
| 83 | + |
| 84 | +You also need Jira Cloud credentials to access project metadata and attachments: |
| 85 | + |
| 86 | +| Credential | Where to Find It | |
| 87 | +|---|---| |
| 88 | +| **Jira Host URL** | Your Jira instance URL, e.g., `https://yourcompany.atlassian.net` | |
| 89 | +| **Email Address** | The email associated with your Atlassian account | |
| 90 | +| **Jira API Token** | Generate from [Atlassian API Tokens](https://id.atlassian.com/manage-profile/security/api-tokens) | |
| 91 | + |
| 92 | +#### Jira Integration in <BrandName /> |
| 93 | + |
| 94 | +To migrate linked Jira issues and requirements, you must have the corresponding Jira instance integrated with <BrandName />. Without this integration, linked issues will not be carried over during migration. Refer to the [Link Jira Issues with Test Manager](https://www.testmuai.com/support/docs/link-jira-issues-with-test-manager/) guide to set up the integration before starting the migration. |
| 95 | + |
| 96 | +#### Permissions |
| 97 | +- Your Jira account must have **read access** to the project you are migrating. |
| 98 | +- Your X-Ray API key must have permission to access test cases and test sets in the target project. |
| 99 | + |
| 100 | +--- |
| 101 | + |
| 102 | +## Step-by-Step Migration Guide |
| 103 | + |
| 104 | +### Step 1: Open the Migration Tool |
| 105 | + |
| 106 | +1. Log in to your **<BrandName />** account. |
| 107 | +2. Navigate to **Test Manager Projects** from the left sidebar. |
| 108 | +3. Click the **Import data** option on the Project Listing page. |
| 109 | +4. Select **X-Ray Cloud** as the migration source from the **Import from** dropdown. |
| 110 | + |
| 111 | +<img loading="lazy" src={require('../assets/images/xray-migration/import-data-project-listing.png').default} alt="import-data-project-listing" className="doc_img" width="1366" height="629"/> |
| 112 | + |
| 113 | +### Step 2: Enter Your Credentials |
| 114 | + |
| 115 | +Fill in the following fields: |
| 116 | + |
| 117 | +| Field | Description | |
| 118 | +|---|---| |
| 119 | +| **Jira Host** | Your Jira Cloud instance URL (e.g., `https://yourcompany.atlassian.net`) | |
| 120 | +| **Jira Email Address** | Your Atlassian account email | |
| 121 | +| **Jira API Token** | API token generated from Atlassian | |
| 122 | +| **X-Ray Client ID** | Client ID from X-Ray API Keys. Refer to the [X-Ray Global Settings - API Keys](https://docs.getxray.app/space/XRAYCLOUD/44568019/Global+Settings+-+API+Keys) documentation. | |
| 123 | +| **X-Ray Client Secret** | Client Secret from X-Ray API Keys. Refer to the [X-Ray Global Settings - API Keys](https://docs.getxray.app/space/XRAYCLOUD/44568019/Global+Settings+-+API+Keys) documentation. | |
| 124 | + |
| 125 | +Click **Continue**. The system validates both your Jira and X-Ray credentials in parallel. If either set is invalid, an error message indicates which credentials need to be corrected. |
| 126 | + |
| 127 | +<img loading="lazy" src={require('../assets/images/xray-migration/enter-credentials.png').default} alt="enter-xray-credentials" className="doc_img" width="1366" height="629"/> |
| 128 | + |
| 129 | +### Step 3: Select the Jira Project |
| 130 | + |
| 131 | +1. After successful validation, a list of your Jira projects containing X-Ray test cases is displayed. |
| 132 | +2. Select the **project** you want to migrate from. You can select multiple projects at once. |
| 133 | +3. Click **Start Migration**. |
| 134 | + |
| 135 | +<img loading="lazy" src={require('../assets/images/xray-migration/select-project.png').default} alt="select-jira-project" className="doc_img" width="1366" height="629"/> |
| 136 | + |
| 137 | +### Step 4: Monitor Progress |
| 138 | + |
| 139 | +- A **progress bar** shows real-time migration status. |
| 140 | +- The migration processes test cases in batches. Depending on the size of your test library, the complete process may take some time. |
| 141 | + |
| 142 | +<img loading="lazy" src={require('../assets/images/xray-migration/migration-progress.png').default} alt="migration-progress" className="doc_img" width="1366" height="629"/> |
| 143 | + |
| 144 | +- You can navigate away from the page and continue other work — the migration continues in the background. Once the migration is complete, you will receive an email notification. |
| 145 | + |
| 146 | +<img loading="lazy" src={require('../assets/images/xray-migration/email-completion.png').default} alt="email-completion-notification" className="doc_img" width="1366" height="629"/> |
| 147 | + |
| 148 | + |
| 149 | +### Step 5: Review the Results |
| 150 | + |
| 151 | +Once migration completes: |
| 152 | + |
| 153 | +1. The migrated X-Ray projects will appear on the **Projects** listing page in Test Manager. |
| 154 | +2. Navigate to the **Test Cases** section in any of your migrated projects. |
| 155 | +3. Verify that your test cases, folder structure, and attachments have been imported correctly. |
| 156 | +4. Check a few test cases to confirm that steps, custom fields, and linked requirements are intact. |
| 157 | + |
| 158 | +<img loading="lazy" src={require('../assets/images/xray-migration/migration-results.png').default} alt="migration-results" className="doc_img" width="1366" height="629"/> |
| 159 | + |
| 160 | +--- |
| 161 | + |
| 162 | +## What Gets Migrated |
| 163 | + |
| 164 | +The following entities and data are transferred from X-Ray to Test Manager during migration: |
| 165 | + |
| 166 | +| Entity | Details | |
| 167 | +|---|---| |
| 168 | +| **Test Cases** | All test cases from the selected project are imported with their complete definitions. | |
| 169 | +| **Test Case Metadata** | Summary, description, priority, labels, and preconditions are mapped to their corresponding Test Manager fields. | |
| 170 | +| **Manual Test Steps** | Each step's **Step Description** and **Expected Result** are migrated directly. Step ordering is preserved. | |
| 171 | +| **BDD/Gherkin Scenarios** | Full Gherkin scenario text is extracted and stored under the BDD Scenarios template. | |
| 172 | +| **Attachments** | Both test case-level and test step-level attachments are downloaded and re-uploaded to Test Manager. | |
| 173 | +| **Rich Text Fields** | Rich text content — including embedded screenshots, tables, lists, and other supported formatting — is preserved. | |
| 174 | +| **Custom Fields** | Custom fields are automatically detected in X-Ray and created in Test Manager with matching names. | |
| 175 | +| **Linked Issues / Requirements** | Jira issue links and requirement associations are preserved. Requires [Jira integration](https://www.testmuai.com/support/docs/link-jira-issues-with-test-manager/) to be configured. | |
| 176 | +| **X-Ray Test Key** | The original X-Ray test key is imported within tags, enabling quick reference and filtering in Test Manager. | |
| 177 | + |
| 178 | +:::note |
| 179 | +X-Ray fields that cannot be directly mapped to system fields in Test Manager are automatically imported as custom fields. These may include Reporter, Assignee, Environment, Fix Version, Components, etc. |
| 180 | +::: |
| 181 | + |
| 182 | +:::info Test Data Migration |
| 183 | +Test Data from X-Ray steps is migrated as a single textarea custom field at the test case level, with textual data consolidated together. This is because Test Manager does not currently support a step-level Test Data field. |
| 184 | +::: |
| 185 | + |
| 186 | +## What Does Not Get Migrated |
| 187 | + |
| 188 | +The migration focuses exclusively on your **test library** — definitions, structure, and metadata. The following entities are not included: |
| 189 | + |
| 190 | +| Entity | Reason | |
| 191 | +|---|---| |
| 192 | +| **Test Runs** | Execution-layer entity that is not part of the test case definition. | |
| 193 | +| **Test Execution Logs** | Execution history and pass/fail results are excluded by design. | |
| 194 | +| **Datasets** | Datasets and their corresponding parameters are not imported. | |
| 195 | +| **Standalone Preconditions** | Precondition text is captured within individual test cases, but standalone precondition objects are not migrated as independent reusable entities. | |
| 196 | + |
| 197 | +--- |
| 198 | + |
| 199 | +## Test Steps Handling |
| 200 | + |
| 201 | +### Manual Tests |
| 202 | +Manual test cases are migrated with their full step definitions. Each step's **Step Description** and **Expected Result** fields are mapped directly. Step ordering is preserved, and step-level attachments (e.g., screenshots embedded in steps) are migrated as well. All X-Ray test step templates, except Gherkin, are mapped to the **Manual Test Steps** template in Test Steps of a Test Case. |
| 203 | + |
| 204 | +### BDD / Gherkin Tests |
| 205 | +For BDD-type test cases in X-Ray, the full **Gherkin scenario** text (Given/When/Then) is extracted and stored in the test case as structured BDD content under the **BDD Scenarios** template in Test Steps. |
| 206 | + |
| 207 | +--- |
| 208 | + |
| 209 | +## Troubleshooting |
| 210 | + |
| 211 | +| Problem | Solution | |
| 212 | +|---|---| |
| 213 | +| **Invalid X-Ray credentials** | Verify your X-Ray Client ID and Client Secret. Re-generate them from X-Ray Settings if needed. Ensure you are using **X-Ray Cloud** credentials, not X-Ray Server/Data Center. | |
| 214 | +| **Invalid Jira credentials** | Confirm you are using a **Jira API Token** (not your Jira password). Generate one at [Atlassian API Tokens](https://id.atlassian.com/manage-profile/security/api-tokens). Verify the email matches the account that owns the token. | |
| 215 | +| **No projects found** | Verify your Jira account has access to at least one project containing X-Ray test cases. Check that X-Ray is installed and active on your Jira Cloud instance. | |
| 216 | +| **Migration stalls or takes too long** | Large projects (thousands of test cases with attachments) may take 10–30 minutes. If it does not resume after 30 minutes, re-initiate the migration. | |
| 217 | +| **Missing attachments** | Verify that the Jira API token has permission to download attachments from the source project. | |
| 218 | +| **Custom fields not appearing** | Custom fields are auto-created during migration. Navigate to **Project Settings > Custom Fields** to verify they exist and are enabled. | |
| 219 | + |
| 220 | +--- |
| 221 | + |
| 222 | +## FAQ |
| 223 | + |
| 224 | +**Can I migrate multiple Jira projects?** |
| 225 | + |
| 226 | +Yes. Run the migration once per Jira project. Each migration imports test cases from one X-Ray project into one TMS project. Repeat the process for additional projects. |
| 227 | + |
| 228 | +**Will migration affect my X-Ray data?** |
| 229 | + |
| 230 | +No. The migration is **read-only** on the X-Ray side. Your X-Ray test cases, test sets, and all other data remain untouched. |
| 231 | + |
| 232 | +**Can I run the migration again if something goes wrong?** |
| 233 | + |
| 234 | +Yes. You can re-run the migration for the same project(s). Review the results after each run. |
| 235 | + |
| 236 | + |
| 237 | +**Are Gherkin/BDD scenarios preserved exactly as written?** |
| 238 | + |
| 239 | +Yes. The full Gherkin text (Feature, Scenario, Given/When/Then blocks) is extracted and stored in the TMS test case with formatting and step structure preserved. |
| 240 | + |
| 241 | +**What if I have test cases with no steps?** |
| 242 | + |
| 243 | +Test cases without steps are still migrated. The test case metadata (title, description, priority, labels, etc.) is imported, and the steps section will be empty. |
| 244 | + |
| 245 | +**Is X-Ray Server (Data Center) supported?** |
| 246 | + |
| 247 | +No. This migration currently supports **X-Ray Cloud** (on Jira Cloud) only. |
| 248 | + |
| 249 | +--- |
| 250 | + |
| 251 | +## Known Limitations |
| 252 | + |
| 253 | +| Limitation | Details | |
| 254 | +|---|---| |
| 255 | +| **X-Ray Cloud only** | X-Ray Server and Data Center are not supported | |
| 256 | +| **No execution data** | Test Plans, Test Runs, and execution logs are excluded by design | |
| 257 | +| **No incremental sync** | Migration is a one-time import, not a continuous sync | |
| 258 | +| **Standalone Preconditions** | Precondition text is captured within test cases, but standalone Precondition objects are not migrated as independent reusable entities | |
| 259 | +| **Test case comments** | Jira comments on test case issues are not migrated | |
| 260 | +| **Execution environments** | X-Ray environment configurations are not migrated | |
| 261 | + |
| 262 | +<nav aria-label="breadcrumbs"> |
| 263 | + <ul className="breadcrumbs"> |
| 264 | + <li className="breadcrumbs__item"> |
| 265 | + <a className="breadcrumbs__link" href={BRAND_URL}> |
| 266 | + Home |
| 267 | + </a> |
| 268 | + </li> |
| 269 | + <li className="breadcrumbs__item"> |
| 270 | + <a className="breadcrumbs__link" target="_self" href={`${BRAND_URL}/support/docs/`}> |
| 271 | + Support |
| 272 | + </a> |
| 273 | + </li> |
| 274 | + <li className="breadcrumbs__item breadcrumbs__item--active"> |
| 275 | + <span className="breadcrumbs__link"> |
| 276 | + One Click Migration from X-Ray |
| 277 | + </span> |
| 278 | + </li> |
| 279 | + </ul> |
| 280 | +</nav> |
0 commit comments