How to Migrate IIS Websites to a New Windows Server
Applies to: migrations involving Windows Server 2019, 2022 and 2025.
IIS migration must move configuration, content, certificates, service identities, DNS and application dependencies together.
Migration requires a tested rollback and application-owner acceptance. Visit networkmanager.info for managed Windows VPS services.
Prerequisites
- Install matching IIS role services.
- Inventory sites, pools, bindings and modules.
- Back up content, configuration and certificates.
- Test application compatibility.
Procedure
Step 1: Export inventory
Capture sites and pools.
%windir%\system32\inetsrv\appcmd list site
%windir%\system32\inetsrv\appcmd list apppoolStep 2: Back up configuration
Create named backup.
%windir%\system32\inetsrv\appcmd add backup BeforeMigrationStep 3: Copy content
Preserve ACLs with approved file migration tool.
Step 4: Transfer certificates
Export only approved certificates with private keys through protected PFX handling.
Step 5: Recreate configuration
Build pools, sites and bindings on destination.
Step 6: Test with host override
Validate before DNS cutover.
Step 7: Cut DNS
Use reduced TTL and monitored maintenance.
Verification
Test HTTP status, TLS chain and application transaction from representative clients.
Get-Website
Get-WebBinding
Invoke-WebRequest https://portal.corp.example -UseBasicParsingRollback
Return DNS or load balancer to source and keep destination isolated until corrected.
Operational notes
Application databases, secrets and external services are not included in an IIS configuration backup.
Official references
Explore Netcloud24 Canada.
