JIRA is now available as three separate applications, JIRA Software, JIRA Service Desk, and JIRA Core. For more information on administering these applications, refer to the Administering JIRA Applications documentation.

Importing Data from FogBugz for Your Server

The JIRA Importers plugin, which is bundled with JIRA, allows you to import data from FogBugz for Your Server by connecting to a live FogBugz for Your Server database.

(info) Our main website highlights some top reasons why people migrate from FogBugz to JIRA.Version 4.2 or later of the JIRA Importers plugin is compatible with Fogbugz for Your Server versions 7.3.6 to 8.7.60. The JIRA Importers plugin requires that your FogBugz for Your Server database is MySQL, Microsoft SQL Server or Microsoft SQL Server Express. 

The FogBugz for Your Server import process consists of simply running the FogBugz Import Wizard (below):

  • You can choose to map individual fields and field values during the import process, some of which are mandatory.
  • At the end of the FogBugz Import Wizard, you will be given the option of creating a FogBugz configuration file, which contains the settings you configured whilst running through the FogBugz Import Wizard. This is useful if you need to test your FogBugz import on a test JIRA server first before performing the import on a production system.

(info) These instructions refer to a FogBugz for Your Server, which is an installable implementation of FogBugz that operates behind your firewall. To import from a FogBugz On Demand (SaaS) issue tracker site, please follow the instructions for here.

On this page:

Running the FogBugz for Your Server Import Wizard

  1. Before you begin, please backup your JIRA data.
  2. Log in to JIRA as a user with the JIRA Administrators global permission.
  3. Choose > System. Select Import & Export > External System Import to open the Import external projects page.
    (tick) Keyboard shortcutg + g + start typing external system import
  4. Select the Import button associated with the FogBugz for Your Server option to open the FogBugz Import Wizard: Setup page.
  5. On the FogBugz Setup page, complete the following fields/options:

    Database Type

    Select the type of database that your FogBugz for Your Server installation uses:

    • PostgreSQL
    • Microsoft SQL Server
    • MySQL
    Hostname Specify the hostname or IP address of the server running your FogBugz site's database server.
    Port Specify the TCP/IP port that the FogBugz site's database server is listening on.
    (tick) This field is automatically populated with the default port value based on the Database Type you choose above.
    Database Specify the name of your FogBugz database (into which FogBugz for Your Server saves its data).
    (info) If you need to specify an instance ID for your database, do so using the syntax fogbugz;instance=sqlexpress (where fogbugz is the name of your FogBugz database and sqlexpress is your FogBugz database's instance ID. The database name can usually be found in the Windows registry. See http://bugs.movabletype.org/help/topics/setup/WindowsWhatSetupDoes.html and then search for 'Initialize Registry Settings' (for details on how to access the relevant registry keys and values).
    Username Specify the database user that FogBugz uses to connect to its database.
    Password Specify the password of the database user (above) that FogBugz uses to connect to its database.
    Use an existing configuration file Leave this check box cleared if you do not have a configuration file or if you want to create a new configuration file. Configuration files specify a mapping between fields in FogBugz for Your Server and those in JIRA.
    (info) Note:
      • If you select this option, you will be asked to specify an Existing Configuration File.
      • If you do not select this option, then at the end of the FogBugz Import Wizard, JIRA will create a configuration file which you can use for subsequent imports (for re-use at this step of the FogBugz Import Wizard).
    JDBC connection parameters
    (in expanded Advanced tab)
    The FogBugz Import Wizard will construct a JDBC-based database URL from the FogBugz database server details you specify above. JIRA uses this URL to connect to and import issues from FogBugz for Your Server. If you need to specify any additional connection parameters to your FogBugz database, specify them here.
    (info) If you chose MySQL (above), the FogBugz Import Wizard will add several additional connection parameters by default.
  6. Click the Next button to proceed to the Set up project mappings step of the FogBugz Import Wizard.

  7. On the Set up project mappings page, select which FogBugz projects you wish to import into JIRA.

  8. (info) All projects are selected by default, so clear the check boxes under Import of the FogBugz projects you do not wish to import into JIRA.
    For FogBugz projects you wish to import into JIRA, click in Select a project and then do either of the following:
    • Start typing the name (or key) of a project that already exists in JIRA or use the dropdown menu to select an existing JIRA project.
    • Select Create New from the dropdown menu and in the resulting Add A New Project dialog box, type the following:
      1. A new project Name
      2. A new project Key
        (info) This will be used as the prefix for all issue IDs in your JIRA project.
      3. The Project Lead.
  9. Click the Next button to proceed to the Set up custom fields step of the FogBugz Import Wizard.
  10. On the Set up custom fields page, for each External field in FogBugz which the FogBugz Import Wizard cannot match to an existing JIRA field, you can choose to either:
    • have the FogBugz Import Wizard automatically create new custom fields in JIRA based on the names of FogBugz's fields. This is the default option - whereby the names of the JIRA custom fields to be automatically created appear in the JIRA field dropdown lists.
  11. Click the Next button to proceed to the Set up field mappings step of the FogBugz Import Wizard.
  12. On the Set up field mappings page, if there External fields in FogBugz whose values you wish to modify before they are imported into JIRA, select the Map field value check boxes next to the appropriate fields.
    (info) Please note that it is mandatory to map FogBugz's sStatus (i.e. Status) field to specific JIRA Status field values as the JIRA Status field is an integral part of JIRA workflows.
    • Other External fields in FogBugz which are likely to appear on the Set up field mappings page are:

      External field in FogBugz Not choosing the 'Map field value' check box
      sCategory The FogBugz Import Wizard will automatically create missing issue types in JIRA and will ensure that the issues are migrated with the correct issue type.
      sCustomerEmail The FogBugz Import Wizard will not map values for this field.
      sComputer The FogBugz Import Wizard will not map values for this field.
      sFullName The FogBugz Import Wizard will automatically map FogBugz usernames to JIRA usernames (lowercase).
      sPriority The FogBugz Import Wizard will automatically create missing values in JIRA and will ensure that the issues are migrated with the correct priority (e.g. "Normal" in FogBugz to newly-created "Normal" in JIRA).
      sStatus (Resolution) The importer will create corresponding Resolutions in JIRA instead of using the existing ones.
    • Select the appropriate JIRA Workflow Scheme in that will be used by the FogBugz issues you will import into your JIRA project.
      (info) If you are importing your FogBugz issues into an existing JIRA project, ensure that you choose the JIRA workflow scheme used by that existing JIRA project.

  13. Click the Next button to proceed to the Set up value mappings step of the FogBugz Import Wizard.
  14. On the Set up value mappings page, specify JIRA field values for each FogBugz field value (as detected by the FogBugz Import Wizard).
    (info) Any fields whose Map field value check boxes were selected in the previous step of the FogBugz Import Wizard will be presented on this page, including the mandatory sStatus FogBugz field.
  15. Click the Next button to proceed to the Set up links step of the FogBugz Import Wizard.
  16. On the Set up links page, specify the JIRA link type for each FogBugz link type (as detected by the FogBugz Import Wizard). To learn more about JIRA link types, please see Configuring Issue Linking.
  17. Click the Begin Import button when you are ready to begin importing your FogBugz data into JIRA. The importer will display updates as the import progresses, then a success message when the import is complete.
    • If you experience problems with the import (or you are curious), click the download a detailed log link to reveal detailed information about the FogBugz Import Wizard process.
    • If you need to import data from another FogBugz product/project or site with the same (or similar) settings to what you used through this procedure, click the save the configuration link to download a FogBugz configuration file, which you can use at the first step of the FogBugz Import Wizard.

Congratulations, you have successfully imported your FogBugz projects into JIRA! If you have any questions or encounter any problems, please contact Atlassian support.

Tips for importing FogBugz for Your Server data into JIRA fields

During the import process, the following data is copied from the FogBugz Server database into JIRA:

In FogBugz


Import Notes



FogBugz data is imported on a per-project basis. You can either specify an existing JIRA project as the target, or the importer will automatically create a project(s) for you at time of import. (For more information about JIRA projects, please see Defining a Project.)



You can choose to have the importer automatically create your FogBugz components in JIRA, or choose to have bugs imported into no component in JIRA.


Fix Version

Versions are imported from FogBugz (if you choose). After importing, you can manually set appropriate versions to the Released state in JIRA if you wish.



Every FogBugz case becomes a JIRA issue.

Case ID

Bug Import ID

Each imported issue ('case') will be given a new JIRA ID, and the old FogBugz ID will be saved into a JIRA custom field called 'Bug Import ID'. This custom field is searchable, so you can search for JIRA issues by their old FogBugz ID. If you don't need this custom field, delete it or 'hide' it (as described in Specifying Field Behavior).





FogBugz allows for links to other issues to be automatically generated by using the format "bug issueId" or "case issue id". After import, any string matching this pattern will be rewritten to their new JIRA key. For example, a comment "Please see case 100" may be rewritten to "Please see IMP-100".



Attachments are extracted from the FogBugz database and saved to disk. Any e-mail issues will be parsed for attachments and the e-mail text saved as a comment. The dates and user attaching the attachments will be retained.To specify the location on disk, see Configuring File Attachments.


Issue Type

You can configure mapping of specific Case Categories to specific Issue Types.



You can configure mapping of specific FogBugz values to specific JIRA values.



You can configure mapping of specific FogBugz values to specific JIRA values, provided you create your workflows in JIRA before running the importer.

  • The JIRA 'Status' field is integral to JIRA workflow. To learn more, please see What is Workflow.
  • To create a JIRA workflow, please see Configuring Workflow.
  • To create a JIRA workflow scheme (which you can then associate with appropriate projects and Issue Types), please see Activating workflow.



You can configure mapping of specific FogBugz values to specific JIRA values.



You can configure mapping of specific FogBugz link types to JIRA link types.



The FogBugz Computer field is imported into a JIRA Custom Field called 'Computer'.

Customer Email

Customer Email

The FogBugz Customer Email field is imported into a JIRA Custom Field called 'Customer Email'.



You can choose to have the importer automatically create JIRA users for any FogBugz users who do not already exist in JIRA.

  • Users who interacted with the FogBugz system will be created as active accounts in JIRA. Other users will be imported into a special group called "fogbugz-import-unused-users" and will be deactivated.
  • Passwords from FogBugz are not imported (as they are hashed in the database). Users from FogBugz will need to get their passwords emailed to them the first time they log into JIRA.
  • Users with no real name stored in FogBugz will get the portion of their email address (login name) before the "@" character as their Full Name in JIRA.
  • If you don't specify any particular mappings, the user name will be created from the first letter of the first name and the last name, all in lowercase.
  • If you are using External User Management, the import process will not be able to create JIRA users; instead, the importer will give you a list of any new users that need to be created. You will need to create the users in your external user repository before commencing the import.
  • If you have a user-limited license (e.g. personal license), and the number of required users is larger than the limit, then the import will be stopped. A page will be displayed showing a list of users that can't be created.

Other fields

Custom fields

If your FogBugz system contains any custom fields, you can choose to map them to specific JIRA custom field(s). If your custom fields don't yet exist in JIRA, the importer can automatically create them for you.
Please note that the FogBugz Custom Field plugin is not supported.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

22 Archived comments

  1. User avatar

    Todd Day

    Ugh.  I'm using 7.2.16 of FogBugz, and this plugin wants at least 7.3.6.  I'll have to spend $3k to upgrade it just so I can get off it! (sad)

    03 Jun 2011
    1. User avatar

      Pawel Niewiadomski [Atlassian]

      Hi Todd,
      give it a try it may work.

      It's not that for sure it will not work. The statement says that with 7.3.6 we're sure it will work.

      If there were no major changes in the database structure between 7.2.16 and 7.3.6 everything should go fine.


      03 Jun 2011
  2. User avatar


    You may be able to get it to work by making a small set of changes to your FogBugz schema.  I was able to do this with FogBugz 4.5.x.  Fog Creek publishes a description of their schema so it's generally possible to determine what changes need to be made by correlating the error with the schema.  I'd suggest doing this on a clone of your database, not the production db.

    16 Jun 2011
  3. User avatar


    is there an option for us to do this from the Fogbugz hosted solution? We have been using this and have 3 years of history in there we don't want to lose. Thanks for the help.

    22 Jun 2011
    1. User avatar

      Pawel Niewiadomski [Atlassian]

      Sure there is. You need to create a database dump of your account using Admin->Your on demand account->Download your database (at the bottom).

      Then you need to import it into a local database server and you can then use JIRA importers plugin to do the rest.


      24 Jun 2011
  4. User avatar

    Paul Lomax

    Does this work with Jira On Demand?  (Especially if our Fogbugz hosted server is on an internal network...)

    02 Nov 2011
    1. User avatar

      Roy Krishna [Atlassian]

      Not yet, we are working on making our importers work with JIRA OnDemand. The best way to do this now is to download JIRA, run the importer, make a JIRA backup then we can import that into your JIRA OnDemand service.

      02 Nov 2011
      1. User avatar

        Kshitij Peter


        Is there any update on this?  We have Fogbugz(version 8.7) hosted at our end and would like to move it to JIRA on Demand(we are using JIRA Agile Cloud).

        I tried to use the url which we use to access Fogbugz but JIRA importer is not accepting it.

        23 Sep 2014
        1. User avatar

          Przemyslaw Borkowski [Atlassian]

          JIRA Cloud is only supporting FogBguz On Demand importer, because this one is based on FogBugz API. You can use it for your local installation of FogBugz, but you need to make sure that your FogBugz instance is visible to the outside world, so JIRA can access it during import process.

          If you cannot make your instance public, then you'll need to install local JIRA instance (even on evaluation license), run importer (FogBugz for Your Server or FogBugz On Demand - both should work) and then migrate local JIRA to JIRA Cloud - just as Roy has mentioned above.

          If you are sure that your FogBugz instance is visible to the outside world and importer still doesn't allow you to run import, then please contact with our support team - this scenario should work and we are supporting this type of migration.

          24 Sep 2014
          1. User avatar

            Ian Wells

            I got a HTTP 403 when attempting to login to my Fogbugz server instance, importing to JIRA cloud.


            This was because I was attempting to access using  port: 4565 for  Fogbugz.

            Because JIRA. " OnDemand instances have proxy configured to allow only connections on default ports." I switched to the default ports instead, and then it worked.

            22 Apr 2015
  5. User avatar


    Is the last comment still valid? Must we install JIRA on our server and use the importer, to then backup and make you import into the On Demand, or can we do it completely from the on demand?

    14 Jan 2013
    1. User avatar

      Pawel Niewiadomski [Atlassian]

      That depends on you configuration - if your FogBugz server is available from Internet you can try using "FogBugz On Demand" importer that's available in JIRA OnDemand. Because each FogBugz server has a remote API installed so there's no difference between your hosted FogBugz and FogBugz On Demand served by FogCreek.

      If you FogBugz is not available you don't have any other option than install JIRA locally for the import time.

      14 Jan 2013
  6. User avatar


    Will it also import FogBugz WIKI or only cases/issues ?

    12 Feb 2013
    1. User avatar

      Pawel Niewiadomski [Atlassian]

      No, we don't import FogBugz Wiki because JIRA doesn't support wiki pages. You can try using Universal Wiki Converter to import FogBugz wiki to Confluence.  If you need support with that you can start with asking on answers.atlassian.com

      12 Feb 2013
  7. User avatar

    Francis Upton

    Is there a way to preserve the Fogbugz ids to be the same as the JIRA issue Ids if they are being imported into an empty project?

    16 Jul 2013
  8. User avatar


    Is this an all or nothing import or can I select a range of issues based  on some key in FogBugz

    25 Sep 2013
    1. User avatar

      Przemyslaw Borkowski [Atlassian]

      It's all or nothing per project - During import you can select FogBuz projects and all issues for selected projects will be imported.

      26 Sep 2013
  9. User avatar

    Soo Min Ooi

    I tried the Fogbugz importer on JIRA, however the case comments were not ported completely to JIRA "Activity" tab, only the initial first comment was ported, subsequent comments were ignored. Anyone has encountered the same problem?

    23 Oct 2013
    1. User avatar

      Pawel Niewiadomski [Atlassian]

      It is strange, all comments should be visible on Activity tab for the issue, but they will not be visible on History page for the issue (because importer doesn't import historical changes). If you're still having the problem please contact https://support.atlassian.com so they'll be able to help you investigate the issue.

      24 Oct 2013
  10. User avatar

    William Wynn

    After running the import just as a test, I see that any comments in HTML format in Fogbugz (most of them), don't properly display any markup but just the raw tags instead. This makes some comments almost unreadable. Is there anything that can be done about this before or after the import?

    23 Oct 2013
    1. User avatar

      Pawel Niewiadomski [Atlassian]

      Sorry, that's currently unsupported (the formatted message is directly put into JIRA), I raised issue to fix that -  JIM-1070 - Support rich text format in FogBugz Open

      As a workaround you may want to try https://marketplace.atlassian.com/plugins/com.garyhodgson.jira.tinymce-renderer-plugin which should render all those HTML comments.

      24 Oct 2013
  11. User avatar

    Ian Wells

    I just found out that the conversion will create "fixVersions" for each of the Fogbugz assignable milestones.  If you want all milestones mentioned in all Fogbugz tickets, you may want to make all your Milestones "assignable" in the Fogbugz admin project  section first.

    13 May 2015
Powered by Confluence and Scroll Viewport