QA/Firefox migrators
Migrator Overview
Supported data types
| Data Type | 360se | Chrome/Chromium/Canary/Edge | Legacy Edge | Firefox (Refresh) | Internet Explorer | Safari |
|---|---|---|---|---|---|---|
| Bookmarks | Yes | Yes | Firefox 41+ | Yes | Yes | Not smoothly on modern macOS |
| Cookies | No | Only unencrypted (bug 1163165, bug 1163166, bug 1163167 ) | Firefox 41+ | Yes | Yes | No (bug 712240) |
| Form History | No | No | No | Yes | No | Only search history (bug 363488) |
| Form Autofill | No | No | No | Yes | No | No |
| History | No | Yes | Only typed URL history, Firefox 44+ | Yes | Yes | Not smoothly on modern macOS |
| Passwords | No | macOS (since Fx71) and Windows | Firefox 42+ (bug 1192035) | Yes | Form passwords up to Win7 (43+) Win8+ (42+, bug 1192035), not HTTP Auth. (bug 1191175) | No (bug 1018667) |
| Session | No | No | No | Yes | No | No |
| Settings | No | No | No (WONTFIX) | No. This is intentional so Refresh can fix problems. | Yes | Yes |
| Other Data | No: Address and Credit Card Autofill | Reading List (42+) | Bookmark Backups, Personal Dictionary, FHR Data, Sync login | Search history |
- Homepage import was removed in bug 1434167 (Firefox 60)
Common issues affecting most browsers
- Favicons aren't imported (e.g. bug 718220 & bug 711995)
- Imports may fail if the source browser/profile is running (e.g. bug 706005 & bug 715315)
Differences between official and unofficial builds
Homepage import (Only appears in official builds)- Removed in bug 1434167
Differences between startup and later migrations
Startup migration happens when a user has no profiles.ini (i.e. no profiles) and they see the migrator automatically during startup (possibly only in official builds?). It can also be triggered with the -migration command-line argument. Migration can be accessed for existing profiles from the Places window (bookmark/history manager) from the last toolbar button => Import Data from Another Browser
- Non-toolbar bookmarks are imported at the top level for startup migration but in a sub-folder with the browser's name afterwards.
- The data selection page is skipped during startup migration and all data for the specific browser is chosen.
- The system default browser should be first and initially selected during startup migration.
IE migrator
Summary
The feature's goal is to migrate data and settings safely from Internet Explorer to Firefox.
Reference
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1
Test Cases
- A list of test cases for this feature can be found here: Test Cases
Edge migrator
Summary
The feature's goal is to migrate data and settings safely from Microsoft Edge (Project Spartan) to Firefox.
- Meta bug: bug 1163644.
Reference
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1
Test Cases
Chrome migrator
Summary
The feature's goal is to migrate data and settings safely from Google Chrome, Chromium and Chrome Canary (except Canary on Linux) to Firefox. The new Microsoft Edge is also included.
- Other Chromium-based browsers like Opera (bug 707601), Brave, and Yandex aren't yet supported.
Reference
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1
Test Cases
- A list of test cases for this feature can be found here: Test Cases
Safari migrator
Summary
The feature's goal is to migrate data and settings safely from Safari to Firefox.
Reference
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1
Test Cases
- A list of test cases for this feature can be found here.
Firefox migrator
Summary
It is used by the reset/refresh profile feature from about:support and a notification bar if a profile hasn't been used in 60 days. It's not shown in the list of migrators at this time as it's meant for Refresh scenarios. It only supports migrating from the default Firefox profile to a new one.
Reference
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1
Test Cases
- A list of test cases for this feature can be found here: Test Cases