Hi,

can any one suggest on below.

Many people suggested to change the classic authentication in SP2010 to claims base authentication before migration SP2010 to 2013.So i migrated all the classic based authentication site in our SP2010 server to Claims authentication.

But now in SP2010 it self we had many custom web application got deployed which works based on login windows users and its assigned authentication. Which are not working properly after claims migration in SP2010.

So can we skip this claims authentication step to migrate successfully our 2010 site to 2013 SharePoint.

You can migrate from Classic to Claims either before or after migration.  Its easier to do it before migration, but as you found out that will affect your existing 2010 environment.  If you don't want that side effect so the 2010 environment can continue to run then migrate after upgrading to 2013.  YOu will still need to update some of you custom code if its not working correctly under claims as part of your upgrade.  But at least 2010 will continue to work while you do that.

I prefer to do it after. Typical workflow for multiple farm upgrades I did was:

Create SharePoint 2013 Web Application in Claims mode

Mount SharePoint 2010 Classic DB to 2013 Claims Web App

Use Convert-SPWebApplication to migrate from Classic to Claims for each database that is mounted

I find it easier and quicker to convert post-migration.

Hi Paul,

Thanks for Reply.

Can I continue with classic authentication even in sp2013 for the intranet sites which we are going to migrate 2013. Since we had many application as part of our intranet with custom applications. Where each dash board we designed on login users windows account and the group he belongs to.

I hope this custom application will break even after migrating to 2013 with claims authentications. Since all this are written on the logic of windows user account.

Please suggest.