We offer attended migrations of your existing For Your Server data to Manuscript On Premises, typically during our normal business hours (9AM to 5PM Eastern, Monday to Friday). If you’d prefer to migrate your data yourself, great! The following outlines that process, with minimal help from us.

Please note that this document applies to customers already using SQL Server. To import a MySQL database, you’ll need to first convert to SQL Server.

Getting Started

With proper preparation, migrating data to Manuscript On Premises can be accomplished with minimal downtime.

  1. Make sure a SQL Server backup of the FogBugz For Your Server database is available locally on the Manuscript On Premises database server. For reduced downtime, we recommend moving the FYS database to your new server before the migration to On Premises.
  2. Install Manuscript On Premises. For reduced downtime, do this ahead of your migration date.

Migrating the Data

  1. Stop IIS on both the Manuscript On Premises and For Your Server web servers
  2. Restore the FogBugz For Your Server SQL Server backup over the top of the appropriate Manuscript On Premises database (see below) — or simply rename the databases if they are on the same server already.If this is the first site you are migrating data for, you’ll want to restore your For Your Server data over the trial1 database (the trial number will be different if you have multiple Manuscript sites running on the same server). If this is an additional site that is being migrated in addition to an existing site in Manuscript On Premises, the database name will be trial2 or higher — the highest trial number is the most recently configured site.
  3. Ensure the Manuscript On Premises database user is mapped as db_owner on the new trial database.
  4. Disable active mailboxes. This gives you an opportunity to confirm the migrated data before pulling in new cases from any active mailboxes:
    UPDATE Mailbox SET fEnabled = 0 WHERE fDeleted = 0;
  5. If this is a test instance, we recommend sanitizing the database to avoid interactions with your production instance.
  6. Start IIS on the Manuscript On Premises web server, and allow the database to be automatically upgraded.
  7. Do the following from the Manuscript web server
    1. Make sure you are logged into Manuscript as an administrator
    2. Navigate to <your Manuscript URL>/f/debug/featureswitches (you’ll get 403s from external machines)
    3. Select the dropdown in the row labeled “SelfServiceSchemaFix” and choose “Force Enable” and click the “Update” button — if you don’t see this row, you can proceed to the next step.
    4. Navigate to <your Manuscript URL>/f/debug/database/schemacheck
    5. If there are errors on the page, click on the button labeled “Fix these errors” (if you aren’t logged in as an admin, you can’t see this button)
    6. On the resulting page, click the “Back to Schema Check” button. If there are still errors on the page, contact us.
  8. Start ES backfills by navigating to <your Manuscript URL>/f/debug/es from the Manuscript web server (you’ll get 403s from external machines).  You may see an alert that says “Alias not found”.  If that’s the case, click the button below it that says “Create ES Alias”.
  9. Click the “Start Indexer Backfill” button for each document type (bug, wikipage, and discusstopic).
  10. Update the sURLEmailPrefix (if you are changing URLs):
    SELECT * FROM Setting WHERE sKey LIKE '%sURLPrefixEmail%';
    UPDATE Setting SET sValue = '<new URL including protocol>' WHERE sKey LIKE '%sURLPrefixEmail%';
  11. Disable the Kiln plugin:
    UPDATE Plugin SET fEnabled=0 WHERE sPluginId LIKE '%kiln%';
  12. Ensure there are no admin notifications under the Gear Menu
  13. Once you are satisfied with the migrated data, re-enable mailboxes as necessary (Avatar Menu (bottom left) > Mailboxes)

Next Steps

Once your data is migrated to Manuscript On Premises, you may want to:

If you have any questions or would like assistance with this process, please don’t hesitate to contact us. We’re happy to help!