Using FogBugz On Demand? We've recently rolled out a new sidebar as part of taking FogBugz forward. Please see this article for details on what's new, what's changed, and where you can find all your favorite things.


Provided you have received confirmation for the migration from Fog Creek customer service, on the morning of, or evening before, you will need to do the following as described in the further sections:

  1. Shutdown your system(s)
  2. Prepare your data

Shutdown your system(s)



Preparing your data


WARNING: FogBugz will need to be completely shut down during these steps.

  1. Disable your mailboxes.
    1. NOTE: This will prevent any accidental consumption of emails from your mailboxes in the On Demand environment until you are ready to do so.
  2. If you have Microsoft SQL Server:
    1. Produce a Microsoft SQL Server backup (.bak) file of the FogBugz database
  3. If you have MySQL:
    1. If you’re using MySQL, you’ll need to run the mysqldump command which produces a .sql file:
    2. If you’re MySQL settings match the recommended settings (i.e. you use latin1_swedish_ci throughout) then:
      mysqldump -u<USER> -p<PASS> --default-character-set=latin1 --max_allowed_packet=200M <DBNAME> > <mysql_filename>.sql
    3. If you’re MySQL settings do not match the recommended settings (i.e. you use utf8_general_ci throughout) then:
      mysqldump -u<USER> -p<PASS> --max_allowed_packet=200M <DBNAME> > <mysql_filename>.sql
  4. Compute the Checksum (instructions below) for the Microsoft SQL Server .bak file or MySQL .sql file.
  5. Zip up the Microsoft SQL Server .bak file, or the .sql file if you’re using MySQL
  6. Compute the Checksum (instructions below) for the .zip file.
  7. Upload the zip file to the Fog Creek-provided unique and secure FTPS location


Your repositories can be migrated to On Demand after the FogBugz import is successfully completed.

  1. First, we recommend installing the Kiln Client and Tools. This includes the BigPush extension for Mercurial, which can help when pushing repositories with long histories that have grown unavoidably large.
  2. Create repositories in Kiln for the repositories you wish to move to On Demand.
  3. Push the repositories to move into their new Kiln On Demand repositories. As the changesets are recorded, cases mentioned in the commit messages will be linked to the appropriate cases.

Computing the checksum


To compute a checksum (the last line in the output depicted below), use this Microsoft utility: You’ll run the downloaded exe which will extract the files you need. From there you should end up with a fciv.exe file, so you’ll run it like so:

c:\your\extracted\location\> .\fciv.exe c:\path\to\backup\file.bak

And then get this output:

// File Checksum Integrity Verifier version 2.05.
3f435a19a285335472ce0a0b8a5e3185 c:\path\to\backup\file.bak

Send the last line to us.


At the command prompt, run:

md5sum <mysql_filename>.sql

And you’ll output similar to below:

MD5 (<mysql_filename>.sql) = 02496e675110e889c74e56c7e5e1daf2

Send this last line to us.