Engine migration
Engine migration converts a profile from one browser engine to another — Firefox (Maskifox) to Chrome, or Chrome to Firefox — while preserving cookies and bookmarks.
What is migrated
| Data | Migrated? |
|---|---|
| Cookies | Yes |
| Bookmarks | Yes |
| Passwords | No |
| Extensions | No |
| Browsing history | No |
| Open tabs | No |
Only cookies and bookmarks carry over. Passwords, extensions, browsing history, and other browser data are not transferred.
Migrate a single profile
- In the Profiles list, open the three-dot row menu for the profile.
- The migrate option shows the target engine: Migrate to Chrome or Migrate to Firefox depending on the profile's current engine.
- Click the option.
- A confirmation dialog appears. It lists exactly what will and will not be carried over.
- Click Migrate to proceed.
You cannot migrate a running profile. The option is disabled for active profiles.
Migrate multiple profiles
- Select the profiles using the checkboxes (see Bulk actions).
- In the bulk toolbar, click the Chrome or Firefox engine button.
- Confirm in the dialog.
The migration runs per profile. When all are done:
- A success toast shows the total count of migrated profiles.
- If any failed, a warning toast groups failures by reason and names the affected profiles (up to 5 per group).
Skipped profiles
Profiles that are active on another team device are skipped and named in a warning toast. Stop those profiles before migrating them.
After migration
The profiles list reloads automatically. Each row's engine icon updates to reflect the new engine. The profile is ready to launch with the new engine immediately.
Reverting a migration
Run migration again in the opposite direction. Cookies and bookmarks that were present at the time of the original migration will carry back. Any cookies or bookmarks added in the new engine after migration are included in the reverse migration.