Are BMC AMI DevX and Compuware Topaz the same thing?

Substantially, yes. BMC acquired Compuware (BMC) in 2020 and has since folded the Compuware developer and test tooling, the Topaz Workbench and the products that ran inside it, into the BMC AMI DevX family. Topaz Workbench is now branded BMC AMI DevX Workbench for Eclipse, Xpediter is BMC AMI DevX Code Debug, ISPW is BMC AMI DevX Code Pipeline, and File-AID and Abend-AID carry the BMC AMI DevX prefix. So this is not two competing products to choose between. It is one product lineage under one owner, observed at two points in its naming history. The practical question for a buyer is which name and which contract era your entitlements sit under, and how BMC consolidates them at renewal.

Do we need to migrate from Compuware Topaz to BMC AMI DevX?

Functionally there is rarely a forced migration, because the underlying tools are the same code carried forward under new names, and the Topaz Workbench continues to host them as the renamed AMI DevX Workbench. The change buyers actually feel is contractual, not technical: as legacy Compuware schedules expire, BMC commonly moves the entitlement onto current BMC AMI DevX terms, often subscription based and frequently aligned with the wider BMC AMI portfolio. The work at renewal is reconciling what you are entitled to under the old Compuware paper against what the new BMC AMI DevX quote actually grants, seat for seat and component for component.

What changes at renewal when Compuware tools move under BMC AMI DevX?

Three things commonly shift. First, the naming and packaging: standalone Compuware products are presented as components of the BMC AMI DevX family, which can blur what you previously held as separate, individually priced entitlements. Second, the model: legacy perpetual plus maintenance positions are often steered toward subscription, changing the budget shape and the exit profile. Third, the bundle context: the renewal is increasingly framed inside a broader BMC AMI relationship rather than as a discrete Compuware deal. None of that is inherently bad, but it means the new quote rarely maps line for line onto the old one, and reconciling the two is where the leverage lives.

BMC AMI DevX vs Compuware Topaz

BMC AMI DevX vs Compuware Topaz: one owner, two stacks.

This is not a choice between rivals. BMC acquired Compuware (BMC) in 2020 and rebranded the Topaz developer and test tooling as BMC AMI DevX. The products are one lineage under one owner. What differs is the contract era your entitlements sit in, and what BMC does with them at renewal.

Treat this as a reconciliation, not a product decision. BMC AMI DevX is the current branding of the Compuware Topaz stack, so there is no feature contest to settle and no real migration to fund. The exposure is contractual: as legacy Compuware schedules expire, BMC commonly repackages the entitlement onto current BMC AMI DevX terms, often subscription, often inside a wider BMC AMI relationship. The buyer side work is to map what you already hold under the old Compuware paper against what the new AMI DevX quote actually grants, component for component and seat for seat, before agreeing to anything. The naming change is the vendor's leverage. The contract reconciliation is yours.

Compuware Topaz heritage names against current BMC AMI DevX names
Dimension	Compuware Topaz (heritage)	BMC AMI DevX (current)
Owner	Compuware, independent until 2020	BMC, since the 2020 acquisition
Workbench	Topaz Workbench	BMC AMI DevX Workbench for Eclipse
Debug	Xpediter	BMC AMI DevX Code Debug
Source and release	ISPW	BMC AMI DevX Code Pipeline
Test and data	Topaz for Total Test, File-AID	BMC AMI DevX Total Test, File-AID
Fault analysis	Abend-AID	BMC AMI DevX Abend-AID
Common model	Perpetual plus maintenance on legacy paper	Increasingly subscription, often bundled in BMC AMI

Compuware Topaz heritage names against current BMC AMI DevX names

Dimension

Compuware Topaz (heritage)

BMC AMI DevX (current)

Owner

Compuware, independent until 2020

BMC, since the 2020 acquisition

Workbench

Topaz Workbench

BMC AMI DevX Workbench for Eclipse

Debug

Xpediter

BMC AMI DevX Code Debug

Source and release

ISPW

BMC AMI DevX Code Pipeline

Test and data

Topaz for Total Test, File-AID

BMC AMI DevX Total Test, File-AID

Fault analysis

Abend-AID

BMC AMI DevX Abend-AID

Common model

Perpetual plus maintenance on legacy paper

Increasingly subscription, often bundled in BMC AMI

Because there is no rival to pick, the decision is about how you handle the contract transition. Use it this way:

Hold the line on legacy Compuware terms if

Your existing perpetual plus maintenance position is cheaper than the proposed subscription over your planning horizon
You hold favorable inherited terms, caps, or component pricing that the new AMI DevX template would dilute
Your developer seat count is stable, so a usage based or subscription model offers no real upside

Move to current BMC AMI DevX terms if

You want supported, current releases and the legacy version is approaching the end of practical maintenance
A consolidated BMC AMI deal genuinely lowers the combined run rate across DevX and your other BMC tools
Your seat count is volatile and a subscription model right sizes more cleanly than a perpetual estate

Either way, the foundational lever is the same: reconcile the old entitlement against the new quote line by line, confine the license to the developers who actually use the tools, and refuse any repackaging that quietly drops components you already paid for or extends term length in exchange for a headline discount.

Are they the same thing?Substantially yes. BMC AMI DevX is the rebranded Compuware Topaz stack after the 2020 acquisition. One lineage, one owner, two naming eras.

Do we have to migrate?Rarely a forced technical migration. The change you feel is contractual, as legacy Compuware schedules are repackaged onto current AMI DevX terms.

What changes at renewal?Naming and packaging, the move toward subscription, and a wider BMC AMI bundle context. The new quote rarely maps line for line onto the old one.

What is the first move?Reconcile what you already hold under the old Compuware paper against what the new AMI DevX quote grants, component by component, before agreeing.

No product contest here. The deal is won in the reconciliation.

BMC AMI DevX vs Compuware Topaz: one owner, two stacks.

The verdict

Head to head

Who should do what

Frequently asked

A rebrand is not a re-buy. We reconcile old paper to new quote.