Sharepoint 2007 migration

Hi techies,
We have a 1 WFE and 1 DB hosting sharepoint 2007. what we have in that is , 1 web application and inside that 1 sitecollection. this site collection has number of subsites( Around 40-50) and the site collection act as intranet to our org. Most of the data
is list/libraraies, publishing sites, dataview webparts, lot of infopath forms.
Now we are planning to migrate this to sharepoint 2010, what can b the best way to do this, there is no custom codin on server, but we have lot of customisation through sharepoint designer and infopath.
Please guide me on this?
also the dataview / dataform created in sp 2007, are they gonna get affeted after migration? do we need to create these web parts from scratch in sharepoint 2010?
regards,
Rohit
Regards, Rohit

Hi,
There are a lot of resources out there for migrating from MOSS 2007 to SharePoint server 2010. You need to have at least SP2 for MOSS 2007 installed on your WFE server. After that you can check the status of your farm running
stsadm -o preupgradecheck.
I have published a checklist for migration, check it out:
http://social.technet.microsoft.com/wiki/contents/articles/checklist-for-migrating-from-sharepoint-2007-to-sharepoint-2010.aspx
This technet link provide you with a comprehensive guide:
http://technet.microsoft.com/en-us/library/cc303420.aspx
The best approach is to set up a separate SharePoint 2010 farm and the perform a database attach migration. You simply take a backup of your content database and the restore it to your new SQL server, then attach it to a web application you have created.
See the checklist I have provided above.
Regards
Henrik A. Halmstrand
sharepointrevealed.com
getspconfig.codeplex.com
Please click Mark As Answer; if a post solves your problem or
Vote As Helpful; if a post has been useful to you.

Similar Messages

SharePoint 2007 Migration SharePoint 2010 Documents Broken Link Issue

Hello All,
I'm in the process of doing a SharePoint migration from 2K7 to 2010 (different platform). In SP 2K7 I have several thousands of documents. I have approx. 5K documents with anywhere from 1 to several links (http, https) that
will break after the migration. Are there any Best Practices to deal with this issue? Any information at all!!!
Thanks
Suge
Deny yourself the knowledge of other cultures, you deny yourself the true riches of the world. Suge

Hi,
There are a lot of resources out there for migrating from MOSS 2007 to SharePoint server 2010. You need to have at least SP2 for MOSS 2007 installed on your WFE server. After that you can check the status of your farm running
stsadm -o preupgradecheck.
I have published a checklist for migration, check it out:
http://social.technet.microsoft.com/wiki/contents/articles/checklist-for-migrating-from-sharepoint-2007-to-sharepoint-2010.aspx
This technet link provide you with a comprehensive guide:
http://technet.microsoft.com/en-us/library/cc303420.aspx
The best approach is to set up a separate SharePoint 2010 farm and the perform a database attach migration. You simply take a backup of your content database and the restore it to your new SQL server, then attach it to a web application you have created.
See the checklist I have provided above.
Regards
Henrik A. Halmstrand
sharepointrevealed.com
getspconfig.codeplex.com
Please click Mark As Answer; if a post solves your problem or
Vote As Helpful; if a post has been useful to you.

SharePoint 2007 (WSS 3.0) migration to SharePoint Foundation 2013

Hi
I have a requirement to migrate a SharePoint 2007 (WSS 3.0) farm to a SharePoint Foundation 2013 farm. The WSS 3.0 farm has SQL Server 2005 Standard running so no restrictions on the size of the content database. The SharePoint Foundation 2010 and 2013 farms
will share the same SQL Server 2012 Standard instance (as I know WSS 3.0 will have to be migrated to 2010 before 2013). I also have two other WSS 3.0 farms (so three WSS 3.0 Farms, lets call these A (250GB), B (90GB) and C (60GB)) that I need to migrate
into WSS 3.0 Farm A before the migration to SP 2010.
My question is, can I migrate a 400GB WSS 3.0 site collection to SP 2010 or will I have to split this into separate site collections? I have read that there is a best practice limit of 100GB per site collection but this does not stop a larger migration from
happening. Obviously over time when the migration has completed to SharePoint Foundation 2013 the single site collection will grow and grow so perhaps now is the right time to split this out into, say, year named site collections, but surely this will incur
an end of year process to create new site collections and a custom dev headache due to different locations to send newly created sites?
Thanks.

The answer is Yes, and you are correct about the best practice of a limit of 100GB,
although, document and record centers (e.g. non collaborative) can go much higher.
http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#ContentDB
That being what it is, your sites will perform better if you find a topology that allows the content databases to be under 100GB each. You can use Move-SPSite to accomplish that feat.
You'll want a separate instance for 2010 and a separate instance for 2013
and finally, put some quota's in place and then governance document\statement that informs users that 100 GB is the max for any given site collection that uses collaborative features (calendars, lists, workflows, etc.)
The simple path is explained on technet, go from 2007 to 2010 (you can inplace upgrade if you want) then go from 2010 to 2013, database detach and attach is only way.
please check the below link that explains more about the migration from share point 2007->2013.
http://technet.microsoft.com/en-us/library/cc262483(v=office.15)
Stacy www.sharepointpapa.com

Please Help!! Lists and libraries suddenly blocked just before migrating from SharePoint 2007 to 2010

Hi all,
I took several weeks preparing the migration of a large farm from SharePoint 2007 to 2010 using the system of restore databases and mount site collections. I've built the new farm and I have done several full migration tests to verify that all was well the
day of final migration.
The farm consists of three virtual servers: one with SQL Server 2012 and two with SharePoint Server 2010. Upon completion of the tests we've moved the servers to another network. We have turned on the servers and everything seems to work fine.
Just the day of the final migration I wanted to check the HealtReports list of the Central Administration, and when I wanted to look up an alert, the view window has not shown me anything and ribbon has appeared with all options grayed. Days ago worked fine.
Alarmed by this, I have started to check all lists and libraries in the Central Administration and the same happens. I can not view or change the items, nor add. Neither I can change the properties of the lists or libraries, as if everything was locked. I
tried on the main site collection and same thing happens, and I have tried with several user with Total Control permissions. I have also verified that the site collection was not in ReadOnly mode.
I have restored a site collection from SharePoint 2007 and have migrated successfully to 2010. Before applying visual upgrade I found that the content is also locked. It is as if he had changed anything in the configuration of the whole farm, but I can not
find what. The Event Viewer of the three server shows no errors related to this. The SharePoint LOGS not show anything unusual.
I do not know where to look and urges me to find a solution because the old servers must be out of service soon. I accept any suggestions.
Kind regards.

Finally I answer myself because I've already found and fixed the problem. Before moving the servers in farm to the another network I've unplugged the single SharePoint server from the farm database for to clone it. Apparently
this disconnection removes all the implemented solutions and the farm remains without servers. Reconnecting the servers not re-implements the solutions. When I was about to create a new farm I have seen that all solutions were not implemented,
I have implemented one by one and the system worked again.
If any of you happen reaches you, now you know what it may be due.
Kind regards!! Now I'm a happy man! ;)

Sharepoint 2007 to Sharepoint 2010 migration

Hi,
Does Microsoft recommends/support below techniques for SharePoint 2007 to SharePoint 2010 migration?
Migrate SharePoint 2007 site to 2010 using save list as template technique: I use this technique. I have to delete all look up columns and add them again. Because I deleted all look up columns, I lost data of those columns. I am not able to update these
columns data using spreadsheet view copy and paste as those are look up columns. Please tell me what is the easy way to update these look up columns data. After I move it production again I have to do incremental update.
Migrate SharePoint 2007 site to 2010 using an Access table technique: This technique does not support all data types.
Migrate SharePoint 2007 site to 2010 using Power Shell STSADM command: As in my site there are some customization I am not able to migrate site using STSADM command. It is giving me errors.
Thanks,
Amit Khatri

hi
mentioned techniques can be used for copying the data across different web apps/farms within the same Sharepoint version (i.e. from SP2007 to SP2007 or from SP2010 to SP2010, but not from SP2007 to SP2010). If you need to perform upgrade from SP2007 to SP2010
you have 2 ways:
- in-place upgrade
- db attach upgrade
Check the following post for more details:
Upgrade single SPWeb from Sharepoint 2007 to 2010.
Blog - http://sadomovalex.blogspot.com
Dynamic CAML queries via C# - http://camlex.codeplex.com

Migrate the SharePoint 2007 Site containing SharePoint Designer Workflows with Infopath forms to SharePoint 2013

Hi,
We have a requirement to migrate the SharePoint 2007 Site containing SharePoint Designer Workflows with Info path forms to SharePoint 2013.
Can somebody please guide us as to what could be the best approach to go ahead?
Thanks in advance.
Regards,
Vijay

Use STSADM
backup and
restore to migrate SharePoint 2007 site
containing SharePoint Designer Workflows with Info path forms to SharePoint 2013.

What is the best way to migrate SharePoint 2007 to 2013?

HI All,
I would like to migrate SharePoint 2007 to 2013, may i know the easiest way to migrate? Thanks in advance

Hi,
“You cannot upgrade directly from the server products in the Office 2007 release to SharePoint 2013. The changes between versions are too great, and the hardware requirements differ so much between versions that a direct upgrade is not possible
or supported. However, you can perform a series of database-attach upgrades to first upgrade your content to SharePoint 2010 Products and then to SharePoint 2013. This article describes how to perform these sequential database-attach upgrades.”
Agree with Jesper, and here are the links for your reference:
http://blogs.msdn.com/b/ronalg/archive/2013/01/28/can-i-upgrade-from-sharepoint-2007-directly-to-sharepoint-2013.aspx
http://technet.microsoft.com/en-us/library/ee947141.aspx
Should you need more assistance, feel free to ask here.
Regards,
Rebecca Tu
TechNet Community Support

Remove bad dll reference after content data migration sharepoint 2007 - sharepoint 2010

I have 400 subsites under one root site and we need to remove one DLL reference from default.aspx Home page of each sub site.
Assmbly ref like this.
<%@ Register TagPrefix="WpNs0" Namespace="DS.DSQueryWebPart" Assembly="DS.DSQueryWebPart, Version=1.0.0.0, Culture=neutral, PublicKeyToken=709ed70a96eaa5cb"%>
This assmebly is not used anywhere .
This assembly is reflecting in subsite default.aspx after the content database migration sharepoint 2007 to sharepoint 2010.
Is there any way we can remove this bad reference through database query or any other way around
sarav

Hi,
If are sure that this is the only customization in the default.aspx page, then you can safely go into Site Settings -> Site Actions -> Reset to site definition -> Select Reset specific page to site definition version and enter the default.aspx
page url. This will replace the customized page with the original site definition page. The process can be automated using PowerShell/C# Code. Here is an example:
using (SPSite site = new SPSite("http://aissp2013/sites/Team/"))
foreach(SPWeb web in site.AllWebs)
using(web)
SPFile file = web.GetFile(web.Url + "/default.aspx");
if (file.Exists)
file.RevertContentStream();
The main part here is to get hold of the default.aspx file and use RevertContentStream() to reset it to site definition page.
However, if there are other customizations as well, then you will need to get hold of the Project or WSP file and remove the reference there and then run update-spsolution powershell command to update to new WSP.
Thanks,
Nadeem
Please remember to up-vote or mark the reply as answer if you find it helpful.

Delta migration on sharepoint 2007 to sharepoint 2010

To
SharePoint2010 Dear All ,
I am working on (SharePoint 2007 – SharePoint 2010 – SharePoint 2013) migration project . I need to do content database migration from one environment to another and many sites are suggesting the Content Database attach approach. It is working fine but doing
in production it’s taking more time minimum one week to complete this process.
I want to take the incremental backup of MOSS 2007 Content DB (only modified or newly added data )only with one week of updated data and restore in SharePoint 2010 and 2013 Environment .Kind of Delta migration.
Please advice on this.
sarav

If you want to do that the only approach I see is use a 3rd party product such as DocAve and Quest to do delta migrations.
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Sharepoint 2007 to 2010 Migration issue

Hi Techies,
I am doing migration from sharepoint 2007 to 2010,
I have restored the 2007 content DB to 2010 server,But the problem is during attachment of content DB to sharepoint 2010 web application,I am getting the database upgradation issue.
Please help to solve this issue.
Thanks Regards,
Simanchal Padhi

Hi Simanchal,
Could you please let me know what exact error you encountered while attachment of content DB?
By your question, I understand you are facing a database upgrade issue.
Have you run below command before you ran Mount-SPContentDatabase
command?
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Please remember to click 'Mark
as Answer' if the reply answers your query or 'Upvote' if it helps you.

How to migrate search configuration and db from SharePoint 2007 to SharePoint 2010

hi all
currently we have a plan to migrate sharepoint 2007 farm to sharepoint 2010 with sp2 version. we have used the ssp, and only the search function.
Now the search db is quite big.
we have to use the database attach way to do migraion, because the old system must be online in 24 hours per day.
what i want to know is can we migrate the search db directly instead of recreate content source and reconfigure the search and do full crawl?
thanks.

Hi,
Below links should help you
http://technet.microsoft.com/en-us/library/gg593614(v=office.14).aspx
http://msdn.microsoft.com/en-us/library/office/ff828776(v=office.14).aspx
http://www.orcsweb.com/blog/cory-granata/sharepoint2k7-to-2k10-migration-using-db-attach-method/
http://technet.microsoft.com/en-us/library/cc263403.aspx
Please remember to click 'Mark as Answer' on the answer if it helps you

Steps for Migration from SharePoint 2007 to SharePoint 2010?

Hi All,
Can any one tell the steps for migration from SharePoint 2007 to SharePoint 2010.
Thanks in advance!

This is the official communication:
http://technet.microsoft.com/en-us/library/cc263212.aspx
and this is a step by step guide:
Step by Step inplace upgrade to SP2010
Hope it helps!
Thanks, Ransher Singh, MCP, MCTS | Click Vote As Helpful if you think that post is helpful in responding your question click Mark As Answer, if you think that this is your answer for your question.

Post migration Nintex workflow isse (sharepoint 2007 to Sharepoint 2010)

SharePoint2010
Conversation Options
SG
SARAVANAN GAJENDRAN
SARAVANAN GAJENDRAN
To
SharePoint2010 Hi ,
I have migrated Nintex workflow from shrepoint 2007 to sharepoint 2010 after migration one of the workflow is not working .
I am getting the below error .please advise on this .
Tried to export the perticular workflow from sharepoint 2007 and imported in sharepoint 2010 .
Workflow Messages
Time Event Message Outcome
3/2/2015 7:33 AM Workflow Comment Document Creation (v1.60)
3/2/2015 7:33 AM Workflow Comment Error checking in item. The workflow failed because the action requires the document to be checked out. Error
3/2/2015 7:33 AM Error An error has occurred in Document Creation 1.
Please advise on this
sarav

Hi Sarav,
From the error message, it seems that it needs to check out the document first to make the workflow to be executed.
I recommend to check if “Require documents to be checked out before they can be edited” is set to Yes in the Versioning settings of the library where the workflow associated.
If yes, please set it to No and then run the workflow to see if the issue still occurs.
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Sharepoint 2007 Sharepoint Designer Workflow migrate to Sharepoint 2013

SharePoint 2007 sites migration to SharePoint 2013, in SP2007 I have several workflows created using SharePoint Designer. Is it possible to migrate those Workflows to SharePoint 2013? If so, is SharePoint 2013 Workflow
Manager needed to run those Workflows?
BTW, I will be using third party migration tools to migrate SP2007 content to SP2013.

Hi John
I know one third party tool which is best in migration and it migrates designer workflows also
http://en.share-gate.com/sharepoint-migration
http://en.share-gate.com/
Please mark it as answer if it helps you finding your answer
Amit Kotha

Migration from Sharepoint 2007 Website to Office 365

Hi Experts,
I am beginner of sharepoint and want to know the steps of migrating the Sharepoint 2007 website to Office 365.I have searched at google and found a lot of third part tools available in the market but i dont know which is better procedure,manual or by
some thrird party tool ?
Regards,
Lalit Narayan
India

Having been working on a very similar project for a good few months, I could probably write a novel on this.
First, forget about the tool, there's isn't a golden utility that'll do everything for you. This is due to the two generation gap between technologies and the move from on-premise to cloud. Simply throwing a tool at this and hoping it'll work
will cause you problems.
First, analyse your SP 2007 environment and work out what you think your pressure points will be. For us, there were plenty, such as: -
Custom workflows
Densly populated lists
Changes in functionality, content types and so on
Obsecure changes to web part functionality
You'll want to see HOW any tool you look at handles these issues. We ended up using Metalogix Content Matrix, which has a few troubles moving workflows and custom forms. In the end these were recreated manually.
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

Sharepoint 2007 migration

Similar Messages

Maybe you are looking for