Register

// MIGRATION · FREE

We move your project to ComplexQA from any system

TestRail is transferred automatically via the API. Any other service or spreadsheets we transfer manually, quickly, and without stopping your work. Fields that are not in the standard model are kept in custom properties.

Send a requestHow it works
API
TestRail automatically
1 h
if the transfer is ready
0 ₽
whatever the size

TRANSFER MAPsource → ComplexQA

What goes where

SOURCEIN ComplexQASTATUS
Folders, sectionsSuitesTransferred
CasesTest casesTransferred
StepsSteps and expected resultsTransferred
RunsRuns and resultsTransferred
FilesAttachmentsTransferred
Own fieldsCustom propertiesVia properties
Jira linksURL propertyVia properties
UsersTeam membersTo discuss

// SOURCES

We transfer from any system

From TestRail we transfer automatically. From other systems manually, using your export, and just as quickly.

  • API · AUTOMATIC

    TestRail

    Transfer with an API key, from one hour.

  • MANUAL

    Qase

    From a project export.

  • MANUAL

    Test IT

    From a project export.

  • MANUAL

    Zephyr

    From a project export.

  • MANUAL

    Xray

    From a project export.

  • FILE

    Spreadsheets

    CSV, XLSX, and JSON in the ComplexQA import format.

  • MANUAL

    In-house system

    We study the format and write a transfer for it.

  • MANUAL

    Any other service

    Not on the list? Write to us, and we will transfer it.

// TRANSFER METHODS

Choose the right method

The method depends on the system you are moving from. If in doubt, write to us, and we will advise.

The transfer is free, whatever the project sizevolume within your ComplexQA plan

  • 01 · API

    TestRail

    automatically, from 1 hour

    • API key and instance address
    • The project is read directly
    • Suites, cases, steps, runs, attachments
    • Check after the transfer

    Free

  • 02 · MANUAL

    Any service

    from 2 days, complex projects up to 2 weeks

    • Qase, Test IT, Zephyr, Xray, and others
    • In-house systems
    • Mapping agreed before the work starts
    • Own fields in custom properties

    Free

  • 03 · FILE

    CSV, XLSX, JSON

    import in the ComplexQA format

    • Spreadsheets and exports
    • ComplexQA import format
    • Projects that lived in spreadsheets

    Free

Your system is not on the list?

We transfer from any system. We study the export and show what goes where before the work starts.

Send a request

// WHAT IS TRANSFERRED

Everything in the project is transferred

Most of it fits the standard ComplexQA model. The rest is kept in custom properties, without losses.

  • Suites and hierarchy

    The tree of folders and sections is kept as it is.

    Transferred

  • Test cases

    Cases with all text fields.

    Transferred

  • Steps and expected results

    The order of steps and the expected result of each step.

    Transferred

  • Runs and result history

    Past runs and the statuses of cases in them.

    Transferred

  • Attachments

    Files of cases and steps.

    Transferred

  • Custom fields

    They become custom properties with a matching value type.

    Via properties

  • Bug tracker links

    Links to Jira and other trackers are kept in a URL property.

    Via properties

  • Users and roles

    Transferred by agreement: members and permissions are discussed in advance.

    To discuss

// CUSTOM PROPERTIES

Any information model

If your system has fields that are not in the standard model, the data is not cut. Custom properties describe any properties of any elements.

  1. 01

    9 value types

    STRING, TEXT, INTEGER, DATE, URL, USER, DROPDOWN, CHECKBOX, MULTISELECT.

  2. 02

    One or several values

    A property holds one value or a list, as in the source system.

  3. 03

    Required and searchable

    A property can be made required and included in the project search.

  4. 04

    For any elements

    Test cases, bugs, runs and their results, autotests, documents, and checklists.

TEST CASE · ID 412transferred from TestRail

Card payment refund

Custom properties

Component
DROPDOWN
Payments
Jira task
URL
PAY-1187
Owner
USER
Anna Smirnova
Platforms
MULTISELECT
iOS, Android, Web
Estimate, min
INTEGER
15
In regression
CHECKBOX
Yes

// PROCESS

Four steps to working in ComplexQA

You do not need to stop working in your system during the transfer.

  1. 01

    Send a request

    Tell us which system you are moving from and how big the project is.

  2. 02

    We agree on the map

    Before the work starts, we show what goes where, including custom properties.

  3. 03

    Transfer

    TestRail with an API key, other systems from your export.

  4. 04

    Check

    We compare the number of transferred elements and show the differences, if any.

// QUESTIONS

Frequent questions

Everything else we discuss before the transfer starts.

Do we need to stop working during the transfer?

No. You keep working in your system while the project is assembled in ComplexQA.

Can we transfer only part of the project?

Yes. Name the suites you need, and we transfer only that part.

Is the run history transferred?

Yes. Runs and their results are transferred together with the cases.

What happens to the links to Jira bugs?

We keep them in a custom property of the URL type, and the links keep working.

And users and permissions?

They can be transferred, but team members and roles are discussed before the work starts.

What if the source format is non-standard?

We look into it separately. If a transfer is impossible, we tell you before the work starts, not after.