Skip to content
Dolpheen
DEEN
Contact

Healthcare · SwitzerlandCompleted

From QMetry to qTest in a single night

5,047 test cases, 11,508 test executions and a reconciliation report for every one of them — the complete test management landscape of a Swiss hospital group, migrated from QMetry to Tricentis qTest in a single night.

Situation

A complete test management landscape, in one move.

This summer we migrated the complete test management landscape of a Swiss hospital group from QMetry to Tricentis qTest — 33 projects, with years of historic test data in them.

Scope

What moved, across 33 projects.

  • 5,047 test cases in 6,004 versions
  • 11,508 test executions with their 11,438 execution logs
  • 190 releases, 370 cycles, 2,385 test suites and 751 modules
  • 525 embedded images, preserved in the descriptions and attached as originals

Approach

Proven on our own sandbox, loaded in one night.

  1. 01

    A purpose-built migration pipeline.

    Proven end to end on our own sandbox instance before anything touched the customer's production site.

  2. 02

    One night, six parallel lanes.

    The final load ran in six parallel lanes in a single night, inside the agreed API rate budget. Every API call was logged.

  3. 03

    Every object reconciled.

    After the load, every single source object was reconciled against the live system: either it exists as a qTest id, or there is a documented reason why it does not. No silent skips.

  4. 04

    33 verification reports.

    One human-readable report per project, so the customer can check our work instead of taking our word for it.

  5. 05

    After go-live, under real scrutiny.

    The customer put the result under real scrutiny and found genuine edge cases in years of historic test data. Every finding was analysed, repaired in the live system and re-verified within days.

Result

All 33 projects reconciled clean.

  • Complete landscape migrated in a single night, inside the agreed API rate budget
  • Every source object either exists as a qTest id or carries a documented reason why it does not
  • Every finding after go-live analysed, repaired in the live system and re-verified within days
  • 74 executions were not created: in QMetry, a test case of one project ran in another project's suite — a property of the source data, documented per object and accepted by the customer

Tools

What was involved.

  • QMetry (source)
  • Tricentis qTest (target)
  • Purpose-built migration pipeline
  • Per-object reconciliation and verification reports

Responsibility

Who did what.

Dolpheen

  • Migration pipeline, built and proven on our own sandbox
  • Final load in six parallel lanes, inside the API rate budget
  • Reconciliation of every source object against the live system
  • 33 verification reports, one per project
  • Analysis, repair and re-verification of every post-go-live finding

Client

  • Access to source and target systems
  • Review of the result against years of historic test data
  • Acceptance of the documented exceptions

At a glance

Industry
Healthcare
Country
Switzerland
Status
Completed · August 2026
Service
Tool Migration & Modernisation
From → to
QMetry → Tricentis qTest
Scale
5,047 test cases · 33 projects
Engagement model
Co-delivery
About this service

Facing the same move?

Tell us which system you are on and what has to survive the migration. We will come back with an inventory approach and an effort range.

Request the assessment