TeamCity On-Premises
 
Get TeamCity On-Premises

Migrating to External Database

Edit pageLast modified: 24 September 2024

This article covers the steps required to migrate TeamCity data from the database of one type to another. For details on using an external database from the first TeamCity start, as well as the general external database information and database-specific configuration steps, refer to this article.

The most typical case for migration is when you evaluated TeamCity with the default internal database and need to switch to an external database to prepare your TeamCity installation for production use. The recommended steps are also applicable when switching from one external database to another. You can also follow them to move between database servers of the same type, but in that case, the database-specific data transfer is regularly more preferable.

There are several ways to migrate data into a new database:

  • Switch with no data migration: build configurations settings will be preserved, but not the historical builds data or users.

  • Full migration: all the data is preserved except for any database-stored data provided by the third-party plugins.

  • Backup and then restore: the same as full migration, but using the two-step approach.