SquareX to Legba: a step-by-step migration guide

A SquareX to Legba migration is not one-to-one. Start with the job you need to preserve. Then choose the Legba mode that performs that job. A familiar label proves nothing about other controls.

Legba has 2 public product paths. The Chrome extension provides Ghost and Shield. The agent skill exposes routing and isolation for browser steps. This guide maps only those verified jobs.

The migration plan

1. 01

   Write down the jobs you use

   List the workflows you need to keep. Separate private browser routing, off-device page execution, agent browser steps, and organization controls. This prevents a product-name comparison from hiding a missing requirement.

2. 02

   Install Legba and choose one mode

   Add the Legba Chrome extension. Choose Ghost for a private browser route. Choose Shield for off-device page isolation. Test one job at a time.

3. 03

   Verify the real workflow

   Use a non-sensitive page that represents your normal work. Confirm the selected mode performs the job you wrote down. Record missing behavior before changing your setup.

4. 04

   Retire the old path last

   Keep the old path during testing when available. Remove it after the matched jobs pass. Assign every unmatched requirement an owner. Managed environments need a separate control review.

Map the job, not the label

These are the direct Legba paths this guide can verify. The table does not claim that the products share the same architecture, settings, or administrative controls.

Review unmatched enterprise controls separately

Do not assume a browser mode replaces enterprise controls. Your SquareX deployment may include other requirements. Examples include managed rollout, policy enforcement, reporting, identity integration, file controls, support terms, and data handling. Keep each item as a separate acceptance test.

Request current documentation for every required control. Get written answers for anything unclear. Mark unknowns as unknown. Test each replacement in your own environment.

A concise verification checklist

• Write one expected outcome for each workflow.
• Test Ghost with a representative browser-routing job.
• Confirm other apps keep their normal connection.
• Test Shield with a non-sensitive page.
• Confirm the page opens and remains usable through Shield.
• Test the agent skill only on a bounded browser step.
• Record unmatched controls and assign an owner.
• Keep the old path until required tests pass.

This checklist proves only the tested workflow. Treat every other property as a separate requirement.

Price and support

The published extension price is $10 a month, or $100 a year. Free for 30 days. No card required. These terms do not imply feature parity.

For an unmapped job, email support@legba.app. Include the workflow and expected outcome. List every control your organization needs. Treat unanswered requirements as open migration items.

Continue your evaluation

Read the current product comparison in Legba vs SquareX. Review the post-acquisition context in SquareX vs Zscaler vs Legba. Then read how Legba browser isolation works. The SquareX alternatives page provides another category-level view.