I need to perform a staggered migration of my SharePoint 2010 sites to SharePoint 2013. Three of my web applications and associated content databases are ready for a migration / upgrade to 2013 but another two will not be ready for another two months. 

What are the implications of doing this? My concerns are the metadata and mysites but there could be more issues?

Thanks.

Chris

Move the sitecollection to different database using move-spsite command and migrate them to sp 2013. there wouldn't be any problem when you migrate them some site collections now and other later.

With mysites being used in the 2010 I need to move the profilesdb and socialdb to 2013 along with the mysites content db. Would that cause an issue for users who are delayed moving to 2013? Would it be best to migrate mysites to 2013 and set the 2010 mysites to read only (that will mean 2010 users can't update information in mysites).

Also if I migrate the metadata database to 2013 now how does that affect the sites that migrate later to 2013?

Thanks.

Hi Chris,

About upgrading My Sites 2010 to 2013, setting the 2010 My Sites to read only is a suitable way to prevent from issues.

What is the metadata database? Is it the profile database or social database? If you make all MySites as read-only in SharePoint 2010, the profile database and social database will be not changed. After you migrate these databases to SharePoint 2013, all data of these database in SharePoint 2013 is same with the data in SharePoint 2010. It will have few effect when you migrate sites later.

Best Regards,

Dean Wang