Merito UFT Phoenix
Merito UFT Phoenix converts your OpenText UFT One tests from VBScript to Python automatically, in place in your ALM project or from a folder of tests on disk, so the investment your team has made carries forward instead of being rewritten by hand.
Read the customer briefSupported on
Phoenix installs from an offline Windows package with its own Python runtime and needs no internet access to install or to convert.
VBScript tests convert to UFT Python tests automatically, rebuilt through UFT's own object model.
On the ALM path, test IDs, links and Test Lab execution history stay where they are.
A GO or NO-GO verdict and a named blocker list before anything in your project changes.
Backup confirmation, an all-or-nothing pre-flight check, byte-for-byte upload checks and rollback.
A Python suite your engineers can extend with AI coding assistants and hire for.
Why this matters now
Most UFT One suites were built over a decade in VBScript. They still work, but the language around them is moving on, and every year on VBScript widens the gap between the regression suite and the rest of engineering.
Microsoft has formally deprecated VBScript and laid out a phased plan to remove it from Windows. The direction is set, and a suite that stays on VBScript moves further from where the rest of your engineering organization already works.
OpenText Functional Testing 26.3 made Python test authoring officially supported, so new tests can be written in Python or VBScript. The platform you already own has a modern path. The suite you built in VBScript is what keeps most teams from taking it.
AI coding assistants, modern pipelines, code review tools and quality gates all work in Python. A VBScript suite sits outside all of it, so every new test is still written the slow way.
Retyping a regression suite that already works can take a year of engineering time, and coverage is at risk for as long as two versions of the suite run side by side.
In UFT, a reusable action runs inside the calling test's script engine. Convert tests one at a time and chains that mix VBScript and Python fail at runtime.
Fewer engineers want to maintain VBScript every year. Python skills are everywhere, so a Python suite is one any modern engineer can pick up.
Solution overview
Merito UFT Phoenix is a Windows utility, built by Merito, that converts OpenText UFT One GUI tests written in VBScript into UFT One Python tests. It converts a whole OpenText ALM project in place, or a folder of UFT tests on local disk or a network share, and rebuilds each test through UFT's own Automation Object Model so the result is a native UFT Python test.
On the ALM path, converted tests keep their test IDs, links, version history and Test Lab instances with their execution history. Tests that call each other's reusable actions are converted together, so every call chain runs under one script engine.
Conversion is deterministic and rule-based. Phoenix refuses anything it cannot convert safely rather than guessing, so your team fixes those lines at the source and nothing ships on a wrong translation.
What Phoenix does
Phoenix does the conversion work your team would otherwise do by hand, with safeguards at every step that touches your ALM project.
Your VBScript tests convert to UFT Python automatically. Nobody spends the next year retyping a regression suite that already works.
On the ALM path, conversion happens inside the project your tests already live in. Test IDs, links, version history and Test Lab execution history stay where they are.
The first pass is read only and makes zero ALM writes. You see the GO or NO-GO verdict, each test's blockers, and who holds checkouts and locks before anything in your project changes.
Phoenix writes only after a backup confirmation and a whole-project pre-flight check. Every upload is compared byte-for-byte, and a failure rolls the run's tests back from snapshots.
Cross-test reusable actions are rebuilt natively and consumed by reference, so no chain is left half VBScript and half Python.
A Python suite is one your engineers can automate against, extend with AI assistance and hire for.
Operating model
Step 1
Phoenix's environment check confirms UFT One, the ALM client and UFT's Python runtime on every conversion and run machine, plus a live ALM login. Output is a clean check on every host.
Step 2
Analysis inventories every test, flags blockers and returns a GO or NO-GO verdict with zero ALM writes. Output is a blocker list split into fix at the source and out of scope.
Step 3
A representative set of tests converts and runs in its existing Test Lab sets. Output is pilot tests that pass upload verification and match their VBScript baseline.
Step 4
Conversion rules are tuned to your suite until a second pilot pass produces no new warnings and identical output. Output is a rule set ready for the full project.
Step 5
Checkouts and locks are cleared and the backup is confirmed before the window opens. Output is a project ready to convert in one run.
Step 6
The whole project converts, every upload is verified and Test Lab spot checks confirm parity. Output is a Python suite in the ALM project it started in.
Read-only assessment
We show you what converts cleanly and what needs attention before anything in your automation project changes.
Platform ecosystem
Phoenix works inside the OpenText testing stack you already run. Merito is an authorized OpenText reseller and services partner, so the UFT One upgrade a Python suite depends on, the licensing around it and the conversion itself run through one partner.
Selected partner and platform coverage
Services alignment
Merito built Phoenix and can run the migration with you from assessment through rollout.
Run the read-only analysis on your project, triage every blocker and size the remediation before anyone commits to a conversion date.
Convert a representative set of tests, run them in your existing Test Lab sets and confirm they match their VBScript baseline.
Fix refused constructs in the VBScript, plan for recovery scenarios and Environment variables, and review the checkpoints worth a second look.
Plan the window with your ALM administrators, clear checkouts and locks, and run the whole-project conversion with verified uploads.
Python test support is required on the conversion machine and every run machine. Merito handles the UFT One upgrade and OpenText licensing it depends on.
Set standards for the converted suite and equip your engineers to write new Python coverage, including with AI coding assistants.
Outcomes
Each converted test is uploaded, downloaded again and compared byte-for-byte before it is checked in.
Converted tests run in your existing Test Lab sets and fail only where the VBScript version also fails.
Reports, traceability and execution history keep pointing at the same tests after conversion.
The analysis reports which tests are blocked and why, so remediation is a defined list instead of a surprise.
Engineers write new coverage in Python with the AI assistants and tools they already use.
Each run keeps its analysis, conversion and verification records as evidence of what changed.
Why Merito
Merito designed and built UFT Phoenix, so the team running your migration knows the converter from the inside.
Phoenix is rule-based. The same input produces the same output, and anything it cannot convert safely is refused rather than guessed.
Licensing, the UFT One upgrade and the migration run through Merito, so the program has one owner.
Merito is an AI enterprise software partner for application security, quality and DevSecOps, so the converted suite lands in a delivery practice built around it.
Phoenix runs fully offline. Merito does not receive your test assets unless you provide them under a services engagement.
Supported versions, the write-safety model and known limitations are published, so your team can check the details before the first call.
Security validation and release management
Security validation
Phoenix treats your ALM project as production data. Analysis makes zero ALM writes. Before any write, Phoenix requires a backup confirmation and checks the whole project against the analysis, so a project converts completely or not at all.
Every converted test is uploaded, downloaded again and compared byte-for-byte before it is checked in. If a step fails, Phoenix rolls the run's tests back from pre-conversion snapshots, and on version-controlled projects the prior VBScript version stays in ALM history.
Release management
A conversion is only done when the converted tests run. Merito pilots the conversion in your existing Test Lab sets and holds the bar at parity or better, where converted tests fail only where the VBScript version also fails.
Each conversion wave is gated on the Phoenix executive summary verdict, and every run folder is kept as the record of what changed and when.
AI and automation
Phoenix does not use AI to convert your tests. Conversion is deterministic, because a regression suite needs the same answer every time.
What changes is what your team can do next. Once the suite is Python, AI coding assistants, code review tools and quality gates can read it and extend it, so new coverage takes far less effort than it did in VBScript.
Applied AI use cases
Point an AI coding assistant at the converted suite and draft new tests in the patterns your team already uses.
Run the Python test code through the same review, linting and pipeline checks as the rest of your codebase.
New team members work in a language they already know instead of learning VBScript to maintain the suite.
Frequently Asked Questions
Consultation request
Tell us about your UFT One suite and where it lives. Merito will walk through a read-only assessment, what converts cleanly, what needs attention and what a pilot would cover.
Assessment
See what converts cleanly and what needs attention before anything in your ALM project changes.
Pilot
Convert a representative set of tests and confirm they match their VBScript baseline before the full rollout.
Get Started
Your request will be reviewed by our team so we can connect you with the right solution, service, and expert.
Next step
Same tests. Same history. A language with a future. Request a quote for the Phoenix migration, the UFT One upgrade it depends on and the OpenText licensing around it.
