We have to migrate a SP 2010 web application to SP 2013. Total 34 site collection under 1 web application. Data is only 46 gb. We have to use a famous 3<sup>rd</sup> party tool which generally does a good job for site collection migration.
Now we need few suggestions from real-time experience guy who has done migration through Quest tool.
Basically we want to use famous 3rd party tool only for site collection upgrade, all previous steps we have plan to do manually.
Our planned steps are:
- Prepare (This step is not by the 3<sup>rd</sup> party tool)
- Gather information and clean up 2010 farm – Not by 3rd party tool
- Prepare 2013 farm
- Install software
- Configure service application
- Configure farm settings
- Upgrade databases (This step is not by the 3rd party tool tool)
- Copy databases
- Upgrade service application databases
- Create web applications and apply customizations
- Upgrade content databases
- Upgrade sites (site collection)
- Begining from this step 3rd party tool tool needs to be involved.
Note: we have some doubt that if all service applications data can be migrated and reusable or not?
If not reusable then, we have to build particular service application from scratch?
We need your help on the following questions:
- Is our planning correct that we can do steps 1 & 2 without any third party tool?
- Only in case of site collection upgrade we can use the 3rd party tool.
- In this case can we migrate all user privilege through the 3rd party tool while migrating site collections?
Please help with you real-time experience if our plan is realistic.