Migrating from HP Quality Center to Micro Focus ALM: What Your Team Needs to Know
If your organization is still running HP Quality Center (QC) and you're being asked to migrate to Micro Focus ALM, the good news is that ALM is the direct successor to QC. This isn't a platform migration — it's an upgrade. But "upgrade" doesn't mean "frictionless." There are real changes to the interface, the database schema, and the integration landscape that your team needs to plan for.
Understanding the Product History
HP Quality Center was the dominant enterprise test management tool for most of the 2000s and 2010s. HP renamed it HP ALM when they added application lifecycle management features. When Micro Focus acquired the HP Software division in 2017, the product became Micro Focus ALM. The current version as of this writing is ALM 24.x.
The core data model — projects, test plans, test lab, defects — is the same across all these versions. Your test cases, execution history, and defects will survive the migration. What changes is the server infrastructure, some UI elements, and the integration points that other tools connect to.
Pre-Migration Assessment
Before scheduling your migration, answer these questions:
What version of QC/ALM are you running? The upgrade path differs depending on your starting version. Migrating from QC 10.x to ALM 24.x may require intermediate upgrades or a full project export and re-import. Your Micro Focus support team or partner can map the exact path.
How many projects do you have? Each project needs to be upgraded individually. Large organizations with dozens of projects should prioritize which ones migrate first based on active use.
What integrations do you have? Common integrations include connections to Jira, Jenkins, LoadRunner, and UFT (Unified Functional Testing). Some of these integrations use ALM's OTA (Open Test Architecture) COM API. If you have custom integrations or scripts built on OTA, they'll need to be tested against the new version.
What customizations exist? ALM's Project Customization allows site and project admins to add custom fields, workflow scripts (in VBScript), and entity validation rules. Document all customizations before you start — some may need to be re-applied after the migration, and a few may not be supported in newer versions.
The Migration Path
For most organizations, the migration follows this sequence:
Step 1: Upgrade the ALM server. This is handled by your IT or tools team. The Micro Focus upgrade guide covers the database migration (Oracle or SQL Server) and server configuration. Budget time for this — it's not an afternoon project.
Step 2: Upgrade projects. Once the server is running the new version, each project goes through an upgrade wizard in the ALM Site Administration console. The wizard migrates the project's database schema and validates data integrity. For large projects, this can take several hours.
Step 3: Verify data. After upgrade, spot-check critical test plans, recent test executions, and open defects. Pay particular attention to attachments — these are sometimes the first casualty in an upgrade if the file storage configuration has changed.
Step 4: Test integrations. Re-test every integration point. If you use the ALM-Jira connector, verify that you can still create defects from ALM that appear in Jira, and vice versa. If you have CI/CD pipelines posting results to ALM, run a test pipeline and confirm results appear correctly.
Step 5: User acceptance. Before rolling out to the full team, have a small group of representative users work through their normal workflows in the upgraded system. Surface usability issues before everyone is affected.
What Changes for QA Engineers Day-to-Day
The core workflows remain the same: you still navigate to Test Plan to write tests, Test Lab to run them, and Defects to track bugs. But there are a few notable differences:
The client technology changed. Older versions of ALM required Internet Explorer and an ActiveX plugin. Modern ALM uses a web-based client that runs in Chrome or Edge without browser plugins. This is an improvement, but custom workflow scripts written in VBScript for the old client may need to be rewritten or adapted.
The REST API is more capable. Newer ALM versions have an improved REST API alongside the older OTA API. If you have automation that posts test results to ALM, the REST API is now the preferred path. The older OTA API still works but is considered legacy.
Performance profile may differ. Some teams find the newer ALM client faster than the old ActiveX-based one; others find specific operations slower. Identify your team's most common workflows and measure them in a staging environment before committing to rollout.
Common Migration Problems
Attachments don't survive. If your file storage configuration changes between the old and new server, attachments on test cases and defects may become inaccessible. Verify your storage path configuration matches between old and new environments before running the upgrade.
Workflow scripts break. VBScript-based workflow scripts (field validations, email triggers, automatic field population) sometimes stop working after an upgrade because of changes to the underlying object model. Test all workflow scripts in a staging project first.
Reports look different. ALM's built-in reporting uses a separate module that may have changed. Custom reports built with previous versions may need to be rebuilt.
Third-party connectors need updates. If you use a third-party connector for Jira or another tool, check that the connector version supports your new ALM version. Connector compatibility often lags the ALM release by a few months.
Planning the Rollout
Don't migrate everyone at once. A phased approach works better:
Start with a pilot team — ideally one that has a mix of power users and casual users. Run them on the new system for two to four weeks while others remain on the old instance. Collect feedback, fix issues, and document any workflow changes before rolling out to the rest of the organization.
Keep the old instance running in read-only mode for at least 30 days after full cutover. Teams sometimes discover they need historical data that didn't make it into the new system, and having the old instance available as a reference is worth the server cost.
After the Migration
Once you're on current ALM, establish a regular upgrade cadence. Running significantly out-of-date versions is what creates the painful multi-version jumps. Staying within one or two major versions of the current release makes future upgrades incremental rather than transformational.
Also consider this an opportunity to clean up your project. Old ALM instances accumulate years of test cases that were never deleted, duplicate defect types, and unused custom fields. An upgrade is a natural moment to audit what you actually use and remove what you don't.
Keeping an Eye on Production
Your ALM test cycles confirm the application works before a release. But the gap between releases is when production issues most often surface — configuration drift, third-party service outages, data problems that only appear with real user data.
A continuous monitoring tool like HelpMeTest closes that gap by running through your application's key workflows on a schedule and alerting your team immediately when something stops working. It's not a replacement for ALM's formal test management — it's the monitoring layer that covers the time between your planned test cycles.
A successful migration to current ALM puts your test management on a supportable foundation. What you do next to monitor production is a separate conversation, but an important one.