I have SharePoint 2007 website with 2 TB database. I need to migrate this in SP 2013 without using any tool.
Please share your experience.
Hi,
1.Go to SqlServer and take backup of the content database and restore it into your sqlserver.
2.Create new web application and site collection in SP2013.
3.Now remove the content database from this webapplication.
   a.Go to central Administrator
   b.Click on Application Management and then
   c.click on content database => Manage Content database
4.Then select the newly created webapplication URL
5.Click on the database which is on the left side.
6.Then go to remove content database part and check the checkbox then it will prompt you popup there click on then again ok button.
Now test the whether the webapplication still having relation with the content database by using the following command.
Test-SPContentDatabase-Name “name of content database”-webapplication “URL of webapplication”.
7.Now go to sql server and delete the database manually.
8.Now restore the content data base manually.
9.Now we need to attach the resstored content database  by using following command.
Mount-SpContentDatabase-Name “Database name”-webapplication “URL of webapplication”.
Now we can get following error like”Upgrade completed with following errors”.
Finally Migration has been completed successfully.Â
Hi Ashutosh
This is one of the toughest job if you are dealing with SharePoint. To my understand, SharePoint 2010 is the only path to SharePoint 2013. But even before that there other challenges what you need to overcome when you are planning to move in to SharePoint 2013.
The topmost challenge would be evaluation of your 2007 customization. You must go through the all the customization and then check whether the customization or third party tools or add-ins, or web parts are going to work in the new environment. Then decide what needs to be re-customized or deprecated.
Second challenge is user training as user would be experiencing a complete new user interface in comparison to the old interface. Despite of the fact the user interface is much better that the old one the user training is going to be challenge.
Then comes the strategy which I call Hop-in strategy as you need to move 2010 and then one everything works fine their move everything to 2013.
Please let me know if you need any additional information on the same.
-Vikram
Just my two pennyworth!
Ashutosh – This is the scenario we are faced with. We are moving from MOSS 2007 to SP Online. Fortunatley our MOSS enviornment isn’t that large and doesnt have many customisations or custom code.
We have identified the stuff we want in the new world. So we are “clearing” out redundant sites and lists in 2007. We have taken the view that in order to get the best out of 2013/Online we will rebuild most of our apps. Pretty easy for us, but for big MOSS implementation then the 2 step 2010 approach would probably make sense.
Checkout migration from 2007 to 2010 following migration 2010 to 2013. Still will be 2 step migration. MSDN plus some other “blog posts” have pretty much enough info to get it done.
