Software migrations aren’t always easy…
…but we try our best to make this process as painless as possible for you! We provide a variety of methods to import your data. These tools all exploit the Manuscript API to get your data into Manuscript. If you don’t see something here that fits your needs, feel free to contact us and we will find a solution!
Regardless of your previous tool or your method, our advice is always this: Don’t put yourself in a position of migrating too many chunks or with too many phases. Make a plan, prepare the environment, and pull the trigger.
Please note that the tools listed below were originally created for FogBugz, but also support Manuscript. If you run into any issues, we’re here to help!
The Trac Importer will allow you to automate the process of completely migrating from Trac to Manuscript. In addition to your cases and their histories, you get your users and wikis.
Importing from Jira
Someone beat us to the punch, here: Martin Zardecki wrote this importer to get your data from Mantis into Manuscript in a hurry. Welcome to a community of brilliant, engaged, and productive users. Users who are Smart and Get Things Done.
If you can get your cases into a CSV file, we have some resources created by our enterprising users, which you can find below:
- Here is an option using Excel’s URL encode function: Import Tasks from Excel
- There is another Windows app here with source code on Google Code.
Importing from Other Tools
The Manuscript API is sufficiently powerful to use for exporting another bug tracker’s historical information into Manuscript. It has the advantage of not needing direct access to the database. If you’re thinking about doing this, we have friendly developers who can advise you on the process and who are very interested in what you’ve been using and how you’re moving forward. Shoot us an email and we’ll chat!