Transferring data to a new profile: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
(added caveat and link due to users thinking its intended for restoring a entire profile)
Line 9: Line 9:
* <tt>bookmarks.html</tt> - Bookmarks  
* <tt>bookmarks.html</tt> - Bookmarks  
* <tt>cert8.db</tt> - Security certificates
* <tt>cert8.db</tt> - Security certificates
* <tt>chrome/[[userChrome.css]]</tt> and <tt>chrome/[[userContent.css]]</tt> (if they exist) - User-defined styles
* <tt>chrome/[[userChrome.css]]</tt> and <tt>chrome/[[userContent.css]]</tt> (if they exist) - User-defined styles. '''Note:''' It is '''not''' recommended to migrate these files if you had problems with the previous profile.
* <tt>cookies.txt</tt> - Cookies  
* <tt>cookies.txt</tt> - Cookies  
* <tt>formhistory.dat</tt> ''(Firefox)'' or <tt>''(number)''.w</tt> ''(Mozilla Suite)'' - Form history  
* <tt>formhistory.dat</tt> ''(Firefox)'' or <tt>''(number)''.w</tt> ''(Mozilla Suite)'' - Form history  
Line 16: Line 16:
* <tt>hostperm.1</tt> - Cookie, image, and extension install permissions
* <tt>hostperm.1</tt> - Cookie, image, and extension install permissions
* <tt>mimeTypes.rdf</tt> - Actions to perform on downloaded files
* <tt>mimeTypes.rdf</tt> - Actions to perform on downloaded files
* <tt>[[user.js]]</tt> (if it exists) and <tt>[[prefs.js file|prefs.js]]</tt> - User Preferences.  '''Note:''' In most cases, migrating the <tt>prefs.js</tt> 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.  Additionally, you may need to remove preferences that refer to extensions that are not installed in the new profile.
* <tt>[[user.js]]</tt> (if it exists) and <tt>[[prefs.js file|prefs.js]]</tt> - User Preferences.  '''Note:''' In most cases, migrating the <tt>prefs.js</tt> file from one profile to another is '''not''' recommended, especially if you had problems with the previous profile. If you choose to do so, you may need to manually edit the paths in prefs.js to reflect the new profile location.  Additionally, you may need 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 pairs of files from the <tt>searchplugins</tt> folder in the source [[installation directory]]) to the destination <tt>searchplugins</tt> folder in the destination installation directory.  '''Note:''' Starting with Firefox 1.5, newly-installed search plugins will be added to the profile's <tt>searchplugins</tt>  folder, so you may have search plugin files in both the installation directory and the profile.
* <tt>searchplugins</tt> folder - Search plugins. Copy the .src and .gif/.png pairs of files from the <tt>searchplugins</tt> folder in the source [[installation directory]]) to the destination <tt>searchplugins</tt> folder in the destination installation directory.  '''Note:''' Starting with Firefox 1.5, newly-installed search plugins will be added to the profile's <tt>searchplugins</tt>  folder, so you may have search plugin files in both the installation directory and the profile.



Revision as of 22:14, 27 December 2006

This article describes how to copy data and settings from one profile to another and lists a suggested set of files. This process will not migrate extensions, themes or toolbar/window customizations. It is not intended for moving or restoring a complete profile.

Completely close Firefox/Thunderbird/Mozilla Suite, and copy the files shown below from the source profile folder to the destination profile folder. This process will overwrite existing files of the same name so you may wish to back up the profile data beforehand.

Browser

These files are used by Firefox and Mozilla Suite.

  • bookmarks.html - Bookmarks
  • cert8.db - Security certificates
  • chrome/userChrome.css and chrome/userContent.css (if they exist) - User-defined styles. Note: It is not recommended to migrate these files if you had problems with the previous profile.
  • cookies.txt - Cookies
  • formhistory.dat (Firefox) or (number).w (Mozilla Suite) - Form history
  • key3.db and signons.txt (Firefox) - Saved passwords.
  • history.dat - Browsing history
  • hostperm.1 - Cookie, image, and extension install permissions
  • mimeTypes.rdf - Actions to perform on downloaded files
  • user.js (if it exists) and prefs.js - User Preferences. Note: 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 do so, you may need to manually edit the paths in prefs.js to reflect the new profile location. Additionally, you may need to remove preferences that refer to extensions that are not installed in the new profile.
  • searchplugins folder - Search plugins. Copy the .src and .gif/.png pairs of files from the searchplugins folder in the source installation directory) to the destination searchplugins folder in the destination installation directory. Note: Starting with Firefox 1.5, newly-installed search plugins will be added to the profile's searchplugins folder, so you may have search plugin files in both the installation directory and the profile.

Mail and newsgroups

These files are used by Thunderbird and Mozilla Suite Mail.

  • 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 and (number).s - Saved passwords. 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.
  • 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
  • user.js (if it exists) and prefs.js - User Preferences. Note: 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. Additionally, you may 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.

Note: Do not copy the whole profile directory. Some of the other files contain absolute path information (like for security certificates), and your profile might not work correctly with old entries from the original profile.

See also