Zephyr HP ALM Migration Adapter is a unique API-driven solution that lets you migrate your data from HP ALM directly into Zephyr deployment Standalone. The solution works with either an On-premise Prem or in the a Cloud . Zephyr offers dedicated migration service offering that can speed up the transition phase from tools such as HP ALM. Zephyr team will lead the migration process end to end, which includes - planning, prepping the environment, setting up the adapter, dry runs, data migration and verification.installation of Zephyr Standalone.

Note
The HP ALM Migration works with HP ALM 11.0 5 and above. Users can retrieve the HP ALM Migration Adapter from the following download page.

Planning

:

Planning is an important phase of migration. This phase involves:
Determining HP ALM artifacts that need to be migrated
Reviewing production, stage environments of HP ALM and Zephyr configurations
Optimizing stage environments
The sections below explain these in more details:
Determine HP ALM artifacts that need to be migrated
It is important to acknowledge that not all the data you have in legacy system remains good to be transferred. We review with you, In this phase, you should review how your testing methodologies , and practices have changed over the years time and determine the right HP ALM artifacts we suggest transferring to Zephyr. This is typically one or two days of effort where we engage in a dialog with all the project leads and managersthat makes sense to transfer to Zephyr.

Review Production, Stage environments and configurations
Not all HP ALM environments are configured the same. We undertake end to end analysis of hardwarePlease review the hardware configuration, memory allocation for processes, API throttling configurations, network topology etc . We engage with system administrators, network administrators and database administrators.
Optimize stage environment
We determine which style of migration is most suitable for your needs. Typically, we follow for each HP ALM environment.

Determine the migration style
There are two possibilities for the migration: big bang migration or trickle migration. Big
In big bang migration, the process is conducted over a weekend when both HP ALM and Zephyr are shut down for users. With this approach, we suggest at least one dry run of the migration in the a stage environment before the live event. With
In trickle migration, we you may take an incremental approach to migrating data. We run both the systems in parallel and move projects by having both HP ALM and Zephyr available in parallel during weeks/months, and moving projects from HP ALM to Zephyr based on business needs. With this approach a thorough analysis of data dependency is conducted in a stage environment.
With either approach, we undertake at least one week of review, preparation and optimization of stage environment; this includes optimization of system that has Zephyr HP ALM Migration adapter installed. Full access to stage environment is required.

Adapter Overview

:

Below section provides a high-level overview of communication between Zephyr Server, HP ALM and Zephyr HP ALM Migration adapter.

Image Removed

Below steps

The Zephyr HP ALM Migration adapter provides an easy to use HTML UI to configure and run migration.
It uses REST API’s APIs to pull extract data out of from HP ALM and publish import data into Zephyr Standalone. Listed below are few HP ALM API’s we use:
{HP-ALM-HOST}/qcbin/rest/domains
{HP-ALM-HOST}/qcbin/rest/domains/{DOMAIN}/projects
{HP-ALM-HOST}/qcbin/rest/domains/{DOMAIN}/projects/{PROJECT}/tests?fields=name,id,parent-id,creation- time,description,dev-comments {HP-ALM-HOST}/qcbin/rest/domains/{DOMAIN}/projects/{PROJECT}/design-steps?fields=name,id,parent- id,step-order,link-test,expected,description
You can learn more about Zephyr API’s at the DEVELOPER .
Using our migration service you can migrate test cases, test steps, attachments, sub-referenced test steps, folder structure and much more depending on your needs determined during the planning phase.

Setup Instructions:

The section below provides a high-level overview of

adapter setup instructions.

Download and copy Zephyr HP ALM adapter jar file on to a standalone machine that has access to both HP ALM and Zephyr
Install JRE 1.8 or higher
Allocate at least 4 GB of memory for the adapter process. Data is processed in batches to optimize performance and reduce memory usage.
Ensure you can access HP ALM using admin credentials
Ensure you can access Zephyr using Test Manager credentials
Click on the jar file to run the adapter.
Access the adapter via the browser and follow the onscreen instructions to kick off migration as per the plan.

Supported Migration Entities:

NoteUp to Zephyr Standalone 6.2, Zephyr is able to support migration of the following entities from HP ALM 12.5 (on-premises) version.

the communication between the Zephyr Standalone instance, the HP ALM instance, and the Zephyr HP ALM Migration adapter:

Image Added

Supported Migration Entities

The current version of the Zephyr HP ALM Migration Adapter supports migration of the following types of entities:

Projects
Users
Tests
Test Attachements
Test Steps
Step Attachments
Test Folder Organization

Requirements

Requirement Custom Fields

Test Custom Fields
Release
Cycle
Test Run (Execution in Zephyr)

Image Removed

Migrating Defects from HP ALM to Jira

The current process for migrating historical defects from HP ALM into JIRA involves the following steps:

The defects are exported from HP ALM using APIs available from HP
The defects are then imported into JIRA by using JIRA REST API calls or via a .CSV file

Setup & Usage Instructions

For setup and usage instructions, please refer to ___.

Additional Questions

:

Versions Compared

Old Version 8

New Version 9

Key

Table of Contents