Transferring data to a new profile: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
(added back suggestions to back up current profile and to copy over a few files at a time if the old profile was corrupt. Added signons.txt for Thunderbird)
m (Category:Redirects)
 
(27 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Request for comments}}
* [[Transferring data to a new profile - Firefox]]  
[[Category:Profiles]]
* [[Transferring data to a new profile - Thunderbird]]  
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]].
* [[Transferring data to a new profile - SeaMonkey|Transferring data to a new profile - Mozilla Suite/SeaMonkey]]  


Your first step is to create the new profile. 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.
[[Category:Redirects]]
 
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 current 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.
 
==Browser==
''These files are used by  Firefox and [[Mozilla Suite |Mozilla Suite / SeaMonkey]].''
 
* <tt>[[bookmarks.html]]</tt> - Bookmarks
* <tt>cert8.db</tt> - Security certificates
* <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==
''These files are used by Thunderbird and Mozilla Suite / SeaMonkey Mail.''
 
* <tt>''(number)''.s</tt> - 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'''.
* <tt>abook.mab</tt> and <tt>history.mab</tt> - Personal Address Book and Collected Addresses. For migrating other address books, see [[Moving address books between profiles | this article]]. 
* <tt>cert8.db</tt> - Security certificates
* <tt>chrome/[[userChrome.css]]</tt> and <tt>chrome/[[userContent.css]]</tt> (if they exist) - User-defined styles
*<tt>[[Key3.db|key3.db]]</tt> - Key database for passwords 
* <tt>[[MimeTypes.rdf|mimeTypes.rdf]]</tt> - Actions to perform on downloaded files
* <tt>msgFilterRules.dat</tt> (in each account subfolder) - [[Filters (Thunderbird) | Message filters]]
* <tt>[[popstate.dat]]</tt> (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.
* <tt>training.dat</tt> - Custom training for [[Junk Mail Controls]]
*<tt>[[signons.txt]]</tt>  ''(Thunderbird)'' - Saved passwords in recent Thunderbird profiles. '''Important:''' You also need to copy '''key3.db'''.
* <tt>[[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. 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.
* <tt>virtualfolders.dat</tt> ''(Thunderbird)'' - [[Saved Search]] folder settings
* <tt>Mail</tt> and <tt>ImapMail</tt> folders - E-mail messages and settings. See [[Importing_and_exporting_your_mail#Manually_importing_and_exporting | this article]].
* <tt>News</tt> 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.
* <tt>extensions</tt> 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.

Latest revision as of 05:38, 6 February 2009