We are currently in the process of moving the company servers to a new network domain. We currently have both the old and new domains on the network set up as trusted domains of each other. Eventually after everything is migrated, we will discontinue the old domain. We will soon need to move the SQL Server 2008 R2 server to the new domain. Some issues that I am already aware of are; Windows logins - I assume that SQL server logins would be unaffected by this change but that Windows logins would need to be re-created. Correct ? Services startup - All my SQL Server services are currently started/stopped under authority of a domain username. I would need to edit these service properties to change the service username and password. Correct ? Reporting Services - All reporting services permissions that are Windows user based would need to be reconfigured according to the new domain users. Are there any other critical configurations (apart from user permissions) that I should consider to ensure a successful migration ? SQL server master key, encryption keys and database keys - I have no idea how a change in domains could affect these keys. I am especially concerned that the key might no longer be valid on a new domain. I do have backups of all keys, but if a key becomes invalid on a new domain then even a backup is not going to save me if there is a problem. Any advice on the implications here would be greatly appreciated.