Transferring data to a new profile

From MozillaZine Knowledge Base
Revision as of 13:38, 4 September 2007 by Alice Wyman (talk | contribs) (Same format used in Browser and Mail section. Highlighted each filename since that is what is important. Placed related articles in a "See also" section)
Jump to navigationJump to search

This article describe how to do transfer selected user data and settings to a new user profile for your Mozilla application. See Transferring data to a new profile - Firefox and Transferring data to a new profile - Thunderbird for more detailed instructions for Firefox and Thunderbird.

Mozilla applications include a Profile Manager feature that allows you to create a new user profile, which can be useful when your Mozilla application is behaving badly, since the problem is often in the profile. Rather than attempt to find the problem, it's often easier to create a new profile and to transfer desired data from the old profile to the new one.

Copying data and settings

  • As a precaution, it is recommended that you make a copy of the profile folder before you make changes to it.
  • The Mozilla program must be closed before you attempt changes to the profile.
  • Do not copy the entire profile directory because some files only work in a specific directory, as noted below.
  • If you are transferring data to a new profile because you had problems with the old one, you should copy a few files at a time and test between steps. It is recommended that you only copy the data that you truly want in the new profile.

Browser files

These files are used by Firefox and Mozilla Suite / SeaMonkey.

  • 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.
  • 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.
  • 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]
  • 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.

  • 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.
  • abook.mab - Personal Address Book and history.mab - Collected Addresses. For migrating other address books, see this article.
  • cert8.db - Security certificates
  • 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