Migrate from VWO. Step by step.
Written by the ABTestly team. ABTestly pricing verified on our own pricing page on 6 August 2026. VWO details checked on vwo.com/pricing in August 2026. VWO's public page does not list a 100,000 tracked user price, so ask VWO for a current quote. Check their site for current information.
Yes, we are ABTestly, so read this knowing who wrote it. Every step and number here is checkable. Most VWO A/B testing setups move over in an afternoon or two. Swap one snippet, rebuild your live experiments, goals, and targeting, and validate your tracking in ABTestly before you move traffic or cancel anything. Migration help is free and human.
What carries over, and what does not
ABTestly is focused A/B testing, not a full CRO suite. So some of VWO maps across cleanly and some does not. Here is the honest mapping before you start.
| In VWO | In ABTestly | |
|---|---|---|
| Experiments | A/B, split URL, multivariate, multi arm, personalization campaigns | Rebuilt as A/B experiments. Multivariate and personalization do not carry across, since ABTestly is A/B testing focused |
| Variant changes | Built in the visual editor, stored as generated selectors and CSS | Re authored as variation code in Monaco. The change becomes explicit, diffable, and version controlled |
| Goals and metrics | Conversion goals, revenue, engagement metrics | Recreated as goals. Two system goals attach to every new experiment automatically. Conversion and revenue are both supported |
| Audience and targeting | URL, device, geo, cookie, behavioral, and custom JavaScript conditions | Recreated as targeting rules: URL, device, and query parameters. URL rules are case insensitive by default. More specific VWO conditions may map to a custom rule, and we will help you check |
| Statistics | SmartStats Bayesian, with a frequentist option | Three statistics engines (Frequentist on every plan; Sequential and Bayesian on Pro), applied to conversion and revenue |
| Historical reports | Live inside VWO's reporting | Export them before you cancel. Past results stay yours. New data starts fresh in ABTestly |
| Heatmaps, recordings, surveys | Part of the VWO suite | Not offered. Keep a dedicated tool if your program relies on these |
The migration, step by step
1. Inventory what you actually run (30 min). List active campaigns, goals, and targeting rules in VWO. Most accounts find a handful of live A/B tests and a long tail of paused ones. Flag anything that is multivariate, personalization, or heatmap driven, because that is the part that will not move across as is. You are migrating less than you think.
2. Create your ABTestly site and install the snippet (15 min). Sign up free, add your site, and paste the loader into your <head>. The loader is a few lines. It pulls the full runtime, about 27 KB gzipped, measured on our own snippet. Anti flicker is opt in, so you turn it on only for the tests that hide content above the fold.
1<!-- ABTestly · paste first in <head> --> 2<script>(function (w, d) { 3 var s = d.createElement('script'); 4 s.src = 'https://cdn.abtestly.com/s/YOUR_KEY.js'; 5 s.async = false; 6 (d.head || d.documentElement).appendChild(s); 7})(window, document);</script>
The install guide has the exact snippet your site generates, and the consent guide covers wiring it to your CMP if you operate under GDPR.
3. Rebuild one experiment as a pilot (30 to 60 min). Pick your simplest live A/B concept. You build the experiment in the dashboard: variants, their split, targeting, and goals. Each variation is code you write in Monaco, so the change lives in version control if you want it to. The config below is illustrative and shows the shape ABTestly compiles; the exact flow is in the build docs.
1// The dashboard builds this. Each variation is code you write. 2{ 3 "key": "hero-cta", 4 "variants": [ 5 { "name": "control", "weight": 5000 }, // basis points, 5000 = 50% 6 { "name": "b", "weight": 5000 } 7 ], 8 "goals": [ { "key": "signup_click", "isPrimary": true } ] 9}
Where VWO recorded your visual edits as generated selectors, you write the change as variation code in Monaco. It is a few lines, and it says exactly what it does.
1// Variant B: rewrite the hero CTA 2var cta = document.querySelector('.hero .btn-primary'); 3if (cta) { 4 cta.textContent = 'Start free'; 5 cta.dataset.variant = 'b'; 6}
Attach goals, set targeting, and use preview links to QA each variant on your live site before you launch.
4. Validate your tracking before you move traffic (passive). This is the step that de risks the switch, and it is not a race between two live tests. Run the same change in both tools at once and some visitors land in both, some in neither, and two scripts fight over the same elements, so the conversion numbers stop meaning anything. Prove the instrumentation first, without letting two tools touch the same visitor. Install ABTestly as a tracking only experiment that changes nothing on the page, or carve out a mutually exclusive slice of traffic, and confirm the plumbing:
- Eligibility. The visitors you expect to qualify actually qualify, under the same URL, device, and audience rules.
- Consent. Exposure fires only after consent, the way your CMP is wired.
- Exposure. ABTestly records an exposure when you expect one, deduped per visitor, with no sample ratio warning on the results panel.
- Goals. Each goal fires on the same action you defined in VWO.
Once the tracking checks out, launch one real low risk test in ABTestly. Do not expect the two tools' conversion rates to line up to the decimal. Different identity, attribution, consent, and goal definitions can move the numbers for legitimate reasons, so treat this as a plumbing check, not a numbers match. If something looks off, send us both setups and we will find out why before you have committed to anything.
5. Move the rest and cancel (1 to 2 hours). Rebuild the remaining A/B tests, export your VWO history, and cancel. VWO's public page does not publish a 100,000 tracked user price, and its plans commonly run on annual terms, so start this validation a few weeks before renewal and the overlap costs you nothing extra.
Honest effort estimate
| Setup | Expected effort |
|---|---|
| A handful of simple A/B tests, code editor based | Half a day plus the validation week |
| 5 to 10 tests with custom goals and audiences | 1 to 2 days plus the validation week |
| Heavy visual editor usage, multivariate, or personalization | 2 to 4 days. Visual editor changes must be re expressed as code, and multivariate or personalization campaigns need rethinking as A/B tests. Weigh whether code first suits your team before you start (the vs page covers this). |
Where VWO genuinely wins
Honesty matters more to us than the sale, so here is where staying on VWO, or picking it over us, is the right call.
- Breadth of CRO. Heatmaps, session recordings, surveys, funnels, and personalization under one login. If your program uses more than experiments, VWO does more.
- Visual editor for marketers. A page owner can build and QA a variant without a developer. ABTestly is code first, so this is the biggest thing you give up.
- Multivariate and feature experimentation. VWO offers both on higher tiers. ABTestly does neither.
- Integrations and enterprise features. A wide catalog of one tag integrations, SSO, phone support, and formal compliance certifications.
- Vendor maturity. An established company with a large customer base and agency ecosystem. For context, VWO and AB Tasty announced a combination in January 2026, supported by Everstone Capital. Worth knowing when you plan for the long term.
If none of those are blockers, the rest of this guide is the practical path across.
We will do it with you
Migration help is free and human. Send us a screenshot of your VWO campaign list at [email protected] and we will map every A/B campaign, goal, and targeting rule to its ABTestly equivalent, and tell you honestly which parts do not carry across, before you commit to anything.
Start the free pilot: app.abtestly.com/sign-up. Free plan, no card, 1 experiment and 3,000 tracked users, exactly enough for step 3.
What the switch is worth
At 100,000 tracked users, ABTestly Pro is $249 / mo, or $199 / mo billed annually, with unlimited experiments. We publish that price. VWO does not publish a 100,000 tracked user price on its public page, so there is no clean like for like figure to set beside it, and the two products cover different scope anyway. The honest comparison is your own VWO renewal quote, for the scope you actually use, against ABTestly's published plan. Full pricing is on the pricing page, and the VWO vs ABTestly comparison lays out the trade offs. Not sure yet whether to switch at all? Start with the VWO alternative page.
ABTestly prices are billed via Paddle as merchant of record; applicable tax is handled at checkout. VWO's public tiers cover different tracked user volumes, so compare by tracked users and by the features you actually use, not by a single list line.
VWO figures checked on vwo.com/pricing in August 2026. VWO does not publish a 100,000 tracked user price on its public page, so ask VWO for a current quote rather than trusting a number from us. ABTestly is not affiliated with Wingify Software (VWO).
Common questions
How long does a VWO migration take?
For a focused VWO A/B account, about half a day of work plus a short tracking validation step. Budget more if you lean on the visual editor, multivariate, or personalization, since those are re authored as code or do not carry across at all.
Does anything import automatically from VWO?
No. You rebuild your live A/B tests, goals, and targeting, and visual editor changes are re authored as variation code. Send your VWO campaign list to [email protected] and we map every A/B test, goal, and rule for you, and say plainly what does not carry across.
How do I confirm ABTestly is tracking correctly before I switch?
Validate the tracking before you move traffic. Install ABTestly as a tracking only experiment that changes nothing on the page, or use mutually exclusive audiences so no visitor is ever in both tools, and check that eligibility, consent, exposure, and goal definitions match what you expect. Then launch one real low risk test. Do not run the same live test in both tools at once, and do not expect the two tools' conversion rates to match to the decimal.
How much is ABTestly at 100,000 tracked users?
Pro is $249 / mo, or $199 / mo billed annually, for 100,000 monthly tracked users with unlimited experiments. VWO does not publish a comparable public price, so compare your own VWO quote and the scope you use against ABTestly's published plan.
Sources checked
Checked on 7 August 2026. Prices and product behaviour change, so verify against the source before you rely on a number.
- ABTestly pricing: abtestly.com/pricing
- Install snippet and size: docs.abtestly.com/install/snippet
- Statistics engines: docs.abtestly.com/results/engines
- Sample ratio guard: docs.abtestly.com/results/srm
- Refund terms: docs.abtestly.com/billing/refunds
- VWO pricing: vwo.com/pricing
- VWO and AB Tasty combination announcement: abtasty.com/news/vwo-ab-tasty-join-forces