Skip to content

Migration · /// Horizon → AVD

Migrate Horizon → AVD with data, not slide decks.

The same scenario engine runs on VMware / Omnissa Horizon and on Azure Virtual Desktop. Baseline Horizon today, test AVD tomorrow on the same `.lgs` workload, and compare generic p95 and host-pool density side-by-side. Migration validation is a positioning/workflow motion, not a separate engine.

Plan the Horizon → AVD migration with dataTalk to an engineer

Same scenario, both stacksGeneric p95 on each sideCompare and sign cutover

Migration cockpit. Baseline overlay across stacks.

The Problem

Horizon → AVD migrations live on slide decks.

Most Horizon → AVD migrations are pitched on architectural slide decks. Production discovers the gap on cutover weekend. The missing piece is measured side-by-side validation on the same scenario shape.

Two stacks, two test plans.

Without one scenario engine spanning both, teams maintain a Horizon test plan and an AVD test plan separately. Different definitions of "working", different per-step measurements, no direct comparison.

Azure cost forecasts built on guesses.

AVD host-pool sizing depends on measured concurrency on real session hosts, not Horizon-equivalent calculations. Wrong session-host SKU and wrong host-pool count translate directly into Azure invoice surprises.

Brand transition + platform transition compound.

The VMware → Omnissa Horizon brand transition plus the Horizon → AVD platform transition layer on top of each other. Test data scattered across versions; cutover decisions made on incomplete information.

Why LoadGen for Horizon → AVD migration

One scenario engine. Both stacks. Measured.

Author the scenario once. Replay it through the generic wizard against Horizon. Replay unmodified through the 7-step AVD wizard against AVD. Compare both on the same chart with generic p95 on each side. Cutover signs on data.

Horizon baseline via L&P

Horizon scenarios run on the same engine. Load-test Horizon at concurrency through the same scenario engine via Load & Performance Testing. Captures the current state honestly, regardless of VMware vs Omnissa branding.

AVD target via 7-step wizard

The same `.lgs` scenario replays on AVD via the 7-step wizard: Tenant, Client, Resource, Classic/ARM toggle. Workload configuration captured at scenario level.

Cross-stack overlay

Multi-test overlay compares generic p95 on Horizon vs generic p95 on AVD on the same scenario shape. One chart, both stacks.

Multi-test overlay

Horizon vs AVD on one scrub bar.

Stack-honest comparison. The same `.lgs` scenario authored once, runs unmodified on Horizon and AVD. Generic p95 measured on each side, on the same scenario shape.

  • Same `.lgs` scenario authored once, runs unmodified on Horizon + AVD.
  • Up to 5 runs overlaid on one chart. Drill into Moments, Errors, per-step.
  • Generic p95 captured per transaction on each stack.
  • Same data drives cutover sign-off, a positioning/workflow motion on the same scenario engine.

Multi-test overlay. Horizon baseline vs AVD target.

How the engagement runs

Baseline → Author → Execute → Cutover.

Step 01

Baseline Horizon

Capture the current Horizon scenario shape on the generic wizard. Same engine, same `.lgs` artefact. The baseline against which AVD progress will be measured.

Step 02

Author AVD

Use the 7-step AVD wizard to spin up a pilot host pool. Tenant / Client / Resource and the Classic/ARM toggle captured inline.

Step 03

Execute side-by-side

Run the `.lgs` scenario against both stacks. The live cockpit overlays generic p95 on Horizon against generic p95 on AVD on one scrub bar.

Step 04

Compare and sign cutover

Promote users from Horizon to AVD with pilot, scale, and production cohorts. Each cohort re-runs the same scenario at growing scale. Roll back on data, not opinion.

Stack-honest comparison

Same workload, both stacks. What changes.

SignalHorizon (baseline)AVD (target)
WizardGeneric wizard7-step AVD wizard
MeasurementGeneric p95Generic p95
EngineSame scenario engineSame scenario engine
Profile modelPersona / instant cloneCaptured at scenario level
Capacity sizingHorizon at concurrency via L&PHost pool density via L&P
Agent fleetVDI agents (port 4841)VDI agents (port 4841)

Proof

Numbers from the platform.

1.45M+

Tests run

across the customer base

6

Platforms covered

Citrix · AVD · Horizon · RDS · Web · FAT

1×

Scenario authored

reused on both stacks

From €1,099

Per week · transparent

starts at 50 vUsers

See it in action

Three migration surfaces.

Migration cockpit

Baseline overlay across stacks.

AVD wizard

7-step wizard. Tenant · Client · Resource · Classic/ARM.

Run comparison

Horizon vs AVD overlay on one chart.

Where Horizon → AVD lives

Three migration patterns.

Full Horizon → AVD cutover

Baseline Horizon, build a pilot AVD pool, validate per cohort, cut over. Same scenario shape across the entire engagement.

See use case

Hybrid Horizon + AVD

Some workloads stay on Horizon, others move to AVD. Same engine monitors both. One Service Levels report, one cockpit.

See use case

Vendor consolidation review

For organisations evaluating Omnissa Horizon vs Azure-native AVD strategically, LoadGen captures both on the same scenario. Strategic decisions on measured data.

See use case

Plan your Horizon → AVD migration with data.

We’ll baseline your Horizon scenario in the generic wizard, build a pilot AVD pool against your subscription, and run the same workload across both. On a call.

Plan the Horizon → AVD migration with dataRead the migration checklist

Questions

Frequently asked.

Does the same scenario really run on both Horizon and AVD?

Yes. The same `.lgs` scenario authored once runs unmodified on both stacks. The cockpit overlays generic p95 on Horizon against generic p95 on AVD on the same scenario shape.

How does LoadGen handle the VMware → Omnissa rebrand?

LoadGen runs real Horizon sessions end-to-end through the generic wizard, regardless of console branding. The synthetic test is stack-honest about user experience, not vendor API state.

Is there a Horizon-dedicated wizard or vCenter integration?

No. Horizon runs through the generic wizard on the same scenario engine. LoadGen can load-test Horizon at concurrency through the same scenario engine via Load & Performance Testing, there is no separate Horizon wizard and no native vCenter integration.

What does Horizon → AVD migration testing engage with on the AVD side?

The 7-step AVD wizard captures Tenant, Client, Resource, and a Classic/ARM toggle. Workload behaviour is configured at scenario level. Generic p95 is captured per transaction on the live cockpit.

How long is a Horizon → AVD migration testing engagement?

The engagement begins with a baseline of Horizon and a pilot AVD pool, then promotes by cohort behind validation gates. Exact timeline depends on AVD scale and operational readiness. We’ll size it on the discovery call. LoadGen Services (consulting + managed runs) is available where in-house bandwidth is tight.

What does Horizon → AVD migration testing cost?

Load Testing is €1,099 per week at the 50-vUser tier; End-to-End Monitoring is €899 per Agent per month (annual subs include two months free). 25,000+ users have been tested by LoadGen, and LoadGen scales with available test infrastructure and agent capacity. Migration engagements typically combine both modules plus LoadGen Services for the cutover window.

LoadGen Official Logo