YouTrack Standalone 2017.4 Help

Migrate to YouTrack

YouTrack has a range of tools that you can use to migrate your data from other issue tracking systems to YouTrack. When you import your data from another tracker, you can pick up right where you left off in the previous application.

The topics in this section provide instructions for importing data from a number of different issue tracking systems. If the issue tracker that you were previously using is not listed here, import your issues from a CSV file.

YouTrack has a standard integration that lets you import entire projects from a Jira instance. To learn how to set up and use the integration, see Import from Jira.

This section of the documentation provides instructions for the following migration scenarios:

OptionDescription
Import from a CSV FileImport issues from any issue tracker that lets you export issues as a CSV file. Use this option to import issues from Trello (Business Class and Enterprise), Asana, GitLab and many others.
Import from BugzillaImport issues from Bugzilla with a Python import script.
Import from FogBugzImport issues from FogBugz with a Python import script.
Import from GitHubImport issues from GitHub with a Python import script.
Import from Mantis Bug TrackerImport issues from Mantis Bug Tracker with a Python import script.
Import from RedmineImport issues from Redmine with a Python import script.
Import from TracImport issues from Trac with a Python import script.
Import Issues from Another YouTrack ServerImport single issues or entire projects from one YouTrack server to another.
Migrate from Standalone to InCloudMigrate from a self-hosted YouTrack Standalone server to a YouTrack InCloud instance hosted by JetBrains.
Migrate from InCloud to StandaloneMigrate from a YouTrack InCloud instance that is hosted by JetBrains to a self-hosted YouTrack Standalone server.

If you simply want to move a YouTrack Standalone installation from one server to another, you can configure your new YouTrack server to use a copy of your old database. For instructions, see Change Database Location.

Last modified: 28 February 2018