Current dilemma I face is that a client has a Web Application named http://site1 which is their production Web Application is a SP2013 Farm.
In this same Farm they started developing their new environment ( Call it http://site1dev ) which at Go Live is to become their production environment.
The catch is that at go live 'site1dev' needs to be renamed to respond to 'site1' and the existing 'site1' is to become 'site1old' till it's time of full decommissioning.
I have tried migrating the content DB's of the web application to a new one, this however fails as a result of the duplicate site collection ID's in the same farm even though the mount-spcontentdatabase is successful.
What would be the best way to achieve this? Can the IIS Sites be renamed / extended and then just have their bindings modified?