Quick import
Quick import copies a project from your current test management tool into Arcus, with folders, step groups, execution history, and custom fields.
Prerequisites
- Your tool’s credentials.
- The Jira integration for Jira Xray (recommended for Zephyr Scale), or Azure DevOps for Azure DevOps Test Plans.
Start a quick import
Section titled “Start a quick import”-
Open the project switcher at the top of the left navigation, click Project Settings, then open Import.

-
Click Quick import from.
-
In Choose your current Test Management tool, select your tool: qTest, TestRail, Testmo, Jira Xray, BrowserStack, Zephyr Scale, Azure DevOps Test Plans, Qase, or TestMuAI.

The Quick import wizard opens on its first stage, Establish Connection.
Connect to your tool
Section titled “Connect to your tool”-
In qTest Host name, enter your qTest site URL, for example
https://yourcompany.qtestnet.com/. -
In qTest API Key, enter your qTest API key.
-
If your project uses qTest Parameters, enter its URL in qTest Parameters URL, for example
parameters.qtestnet.com.
-
In TestRail Host name, enter your TestRail site, for example
qa-team.testrail.io. -
In TestRail Email, enter the email address you sign in to TestRail with.
-
In TestRail API Key, enter your TestRail API key.
-
In Testmo Host name, enter your Testmo site, for example
yourorg.testmo.net. -
In Testmo API Key, enter your Testmo API key.
Xray reads projects and users through your Jira connection, so connect Jira first. Once it is connected, a banner confirms it.
-
In Client ID, enter your Xray client ID.
-
In Client Secret, enter your Xray client secret.
If Jira isn’t connected, a banner says so and links to the Jira setup, and Proceed stays unavailable until you connect it.
In API Token, enter your BrowserStack username and access key in the form username:access_key.
Zephyr Scale reads project names and users through your Jira connection, so connect Jira first. Once it is connected, a banner confirms it.
-
In Zephyr Scale API Token, enter your Zephyr Scale API token.
-
In Region, select the region your Zephyr Scale instance runs in: US, EU, AU, or DE. It defaults to US. An API token works only in the region it was issued in.
If Jira isn’t connected, you can still import, but a banner warns that project names fall back to project keys and user mapping is unavailable.
Azure DevOps Test Plans needs no credentials here. It uses your Azure DevOps integration instead. If Azure DevOps isn’t connected yet, Connect Azure DevOps says so: click Go to Integrations and connect Azure DevOps, then start the import again.
Once Azure DevOps is connected, Azure DevOps Connection shows the organization you’re connected to. Click Proceed. There is no Test connection step. If the authorization has expired or been revoked, click Reconnect Azure DevOps instead.
In API Token, enter your Qase API token.
-
In Username, enter your TestMuAI username.
-
In Access Key, enter your TestMuAI access key.
For every tool except Azure DevOps Test Plans, click Test connection. Once Connection Tested Successfully appears, click Proceed.

Choose what to import
Section titled “Choose what to import”The How your <tool> data will be migrated to Arcus? panel shows what each item in your tool becomes in Arcus. Folder structure, execution history, and custom fields come across with them.
Under Select Project, each tool has two options, both selected by default. The first brings plans, runs, or cycles as well as test cases. Include closed/completed items brings items already closed or completed in your tool.
| qTest | Arcus |
|---|---|
| Test Cases | Test Cases |
| Test Releases | Test Plans |
| Test Cycles | Test Runs |
| Test Runs | Test Case Executions |
First option: Import all the test cycles and test releases.
| TestRail | Arcus |
|---|---|
| Test Cases | Test Cases |
| Milestones | Test Plans |
| Test Runs | Test Runs |
| Test Results | Test Case Executions |
First option: Import all milestones and test runs.
| Testmo | Arcus |
|---|---|
| Test Cases | Test Cases |
| Test Suites | Folders |
| Test Runs | Test Runs |
| Test Results | Test Case Executions |
First option: Import all test runs and results.
| Jira Xray | Arcus |
|---|---|
| Tests | Test Cases |
| Test Plans | Test Plans |
| Test Executions | Test Runs |
| Test Runs | Test Case Executions |
First option: Import all the test plans and test executions.
| BrowserStack | Arcus |
|---|---|
| Test Cases | Test Cases |
| Test Plans | Test Plans |
| Test Runs | Test Runs |
First option: Import all test plans and test runs.
| Zephyr Scale | Arcus |
|---|---|
| Test Cases | Test Cases |
| Folders | Folders |
| Test Cycles | Test Runs |
| Test Executions | Test Case Executions |
First option: Import all test cycles and executions.
| Azure DevOps Test Plans | Arcus |
|---|---|
| Test Cases | Test Cases |
| Test Suites | Folders |
| Test Plans | Test Plans |
| Test Runs | Test Runs |
| Test Results | Test Case Executions |
First option: Import all test runs and results.
| Qase | Arcus |
|---|---|
| Test Cases | Test Cases |
| Test Plans | Test Plans |
| Test Runs | Test Runs |
First option: Import all test plans and test runs.
| TestMuAI | Arcus |
|---|---|
| Test Cases | Test Cases |
| Test Runs | Test Runs |
First option: Import all test runs and executions.
For Jira Xray and BrowserStack, a banner estimates how many API calls the import makes and how long it takes. Other integrations on that account can slow down while it runs.
-
Under Select Project, choose the options you want.
-
Select the project to import. The number of projects found appears beside Select Project.
-
Click Continue.
Map users
Section titled “Map users”The Map Users stage lists every user in the source project. Each one needs an Arcus user, who becomes the owner of their items. TestMuAI has no Map Users stage and goes straight to Map Fields.
-
For each user, select an Arcus user under TMS USERS. Users mapped counts your progress.
-
Click Continue. It becomes available once every user is mapped.
Map field values
Section titled “Map field values”Map Fields pairs values from your tool with Arcus values. Values with the same name are matched automatically. Any other value is set to Create ‘<value>’, which adds it to Arcus as a new value.
Every tool maps Priority and Execution status. Some also map a third field:
- qTest: Test case status.
- TestRail and Testmo: Case type.
- Jira Xray, BrowserStack, and Qase: Test case type.
-
Review each field. To use an existing Arcus value instead of creating one, select it from the list.
-
Click Begin Import.
Track the import
Section titled “Track the import”The last stage is named for what your tool imports: Import of Test Cases, Cycles & Releases for qTest; Import of Test Cases, Milestones & Runs for TestRail and Testmo; Import of Test Cases, Plans & Executions for Jira Xray; Import of Test Cases, Cycles & Executions for Zephyr Scale; Import of Test Cases, Plans & Runs for BrowserStack, Azure DevOps Test Plans, and Qase; and Import of Test Cases & Runs for TestMuAI.
The import queues, then starts when a worker is free. While it runs, counters show progress for each kind of item, such as test cases, folders, step groups, attachments, and comments. Click View details for more, or Cancel to stop.
When it finishes, Import completed shows how many items of each kind came across, and how many were skipped. Click Done to close the wizard.
For qTest imports, you can also click Re-import. It starts a new import run that re-reads the qTest project and brings in anything new. In Re-import from qTest, choose what happens to test cases already imported that have changed in qTest:
- Leave existing imports only new test cases. Nothing already in Arcus is modified.
- Update existing updates changed cases in place and records the change in their history. Cases you edited in Arcus since the last import are reported and left untouched.
Review the import results
Section titled “Review the import results”Click Report on Import completed to open Import Results. It has a tab for each kind of item, such as test cases, test releases, and test cycles. Each tab shows:
- Totals for imported, skipped, and failed items.
- Failed to import: each item’s ID, title, error type, and the reason it failed.
- The imported items, with their new Arcus ID and folder.
Click Report on this page to download the results.
Was this page helpful?
Thanks for the feedback.