Moving a Citavi 6 database to another MS SQL server 

Use the features in MS SQL to transfer your Citavi database to another MS SQL server. Follow the instructions on Microsoft's support pages for copying and restoring or moving databases and database files.

Your existing Citavi 6 for DBServer licenses will be migrated automatically along with your database.

Please check the following:


Automatically migrate users

As long as the new MS SQL server is in the same domain as before, you do not need to make any changes for Active Directory users or groups.

If you are using SQL server logins, the logins will need to be present on the new SQL server. Transfer them using MS SQL features.

Manually adding a user to the new server

If it's not possible to automatically migrate the user, we recommend using the Citavi 6 DBServer Manager to delete the user before the migration and then later add the user to the new MS SQL Server.

In this case you will need to re-assign database and project roles in the Citavi 6 DBServer Manager. Make note of the way everything was set up before the migration.

Please also read Microsoft's article on how to manage metadata when making a database available on another server.


If the attachments also need to be moved to a new location, make sure that the NTFS rights are correct at the file level. You will also need to use the DBServer Manager to change the attachment path for each project.

Connection files and AdminSettings

The DBServer Manager connection file as well as the Citavi connection file will need to be updated with the connection string to the new DBServer for all clients.

If you used the AdminSetting DBServerConnectionString to distribute the previous SQL Server connection information to the Citavi clients, you will need to re-distribute the connection information. Configure a new MSI Setup for the Citavi users or change the setting in the Windows Registry via the group policy.


If you used Citavi 6 DBServer Manager to set up backups, delete the backup tasks before the migration and create them on the server again. Make sure that the SQL Server service account has sufficient NTFS permissions for the Backup folder.