Cut over with measured confidence, not a status meeting.
LoadGen turns Citrix → AVD migrations into a measured engineering practice — same scenario shape, same engine, side-by-side validation. Every wave is a measurement, every gate is data.
Citrix → AVD · Migration Plan
Source baseline · target validation · wave readiness.
The Problem
Migrations don’t fail at cutover. They fail at assumption.
The questions an infrastructure lead has to answer before promoting Wave 3 don’t come from a vendor brochure — they come from running the same scenario on both stacks.
Migration plans built on slides, not measurements.
A roadmap that says "Q3: cut over Finance" without a Citrix baseline isn’t a plan — it’s a gamble with 312 SAP users on the table.
AVD pilots that pass — and prod regressions that don’t.
A 50-user pilot proves nothing about a 1,500-user finance close. Without parity testing, the regression surfaces on cutover weekend.
No sign-off evidence after the cutover.
Migration is "done" only when leadership has the data to confirm it. Without continuous validation, you ship the move and inherit the doubt.
How LoadGen solves this
Assess · Baseline · Migrate · Validate.
Four motions running in parallel across waves — not a Gantt chart of phases that wait on each other.
Assess
Audit users, app groups, and dependencies. Stack-rank waves by risk and value. Use the Citrix wizard to capture session counts and HDX/ICA telemetry.
Baseline
Run the Citrix wizard scenario at production load. Capture P95 latency, throughput, error rate. Save the comparison anchor.
Migrate
Run the AVD wizard with the same scenario shape. Right-size host pools per wave. Validate before promoting users.
Validate
Overlay Citrix baseline against AVD result. Pass or fail the wave on measured envelope, not on a slide.
Live · Migration Plan
The wave plan, the validation gate, on one surface.
The migration cockpit shows every wave, every app group, every user count — and runs the Citrix-vs-AVD comparison gate on each one. Promote when the gate passes; investigate when it doesn’t.
Outcomes · before / after
Move 4× faster. Inherit 91 % fewer incidents.
Drawn from teams that adopted parity testing as the wave promotion gate for their Citrix → AVD program.
Before
11
After
1
Before
6 days
After
4 hrs
Before
120
After
480
Before
38 %
After
4 %
Migration → Platform
Five features. One migration practice.
Migration isn’t a feature — it’s the way these five compose into a wave-by-wave evidence loop.
- /config/load-profiles/new/citrix— Citrix baseline wizard
- /config/load-profiles/new/wvd— AVD target wizard
- /testing/run— Parallel & sequential execution
- /testing/results— Multi-test overlay
- /monitoring/profiles— Post-migration UX validation
Load Profile Wizard
Citrix and AVD wizards side-by-side — same scenario shape, platform-specific tuning.
/features/load-profile-wizard
Agents
Right-sized agents — Full for Citrix sessions, VDI for AVD pools — no scripts, no toolchain swap.
/features/agents
SUT Monitoring
Bind infra counters to every wave so capacity correlates with broker, host pool, and FSLogix health.
/features/sut-monitoring
Sync
GitOps for migration scenarios — version every wave config, diff before promoting.
/features/sync
Analytics & AI
AI-flagged regressions overlay Citrix vs AVD automatically — no analyst hours per wave.
/products/analytics-ai
Migrate on data. Sign off on evidence.
Run your Citrix baseline this week. Run the AVD scenario next week. Promote Wave 3 the week after with the kind of confidence that doesn’t need a status meeting.
