Migrate Experiments from VWO to Convert Using the Chrome Extension
VWO → Convert Migration via Chrome Extension
THIS ARTICLE WILL HELP YOU:
- Get an Overview
- With Pre-requisites
- Understand How VWO Items Map to Convert
- Know Steps to Migrate Your VWO Experiments
- Understand What the Migration Tool Copies
- Know Partially Supported Visual Changes
- Know What Is Not Migrated
- Review Your Migrated Experiences
- QA the Migrated Experience
- Troubleshoot
- Frequently Asked Questions
- Seek Help
Overview
The VWO Migration Tool is available through the Convert Chrome extension. It helps you move experiment configurations from VWO into Convert Experiences without having to recreate every item manually.
The tool can read and migrate supported VWO:
- Hypotheses
- A/B tests
- Personalizations
- Multivariate tests
- Split URL tests
The migration tool copies as much compatible configuration as possible and creates the corresponding items in your selected Convert project.
All migrated Experiences are created with Draft status. They will not begin serving traffic until you review, QA, and activate them.
The tool does not modify or delete anything in your VWO account.
⚠️ Important:
The migration tool transfers experiment configuration, not historical results or report data.
Before You Begin
Make sure you meet the following requirements.
Browser and extension
You must:
- Use Google Chrome
- Install and enable the Convert Chrome extension
- Keep the extension updated to its latest available version
The Convert extension also provides tools for experiment development, testing, and troubleshooting.
Source: Chrome Debugger Extension For Convert Experiences
VWO access
You must:
- Have access to the VWO account containing the items you want to migrate
- Be logged in to VWO in the same Chrome browser profile
- Be able to open the relevant campaigns and experiment configurations
Convert access
You must:
- Be logged in to your Convert account
- Have Editor or Administrator access to the destination project
- Know which Convert project should receive the imported Experiences
Convert tracking code
The Convert tracking code should be installed on the website where the migrated Experiences will run.
This is required to properly preview, QA, and eventually activate the Experiences.
How VWO Items Map to Convert
During migration, VWO concepts are translated into their closest Convert equivalents.
| In VWO | In Convert |
|---|---|
| Campaign or test | Experience |
| A/B test | A/B Experience |
| Split URL test | Split URL Experience |
| Personalization | Personalization or the closest supported Experience type |
| Variation | Variation |
| Original | Original variation or control |
| Page or URL targeting | Locations |
| Goal | Goal |
| Audience or segment | Audience |
| Variation traffic allocation | Variation traffic distribution |
| Campaign status | The migrated Experience is created as Draft |
Some advanced settings may not have an exact one-to-one equivalent. Review every imported item before activation.
Migrate Your VWO Experiments
Step 1: Log in to VWO
Open VWO in Google Chrome and log in to the account containing the experiments you want to migrate.
Make sure you can access the relevant hypotheses, campaigns, and experiment configurations.
Step 2: Log in to Convert
In another tab within the same Chrome browser profile:
- Log in to Convert.
- Open the account containing your destination project.
- Confirm that you have permission to create Experiences in that project.
Step 3: Open the migration tool
- Click the Convert extension icon in the Chrome toolbar.
- Open the VWO Migration section.
- Allow the extension to load the available information from your VWO account.
The extension will display the supported hypotheses, tests, and campaigns available for migration.
Step 4: Review the available items
The migration list may display information such as:
- Name
- VWO ID
- Experiment type
- Current VWO status
- Import status
Items that have already been imported into the selected Convert project appear disabled with a green checkmark.
These items cannot be imported into the same project again through the migration tool.
Step 5: Select a Convert project
Choose the Convert project where the migrated Experiences should be created.
Review the selected project carefully before starting. The project determines where the imported Locations, Goals, Experiences, and related configurations will be created.
Step 6: Select the items to migrate
Select one or more supported VWO items from the list.
The migration tool will attempt to copy the complete supported setup for each selected item. The original VWO status is not carried over; migrated Convert Experiences are always created as Drafts.
Step 7: Start the migration
Click Start Migration.
Do not close the extension popup while migration is running.
Until the migration finishes:
- Do not click outside the extension popup
- Do not press the Esc key
- Do not close the popup
- Do not refresh or close the relevant browser tabs
Closing the popup before completion interrupts the migration process.
Step 8: Confirm completion
When the migration finishes successfully, the extension displays a confirmation message.
Open your selected Convert project and locate the newly created items.
The migrated Experiences should appear with:
- Draft status
- The closest supported Convert Experience type
- Original and variation names based on the VWO setup
- Migrated configuration where a compatible Convert equivalent exists
What the Migration Tool Copies
The tool is designed to transfer as much compatible setup as possible.
Depending on the VWO configuration, migrated information may include:
- Hypotheses
- Campaign or test names
- A/B test configurations
- Split URL test configurations
- Multivariate test configurations
- Personalizations
- Deploy-type configurations
- Primary URLs
- Locations
- Domains
- Variations and variation names
- Visual and HTML changes
- Pageview goals
- Click goals
- Variation traffic distribution
- Other supported targeting and experiment settings
Partially Supported Visual Changes
Visual changes generated through AI-based editing may be copied completely or only partially.
Because VWO and Convert may represent these changes differently, some AI-generated edits cannot always be translated exactly.
After migration, open every variation and confirm that:
- The intended elements have changed
- The correct content is displayed
- CSS selectors still match the page
- The page behaves as expected across relevant devices
What Is Not Migrated
The following items are not transferred automatically:
- Historical experiment results
- Past reports
- Visitor or conversion history
- Heatmaps
- Session recordings
- Surveys
- VWO-specific add-ons
- Integrations such as Google Analytics or Segment
- Advanced audience rules without a compatible Convert equivalent
- Custom JavaScript that depends on VWO-specific APIs
- Unsupported or highly customized goals and targeting conditions
These items must be reviewed and, where needed, recreated in Convert.
Review Your Migrated Experiences
Migration is intended to save setup time. It is not a replacement for QA.
Before activating a migrated Experience, review the following areas.
Experience type
Confirm that the selected Convert Experience type correctly reflects the original VWO setup.
Locations
Compare the migrated Locations with the URL-targeting rules used in VWO.
URL patterns and targeting structures may not map exactly between platforms.
Audiences
Review all audience conditions and recreate any advanced conditions that could not be transferred.
Variations
Check every variation in the Visual Editor or Code Editor.
Confirm that:
- The visual changes are correct
- The variation code is complete
- The selectors still identify the intended page elements
- The variation behaves correctly on the live website
When adjusting migrated selectors, use the shortest selector that remains reliable and uniquely identifies the intended element.
Goals
Confirm that each required conversion action has a corresponding Convert Goal.
Click goals are supported where they can be mapped, but selectors may need adjustment. Advanced or custom goal types may need to be created manually.
Traffic distribution
Review the traffic distribution assigned to the Experience and each variation.
Custom code
Inspect any migrated JavaScript or CSS.
VWO-specific JavaScript methods and APIs will not work automatically in Convert and must be rewritten using standard browser code or Convert-compatible functionality.
QA the Migrated Experience
All migrated Experiences are created as Drafts so they can be tested safely before launch.
Use Convert’s QA tools to verify:
- The tracking code loads correctly
- The Experience triggers on the intended pages
- Audience conditions work as expected
- Each variation displays correctly
- Goals trigger when the expected actions occur
- No JavaScript errors appear
- The Experience works across relevant browsers and devices
Convert’s QA Overlay can be used to preview Experiences, select variations and audiences, inspect goals, and review live activity before activation.
Source: QA Overlay Widget User Guide
After QA is complete, activate the Experience when you are ready to begin collecting new data in Convert.
Troubleshooting
No VWO items appear
Confirm that:
- You are logged in to VWO
- You are using the same Chrome browser profile for VWO and Convert
- Your VWO account has access to the campaigns
- The Convert extension is installed and enabled
- The extension has finished loading the available VWO data
Reload VWO and reopen the extension if necessary.
An item is disabled with a green checkmark
This means the item has already been imported into the selected Convert project.
Previously imported items cannot be imported into that same project again through the tool.
Convert authentication error
Confirm that:
- You are logged in to Convert
- Your Convert session has not expired
- You have Editor or Administrator access to the selected project
Logging out of Convert and signing in again may refresh the authentication session.
The migration does not complete
The migration can be interrupted when the extension popup closes before processing finishes.
Run the migration again and keep the popup open until the confirmation message appears.
Also disable browser extensions that may interfere with:
- Network requests
- Cookies
- Browser storage
- Website permissions
- API calls
This includes ad blockers, privacy extensions, network-modifying extensions, and security tools that block browser requests.
You may also test the migration in a clean Chrome profile where no other extensions are installed.
A migrated variation does not look correct
Differences between the VWO editor, the Convert editor, and the current website DOM can affect migrated changes.
Open the variation in Convert and:
- Check the affected elements.
- Review the CSS selectors.
- Reapply incomplete visual changes.
- Correct migrated CSS or JavaScript.
- Test the variation on the live page.
A goal is missing or incomplete
The migration tool supports goals that can be mapped to a compatible Convert goal type, including click goals.
Advanced, custom, or unsupported goals may need to be created manually.
Compare the original VWO goal configuration with the migrated Convert Goals before activating the Experience.
The targeting is different
VWO and Convert do not represent every targeting rule in exactly the same way.
Compare:
- VWO URL targeting with Convert Locations
- VWO segments with Convert Audiences
- Device and visitor conditions
- Custom JavaScript conditions
- Included and excluded URLs
Adjust the Convert configuration so it matches the intent of the original experiment.
Frequently Asked Questions
Does the migration tool change anything in VWO?
No. The tool reads supported VWO configurations and creates corresponding items in Convert. It does not modify, pause, or delete anything in VWO.
Will my historical VWO results be migrated?
No. Historical results, reports, visitor data, and conversion data are not migrated. Data collection in Convert begins after you activate the migrated Experience.
Are migrated Experiences activated automatically?
No. Every migrated Experience is created with Draft status. You must review, QA, and activate it manually.
Can I migrate more than one VWO test at a time?
Yes. You can select multiple supported items before starting the migration. Keep the extension popup open until the complete migration process finishes.
Can the same test be imported twice?
An item that has already been imported into the selected project appears disabled with a green checkmark and cannot be imported into that project again through the tool.
Will every VWO configuration transfer exactly?
Not always. The tool transfers as much compatible information as possible, but advanced targeting, custom goals, AI-generated visual changes, integrations, and VWO-specific JavaScript may require manual review or recreation.
Should I QA migrated Experiences?
Yes. Treat every migrated Experience as you would an Experience created manually.
Review the entire setup and complete a full QA process before activating it.
Need Help?
When contacting Convert Support about a migration issue, include:
- Your Convert account and project
- The name or ID of the VWO item
- Your browser and operating system
- A screenshot or screen recording
- A description of the step where the issue occurred
- Any error message displayed by the extension
These details will help the Support team investigate the issue more efficiently.