# Migrating from Selenium WebDriver to TestOwl

:::lead
Step-by-step guidance on importing and converting legacy Selenium WebDriver Java, Python, or JavaScript test suites into maintainable TestOwl tests.
:::

Selenium WebDriver has been the workhorse of automated testing for over a decade. However, maintaining custom Page Object models, managing local browser driver binaries, and constantly fixing broken XPaths creates significant engineering overhead.

## Migration Benefits

- **Zero Driver Configuration:** No need to manage `chromedriver`, `geckodriver`, or grid instances.
- **Autonomous Self-Healing:** Eliminate 95% of maintenance downtime caused by DOM and class changes.
- **Universal Collaboration:** Manual QA testers and product managers can view, edit, and expand tests visually without writing code.

## Step 1: Exporting Test Scenarios

Before using the Import Wizard, identify your high-value regression suites:
- Export your Page Object actions and test methods into structured test scenarios.
- List environment variables, test data sheets, and login credentials.

## Step 2: Running the Import Wizard

1. In TestOwl, click **Import** in the sidebar.
2. Select **Selenium WebDriver** as the source framework.
3. Upload your test project folder or repository archive (`.zip`).
4. TestOwl's parser analyzes your test classes, maps `By.id`, `By.cssSelector`, and `By.xpath` definitions into multi-attribute element fingerprints, and converts helper methods into reusable **Flows**.

## Step 3: Review and Verify Locators

Once imported, open your new Test Suites:
- Run the suite against your staging environment.
- Confirm that self-healing locators resolve successfully.
- Convert any hardcoded credentials into secure [Secrets](/docs/data/secrets).

Learn more in our [Import Wizard Overview](/docs/import-test-scripts/overview) or compare tools in our [Selenium Alternatives Guide](https://testowl.ai/selenium-alternatives).