MozillaZine

Transferring data to a new profile

From MozillaZine Knowledge Base

(Difference between revisions)
Revision as of 02:32, 30 May 2007
Alice Wyman (Talk | contribs)
(reworded intro to allow for the fact that the user may have already created a new profile before coming to this article)
<-- Previous diff
Revision as of 19:43, 28 June 2007
Np (Talk | contribs)
(major rework)
Next diff -->
Line 3: Line 3:
Mozilla applications include a feature that allows you to create a new user [[Profile folder |profile]]. A new profile is 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. This article describes how to accomplish this. Other articles exist for other situations: [[Migrate from Mozilla Suite or Netscape to Thunderbird]], [[Migrate from Thunderbird to Mozilla Suite]], [[Combining two profiles]], [[Moving your profile folder]]. Mozilla applications include a feature that allows you to create a new user [[Profile folder |profile]]. A new profile is 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. This article describes how to accomplish this. Other articles exist for other situations: [[Migrate from Mozilla Suite or Netscape to Thunderbird]], [[Migrate from Thunderbird to Mozilla Suite]], [[Combining two profiles]], [[Moving your profile folder]].
 +==Setting up==
Your first step is to create the new profile, if you haven't done so already. To do this, [[Kill application |completely close the application]] by choosing File -> Exit (or Quit). Next, [[Profile Manager#Accessing_the_Profile_Manager | start the Profile Manager]] for your Mozilla application and create a new profile. Make note of the name you give to the new profile so you can distinguish between the old and the new. Your first step is to create the new profile, if you haven't done so already. To do this, [[Kill application |completely close the application]] by choosing File -> Exit (or Quit). Next, [[Profile Manager#Accessing_the_Profile_Manager | start the Profile Manager]] for your Mozilla application and create a new profile. Make note of the name you give to the new profile so you can distinguish between the old and the new.
-With the application closed again, copy the files you want to retain from the old [[profile folder]] to the new. This process will overwrite existing files of the same name so you may wish to [[Profile_backup | back up the profile]] where you are copying data, as a precaution.+You may want to [[Profile_backup | back up the old profile]] as a precaution.
-Below is a list of recommended files to copy. Do not copy the entire profile directory because some files may contain absolute path information and may cause problems when moved to a different location. 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.+==Copying settings==
 +Do not copy the entire profile directory because some files only work in a specific directory. 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.
-==Browser==+With the application closed again, copy the files you want to retain from the old [[profile folder]] to the new. A list of files needed for each type of user data is provided below; it's recommended you only copy the data that you truly want in the new profile.
-''These files are used by Firefox and [[Mozilla Suite |Mozilla Suite / SeaMonkey]].''+
-* <tt>[[bookmarks.html]]</tt> - Bookmarks+===Add-ons===
-* <tt>cert8.db</tt> - Security certificates+* <tt>extensions</tt> folder (Firefox 1.5 and later). After transferring this data, also delete '''extensions.ini''', '''extensions.cache''' and '''extensions.rdf''' from the new profile. This method will not move data that specific extensions may have saved in the profile.
-* <tt>chrome/[[userChrome.css]]</tt> and <tt>chrome/[[userContent.css]]</tt> (if they exist) - User-defined styles. It is '''not''' recommended to migrate these files if you had problems with the previous profile.+
-* <tt>[[cookies.txt]]</tt> - Cookies +
-* <tt>formhistory.dat</tt> ''(Firefox)'' - Form history+
-* <tt>[[key3.db]]</tt> stores the key (Master Password) to encrypt and decrypt the user names and passwords saved in "signons.txt" ''(Firefox)'' or "(number).s" ''(Mozilla Suite)''.+
-*<tt>[[signons.txt]]</tt> or <tt>[[signons2.txt]]</tt> ''(Firefox)'' - Saved passwords. '''Important:''' You also need to copy '''key3.db'''. +
-*<tt> (number).s</tt> ''(Mozilla Suite)'' - Saved passwords. If you do not migrate 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 [http://seamonkey.ilias.ca/profilefaq/#transferring_passwords]. '''Important:''' You also need to copy '''key3.db'''.+
-* <tt>(number).w</tt> ''(Mozilla Suite)'' - Form history. 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. +
-* <tt>[[history.dat]]</tt> - Browsing history +
-* <tt>[[hostperm.1]]</tt> - Cookie, image, and extension install permissions+
-* <tt>[[mimeTypes.rdf]]</tt> - Actions to perform on downloaded files+
-* <tt>[[User.js file|user.js]]</tt> (if it exists) and <tt>[[Prefs.js file|prefs.js]]</tt> - User Preferences. In most cases, migrating the "prefs.js" file from one profile to another is '''not''' recommended, especially if you had problems with the previous profile. If you choose to migrate "prefs.js", you may need to manually edit the paths to reflect the new profile location. You may also need to edit the file to remove preferences that refer to extensions that are not installed in the new profile.+
-* <tt>searchplugins</tt> folder - Search plugins. Copy the .src and .gif/.png pair of files (or, in Firefox 2, the .xml file) for each search plugin, from the "searchplugins" folder in the source directory to the destination "searchplugins" folder. In Firefox 1.5 or later and in SeaMonkey, newly-installed search plugins are added to the "searchplugins" folder in the [[profile folder]] instead of to the [[installation directory]]. Starting in Firefox 2, a single .xml file is used (instead of .src and .gif/.png files) for each search plugin.+
-* <tt>extensions</tt> folder ''(Firefox)'' - Themes and Extensions. '''Important:''' 1) Only copy this folder in Firefox 1.5 or later. 2) 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). 3) Migrating this folder is '''not''' recommended if you had problems with the previous profile.+
-==Mail and newsgroups==+===Browsing history===
 +* <tt>[[history.dat]]</tt>
 + 
 +===Bookmarks===
 +* <tt>[[bookmarks.html]]</tt>
 + 
 +===Cookies===
 +Keeping cookies will keep you logged in to websites that you were logged in to before.
 +* <tt>[[cookies.txt]]</tt>
 + 
 +===Download actions===
 +What action to perform when downloading certain types of files (save or open with a specified application)
 +* <tt>[[mimeTypes.rdf]]</tt>
 + 
 +===Form history===
 +Autocomplete entries for web forms and the search bar.
 +* <tt>formhistory.dat</tt> (Firefox)
 +* <tt>''number''.w</tt> (Mozilla Suite). 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.
 + 
 +===Permissions===
 +Cookie, image, and extension install permissions.
 +* <tt>[[hostperm.1]]</tt>
 + 
 +===Preferences===
 +* <tt>[[User.js file|user.js]]</tt> (may not exist)
 +* <tt>[[Prefs.js file|prefs.js]]</tt> In most cases, migrating the "prefs.js" file from one profile to another is '''not''' recommended, especially if you had problems with the previous profile. If you choose to migrate "prefs.js", you may need to manually edit the paths to reflect the new profile location. You may also need to edit the file to remove preferences that refer to extensions that are not installed in the new profile.
 + 
 +===Saved passwords===
 +* <tt>[[key3.db]]</tt>
 +* <tt>signons.txt</tt> (Firefox 1.5.0.9 and below, 2.0.0.0, 2.0.0.1)
 +* <tt>[[signons2.txt]]</tt> (Firefox 1.5.0.10 and 2.0.0.2 and above)
 +* <tt>''number''.s</tt> (Mozilla Suite) If you do not migrate 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 [http://seamonkey.ilias.ca/profilefaq/#transferring_passwords]
 + 
 +===Search engines===
 +* <tt>searchplugins</tt> folder
 + 
 +===Security certificate settings===
 +* <tt>cert8.db</tt>
 + 
 +===User styles===
 +Only necessary if you have defined user styles with this method.
 +* <tt>chrome/[[userChrome.css]]</tt>
 +* <tt>chrome/[[userContent.css]]</tt>
 + 
 +===Mail and newsgroups===
''These files are used by Thunderbird and Mozilla Suite / SeaMonkey Mail.'' ''These files are used by Thunderbird and Mozilla Suite / SeaMonkey Mail.''

Revision as of 19:43, 28 June 2007

Mozilla applications include a feature that allows you to create a new user profile. A new profile is 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. This article describes how to accomplish this. Other articles exist for other situations: Migrate from Mozilla Suite or Netscape to Thunderbird, Migrate from Thunderbird to Mozilla Suite, Combining two profiles, Moving your profile folder.

Contents

Setting up

Your first step is to create the new profile, if you haven't done so already. To do this, completely close the application by choosing File -> Exit (or Quit). Next, start the Profile Manager for your Mozilla application and create a new profile. Make note of the name you give to the new profile so you can distinguish between the old and the new.

You may want to back up the old profile as a precaution.

Copying settings

Do not copy the entire profile directory because some files only work in a specific directory. 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.

With the application closed again, copy the files you want to retain from the old profile folder to the new. A list of files needed for each type of user data is provided below; it's recommended you only copy the data that you truly want in the new profile.

Add-ons

  • extensions folder (Firefox 1.5 and later). After transferring this data, also delete extensions.ini, extensions.cache and extensions.rdf from the new profile. This method will not move data that specific extensions may have saved in the profile.

Browsing history

Bookmarks

Cookies

Keeping cookies will keep you logged in to websites that you were logged in to before.

Download actions

What action to perform when downloading certain types of files (save or open with a specified application)

Form history

Autocomplete entries for web forms and the search bar.

  • formhistory.dat (Firefox)
  • number.w (Mozilla Suite). 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.

Permissions

Cookie, image, and extension install permissions.

Preferences

  • user.js (may not exist)
  • prefs.js In most cases, migrating the "prefs.js" file from one profile to another is not recommended, especially if you had problems with the previous profile. If you choose to migrate "prefs.js", you may need to manually edit the paths to reflect the new profile location. You may also need to edit the file to remove preferences that refer to extensions that are not installed in the new profile.

Saved passwords

  • key3.db
  • signons.txt (Firefox 1.5.0.9 and below, 2.0.0.0, 2.0.0.1)
  • signons2.txt (Firefox 1.5.0.10 and 2.0.0.2 and above)
  • number.s (Mozilla Suite) If you do not migrate 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]

Search engines

  • searchplugins folder

Security certificate settings

  • cert8.db

User styles

Only necessary if you have defined user styles with this method.

Mail and newsgroups

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

  • (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. Important: You also need to copy key3.db.
  • abook.mab and history.mab - Personal Address Book and Collected Addresses. For migrating other address books, see this article.
  • cert8.db - Security certificates
  • chrome/userChrome.css and chrome/userContent.css (if they exist) - User-defined styles
  • key3.db - Key database for passwords
  • mimeTypes.rdf - Actions to perform on downloaded files
  • msgFilterRules.dat (in each account subfolder) - Message filters
  • 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.
  • training.dat - Custom training for Junk Mail Controls
  • signons.txt (Thunderbird) - Saved passwords in recent Thunderbird profiles. Important: You also need to copy key3.db.
  • user.js (if it exists) and prefs.js - User Preferences. In most cases, migrating the "prefs.js" file from one profile to another is not recommended. If you choose to do so, you may need to manually edit the paths in "prefs.js" to reflect the new profile location. You may also need to remove 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 (Thunderbird) - Themes and Extensions. Important: 1) Only copy this folder in Thunderbird 1.5 or later. 2) 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). 3) Migrating this folder is not recommended if you had problems with the previous profile.