How-To: Migrate Classic Path-based SP2010 Site Collection with OOTB/SPD Workflows = To: Claims Different Path-based SP2013 Site Collection ?

Question

Hello,
I want to move an entire site collection from an old SharePoint 2010 farm to a new SharePoint 2013 farm. But there are a few requirements:
- The old SP2010 site collection contains multiple SPD Workflows and OOTB Workflows.
- URLs must be changes as the example: 
Source Site Collection URL: http://OldWebApp.SP2010.com/sites/OldSiteCollection 
Destination Site Collection URL shall be: http://NewWebApp.SP2013.com/projects/NewSiteCollection
- There are no custom solutions nor web parts.
How to accomplis this successfully ?
My steps would be:
1) Copying the content database from SP2010 SQL to the SP2013 SQL via: Copy-only backup feature, or the traditional Backup & Restore.
2) I have already the Web Application on the new SP2013 ready, So, I will just need to create the destination site collection in the SP2013 environment with the new desired URL: (http:\\NewWebApp.SP2013.com\projects\NewSiteCollection).
3) Remove the newly created Content Database of the new site collection in the destination environment.
4) Test-SPContentDatabase -name Old_Content_DB -webapplication http://NewWebApp.SP2013.com > C:\Issues.txt
My worry is that the SP2010 Web Application is Classic-based and I cannot change the entire Web Application to Claims-based as it hosts other running site collections !
Equally, My other worry is that the SP2013 Web Application is Claims-based and I cannot change the entire Web Application to Classic-based as it hosts other running site collections !
First-Question=> I cannot run Convert-SPWebApplication as I don't want to impact the entire source nor destination web applications - How to resolve this?
5) Mount-SPContentDatabase "Old_Content_DB" -DatabaseServer "DBServer" -WebApplication http://NewWebApp.SP2013.com
Second-Question=> As I mentioned above that my requirement is to migrate this old SP2010 site collaction to a totally new URL in SP 2013. My concern is that after completing step-5, the site
collection will overwrite the root new web application and it gets placed on: (http://NewWebApp.SP2013.com) !  I want it to be: (http://NewWebApp.SP2013.com/projects/NewSiteCollection) ? How to do this trick?
Third-Question=> Will all the SPD Workflows & the OOTB Workflows work correctly after the entire site collection has been moved from SP2010 to SP2013? I am asking this because I seen this:
(http://blogs.msdn.com/b/chandru/archive/2013/04/14/upgrading-spd-2010-workflows-to-spd-2013-workflows.aspx), and I got scared. What do you think ?
Could you please help me out in my three questions ?

Answer 1

Following are the steps:
Take the backup of the content database in SP 2010.
Create a classic based web application in SP 2013 using PowerShell.
New-SPWebApplication -Name "TestApplication" -ApplicationPool "TestApplicationAppPool" -AuthenticationMethod "NTLM" -ApplicationPoolAc
Create a content database in the web application created above.
Mount the database 
Mount-SPContentDatabase WSS_Content_100 -DatabaseServer SQL2012Demo -WebApplication http://sp2013demo:100
Now convert the web application to use claims authentication:
Convert-SPWebApplication -Identity "http://sp2013demo:100" -To Claims –RetainPermissions -Force
Finally, migrate the users to use claims identity:
$w = Get-SPWebApplication "http://sp2013demo:100"
$w.MigrateUsers($True)
See these links for more information:
http://www.sharepointnadeem.com/2013/12/sharepoint-2013-upgrade-from-sharepoint.html
http://www.sharepointnadeem.com/2014/01/upgrade-from-sharepoint-2010-classic.html
Blog | SharePoint Learnings CodePlex Tools |
Export Version History To Excel |
Autocomplete Lookup Field