Transferring data to a new profile

From MozillaZine Knowledge Base
Jump to navigationJump to search

This article explains how to transfer your Mozilla application user data and settings to a new profile and includes a list of suggested files. This article does not apply to Firefox 3.

Firefox users should read Transferring data to a new profile - Firefox instead of this article, since it contains more detailed instructions and information about files specific to Firefox 3. Thunderbird users should read Transferring data to a new profile - Thunderbird for more detailed instructions.

Background

Mozilla applications store your user data in a profile folder, separate from the program. Normally, you only need a single profile, the original "default" profile that was created when you first installed your Mozilla application. You can transfer your data and settings to the "default" profile on another computer. You can also use the Profile Manager to create an additional user profile on the same computer and both profiles will be available. This can be useful when your Mozilla application is behaving badly, since most problems are in the profile and it's often easier to create a new profile and copy over desired data than to fix the problem in the original profile.

Copying data and settings

  • As a precaution, it is recommended that you make a profile backup to safeguard your important data, before making any changes.
  • The Mozilla program must be closed before you attempt changes to the profile.
  • Although in many cases it is possible to copy the entire contents of a profile to a new profile, it is recommended that you only copy the data that you truly want to keep.
  • If you are transferring data to a new profile because you had problems with the old one, copy a few files at a time and test between steps.

Browser files

These files are used by Firefox 2 (or prior) and Mozilla Suite/SeaMonkey 1.x. For Firefox 3, see Transferring data to a new profile - Firefox for an updated list of files and additional instructions.

  • cert8.db - Security certificate settings
  • cookies.txt - Cookies (Keeping cookies will keep you logged into websites that you were logged into before.)
  • formhistory.dat - Form history (Firefox) Autocomplete entries for web forms and the search bar.
  • (number).w - Form history (Mozilla Suite/SeaMonkey). If you do not migrate the "prefs.js" file, then use about:config to modify the wallet.SchemaValueFileName preference value to match the copied "(number).w" file name.
  • hostperm.1 - Permissions Cookie, image, and extension install permissions.
  • key3.db - Key database for passwords. To transfer saved passwords you must copy key3.db along with one of the following files.
    • signons.txt Saved passwords in Firefox 1.5.0.9 and below and Firefox 2.0.0.0, 2.0.0.1
    • signons2.txt - Saved passwords in Firefox 1.5.0.10 and 2.0.0.2 and above.
    • (number).s - Saved passwords in Mozilla Suite/SeaMonkey. If you do not copy the "prefs.js" file, you must first save a password in the new profile so that a "(number).s" file is created, then use about:config to modify the signon.SignonFileName preference value to match the copied file name [1]
  • prefs.js and, if it exists, user.js - Preferences. Important: Copying the "prefs.js" file from one profile to another is not recommended if you had problems with the previous profile. If you choose to transfer "prefs.js" to the new profile, you may need to edit the prefs.js file (or use about:config) to remove (or reset) preferences that point to invalid directories or preferences that refer to extensions that are not installed in the new profile.
  • searchplugins folder - Search engines.
  • extensions folder - Extensions and Themes (Firefox 1.5 or later only) Important: Copying this folder is not recommended if you had problems with the previous profile. It is also necessary to delete these three files at the same time: extensions.ini, extensions.cache and extensions.rdf (these files will be regenerated on restart). Note that this method will not move data that specific extensions may have saved in the profile.

Mail program files

These files are used by Thunderbird and Mozilla Suite/SeaMonkey Mail.

  • abook.mab - Personal Address Book and history.mab - Collected Addresses. For migrating other address books, see this article.
  • cert8.db - Security certificates
  • key3.db - Key database for passwords. To transfer saved passwords you must copy key3.db along with one of the following files.
    • (number).s - Saved passwords in Mozilla Suite and older Thunderbird profiles. If you do not migrate the "prefs.js" file, use about:config to modify the signon.SignonFileName preference value to match the copied "(number).s" file name.
    • signons.txt - Saved passwords in recent Thunderbird profiles.
  • popstate.dat (inside each POP mail account subfolder) - Keeps track of which messages have been downloaded from the POP server. If you don't copy it, previously downloaded messages still on the server might all get downloaded again.
  • prefs.js and, if it exists, user.js - Preferences and account settings. Copying the "prefs.js" file from one profile to another is not recommended if you had problems with the previous profile. If you choose to transfer "prefs.js" to the new profile, you may need to edit the prefs.js file (or use about:config) to remove (or reset) preferences that point to invalid directories or preferences that refer to extensions that are not installed in the new profile.
  • virtualfolders.dat (Thunderbird) - Saved Search folder settings
  • Mail and ImapMail folders - E-mail messages and settings. See this article.
  • News folder - Newsgroups messages and settings. If necessary, create a new "newsgroup" account for each news server in the new profile ("File -> New -> Account"), then close Mozilla Suite or Thunderbird and copy over the "News" folder contents.
  • extensions folder - Themes and Extensions (Thunderbird 1.5 or later only). Important: Copying this folder is not recommended if you had problems with the previous profile. It is also necessary to delete these three files at the same time: extensions.ini, extensions.cache and extensions.rdf (these files will be regenerated on restart).

See also