Projects Import

Importing projects

1. On the source TeamCity On-Premises server, create a backup file containing the projects to import.

2. On the target server, go to Server Administration | Project Import, upload the backup file, and follow the wizard. TeamCity displays the results when the import finishes.

Data not included into import

The import has the following limitations:

• Agents and agent pools are not imported (TW-39797).

• Settings are merged on a per-file basis: new files are added, but no settings files are merged. For example, if a project being imported already exists on the target server, its parameters, project features, and plugin settings are not merged.

• If you use the "Store secure values (like passwords or API tokens) outside of VCS" option for versioned settings, credentials are not imported for the projects that already exist on the server.

• Audit records are imported only if users are in the import scope.

• Running builds and the build queue are not included in the backup, and thus not imported.

• Internal IDs, such as build IDs, are not preserved. This means that URLs to the build results pages from the old server appear broken even if redirected to the new server.

• Global server settings (authentication schemes, custom roles, and so on) are not imported.

• Build artifacts and logs cannot be imported to TeamCity Cloud.

Moving artifacts and logs

Restoring artifacts and logs of imported projects is available only on TeamCity On-Premises instances. See this article for more information: Migrate from TeamCity On-Premises to TeamCity Cloud.

Viewing Import Results

Each import process creates the projectsImport-<date> directory under the TeamCity logs, allowing you to view the import results. This directory contains:

• the conflictingFiles directory with all the data that has been merged

• mappings of the fields in the source and target databases

• the import report listing the import results, including the information on the data that has not been imported (if any)