How to Migrate an IIS Website to a New Server

Easily migrate website from IIS to new server with secure and seamless transfer. Our IIS Support team is ready to assist you. 

How to Migrate an IIS Website to a New Server

Moving an IIS website to a new server can be simple and safe when done correctly. Choosing the right approach ensures your website remains functional and secure throughout the migration. There are two reliable ways to transfer your site: using Shared Configuration or the AppCmd command-line tool. Both methods are effective, and your choice depends on your server setup and preferences.

Using Shared Configuration for Migration

Shared Configuration allows you to export your server’s configuration and apply it directly on the new server.

1. Open IIS Manager on your current server and select the main server node.
2. Locate the Shared Configuration option in the server settings and open it.
3. Click on Export Configuration and select an existing folder to save the configuration files. Protect these files with a strong password that includes numbers, upper and lower case letters, and symbols.

This process preserves your IIS website configuration, ensuring all website settings and bindings are consistently applied on the new server.

4. You will find three key files in the folder:

• administration.config
• applicationHost.config
• configEncKey.key

Copy these files to the new server.

5. On the destination server, open IIS Manager and enable Shared Configuration. Enter the folder path, username, and password used earlier. Confirm the encryption password when prompted and restart IIS Manager to apply the changes.

This method works best for new server environments and ensures a consistent configuration transfer.

Using AppCmd for Manual Migration

For a more controlled migration, the AppCmd command-line tool can be used to export and import website and application pool settings.

1. Open Command Prompt on the original server and export all application pools using the appropriate AppCmd command. Delete default application pools on the new server to prevent conflicts.
2. Export your website settings with AppCmd and save the output files.

You can also integrate an IIS hostable web core for lightweight testing or hosting of web applications during the migration to ensure everything functions before switching fully to the new server.

3. Transfer the exported files to the new server and open Command Prompt.
4. Import the application pools first, followed by the website settings. Verify that all configurations are correct and that the websites function as expected.

This method is ideal for servers with custom configurations or multiple websites, giving you precise control over what is transferred.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion 

In short, to migrate a website from IIS to a new server, follow the right method carefully to ensure a smooth transfer with minimal downtime while keeping all settings intact.