Need to upgrade service providers of Moss 2007 to SharePoint 2013

I have upgraded the Moss 2007 Content database via native approach into SharePoint 2013. I am wondering how we can upgrade the service providers of Moss 2007 to SharePoint 2013 service applications.
Regards Restless Spirit

Hi Restless,
According to your description, my understanding is that you want to upgrade the service providers of MOSS 2007 to SharePoint 2013 service application.
Per my knowledge, you need to firstly upgrade the service providers of moss 2007 to SharePoint 2010 via database content, then upgrade SharePoint 2010 service applications to SharePoint 2013.
There are some useful articles for your reference:
MOSS 2007 upgrade - Shared-Services Provider SSP migration and my sites
MOSS SharePoint 2007 SSP migration to SharePoint 2010
Upgrade service applications to SharePoint 2013
Best Regards,
Wendy
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]
Wendy Li
TechNet Community Support

Similar Messages

Migrating from Moss 2007 to SharePoint 2013

I am reaching out here as we require some inputs around migrating the SharePoint based application from MOSS 2007 to 2013.Please find more details from below
Requirement:
Migrating SharePoint site collection (which contains just 1 Top level site and 2 libraries with in it and no item level/library level permissions exists) which is on MOSS 2007 with size of 500GB to SharePoint 2013, hence we like to know your inputs in related
to this
Note:
1) The site collection has its own separate content database
2) There are nearly 200 thousand documents where the document with higher version is 90
3) The documents are stored in the libraries with up to third level of folder structure
4) The site collection is created based on custom site definition (created using visual studio)
Few things that I like to mention/ask here
a) Having 500GB data in one single content database inj the MOSS 2007 environment does it impacts the site performance?
b) Migrating the site collection as is onto single content database (all 500 GB into one content database) into destination SharePoint 2013, does it will be a good practice? Hope SharePoint 2013 content database limit is 200 GB, hence moving 500GB
as is into one database will it be good practice?
c) Does database attach and detach works for the databases which are of size 500GB?
d) Can we do database attach and detach directly from MOSS 2007 to directly onto SharePoint 2013, without hopping onto SharePoint 2010 in between and then later to SharePoint 2013?
e) If moving 500GB data into one content database will not be a good approach, can we split it onto multiple databases?
f) If database attach and detach doesn’t help for databases which are of size 500GB, should we go for any tool based approach? If yes, which tool does best fit?

a) Having 500GB data in one single content database inj the MOSS 2007 environment does it impacts
the site performance?
Inder: Yes, it will impact site performance at large extended, recommended is 200 gb only. Check it IO of your disk to analyze performance issue
b) Migrating the site collection as is onto single content database (all 500 GB into one content
database) into destination SharePoint 2013, does it will be a good practice? Hope SharePoint 2013 content database limit is 200 GB, hence moving 500GB as is into one database will it be good practice?
Inder:
Content database size (all usage scenarios)
4 TB per content database
Supported
Content databases of up to 4 TB are supported when the following requirements are met:
Disk sub-system performance of 0.25 IOPs per GB. 2 IOPs per GB is recommended for optimal performance.
You must have developed plans for high availability, disaster recovery, future capacity, and performance testing.
http://technet.microsoft.com/en-us/library/cc262787%28v=office.15%29.aspx#ContentDB
c) Does database attach and detach works for the databases which are of size 500GB?
Inder: Yes it does work
d) Can we do database attach and detach directly from MOSS 2007 to directly onto SharePoint 2013, without
hopping onto SharePoint 2010 in between and then later to SharePoint 2013?
Inder: No, you need to pass through 2010 and then 2013
e) If moving 500GB data into one content database will not be a good approach, can we split it onto
multiple databases?
Inder: you can go with 500 gb
f) If database attach and detach doesn’t help for databases which are of size 500GB, should we go for
any tool based approach? If yes, which tool does best fit
Inder: Below are few tools you can try
http://www.metalogix.com/Products/Content-Matrix.aspx
http://en.share-gate.com/
http://www.avepoint.com/sharepoint-migration-tools/
http://www.quest.com/sharepoint/migration.aspx
If this helped you resolve your issue, please mark it Answered

Migration steps for moss 2007 to sharepoint 2010 and sharepoint 2013

Hi,
I need to learn migration steps from moss 2007 to sharepoint 2010 and sharepoint 2013.Can any one please explain the step by step procedure for this.What are the migration tools available.Please reply.
Regards,
Praveen

Hi Praveen,
This link describes the process:
http://www.winwire.com/moss-2007-to-sharepoint-2013-migration-using-database-attach-method/
Some paid tools for migration:
https://www.harepoint.com/Products/HarePoint-Content-Workflow-Migrator/Default.aspx?gclid=CM2l1v3m28MCFRVxvAodpq0AVA
https://www.avepoint.com/sharepoint-migration-download/?gclid=CPK17_fm28MCFQ1xvAodekAA8w
Thanks,
Nadeem
Please remember to up-vote or mark the reply as answer if you find it helpful.

SharePoint 2007 to SharePoint 2013 Upgrade - Need to Goto SharePoint 2010 First?

All,
I've seen some posts that say one can go from SharePoint 2007 to SharePoint 2013 - without upgrading to SharePoint 2010. Other posts say otherwise.
Therefore, what is indeed the answer. Ideally I'm looking to stand-up a new SharePoint 2010 or SharePoint 2013 farm then likely do a detach then upgrade of the SharePoint 2007 content databases to SharePoint 2010 or 2013.
Thanks

If you want to do a standard SharePoint upgrade, yes you must go to SharePoint 2010 prior to 2013. If you want to use a 3rd part/in-house custom application content migration upgrade, then you can go straight from SharePoint 20xx to 2013.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Data Migration from MOSS 2007 to SharePoint 2010

Hi,
We have done a migration project for one of our client.
This migration was done from MOSS 2007 to SharePoint Enterprise Server 2010.
After the migration was completed we developed lot of new webparts, lists ,application pages in this newly migrated farm in SharePoint Enterprise Server 2010.
However the entire project took around 1 year due to some unavoidable delays. During this one year our client was using MOSS 2007 sites for there work. hence the data in MOSS 2007 farm/sites was continuously updated.
Our client needs to go live in next month and also needs the sites/lists/libraries which are migrated in new SP 2010 farm to be updated as per the MOSS 2007 farm.
Kindly suggest best possible way to achieve this data migration since last 1 year from MOSS 2007 to newly migrated SharePoint Enterprise Server 2010 farm.
Kindly note we have done lot of customization and new developments in newly created SP 2010 farm.
Thanks and regards,
Amien

Hi there,
If you have already taken care of customization on SP2010 server. Then use any of the migration tools available in market to migrate data to target SP server.
Content Matrix gives free 25 GB to migrate your SharePoint data (https://www.metalogix.com/Resources/Promotions/Content-Matrix-Migration-Express-Download.aspx).
If you don't know what is changed in last 1 year, then best thing to do is add new content database and migrate your data into it.
Hope that helps.
Regards,
Tapan

Migrate Infopath forms from MOSS 2007 to SharePoint 2010

Hi,
Please provide help
Migrate infopath 2007 forms in MOSS 2007 to SharePoint 2010

How many forms do you have that needs to migrate from 2007 to 2010?
You can also open the 2007 forms in Designer mode of InfoPath 2010, save as 2010 filler or browser.
You need to make sure data connections are updated to point to new sites/document libraries/lists etc.
Any custom code that may contain data connections should be updated.
Inspect Rule Inspector to see if you find any connections hardcoded anywhere.

Search not working in site collections migrated from MOSS 2007 to SharePoint Server 2013

I have few site collections migrated from MOSS 2007 to SharePoint Server 2013 using database attach (first to 2010 and then to 2013).
When I search for anything in these migrated sites, I get "Nothing here matches your search".
Checked the crawl log for these sites and see this error for all items.
The content processing component failed to process the security descriptor of the item. ( The input ACL is invalid (1210 / 2072).; ; SearchID =
Some-Random-GUID )
Search works fine in newly created sites in 2013 environment.
Please help.

Hello
Did you migrate your users to claims when you migrated the databases?
$wa = Get-SPWebApplication http://yourdom.com
$wa.MigrateUsers($true)
$wa.ProvisionGlobally()
I assume the sites that work and the migrated content are in the same database?
MCITP-EA | "Never test how deep the water is with both feet"

Losing out custom metadata info of few documents of a document librarby when migrated from MOSS 2007 to Sharepoint 2010

We have recently migrated from moss2007 to sharepoint 2010.We have a document library containing large no. of documents in it & for those documents there are some custom metadata columns apart from OOB library columns . We have user content DB attach
migration and after that we can see blank value under the custom columns for some records. However interesting point is we can see this metadata is showing for few documents.
Please suggest.

Hi,
What is your Office edition? When we create a managed metadata column in a Document Library, it will prompt that ‘Earlier versions of client programs might not support this type of column’. You should use Office 2010 to edit and create a document then save
to document library .
For detailed information ,please refer to this article:
http://rules.ssw.com.au/SoftwareDevelopment/RulesToBetterSharePoint/Pages/2010-Managed-Metadata-with-Office-2007.aspx
Beside, here are similar posts, you can use as a reference:
https://social.technet.microsoft.com/forums/sharepoint/en-US/1b115343-20e5-4962-af97-793194f07637/metadata-missing-when-revising-document
https://social.technet.microsoft.com/Forums/office/en-US/a65f9828-6e2f-4eb7-bde6-bd0600e3b1a2/migrating-documents-from-moss-2007-to-sharepoint-2010?forum=sharepointadminprevious
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Third party tools to upgrade sharepoint 2007 to sharepoint 2013

I'm looking for third party tools that can be used to upgrade sharepoint 2007 to sharepoint 2013. Any suggestions?
Thanks,
JohnWeb

Hi,
To migrate from 2007 to 2013 directly. I believe AvePoint and possibly Axceler have such products.
https://social.technet.microsoft.com/Forums/office/en-US/f46e4593-1283-4aec-bd63-564779883ac8/upgrade-moss2007-to-sharepoint-2013?forum=sharepointadmin
http://social.technet.microsoft.com/wiki/contents/articles/15743.sharepoint-2013-upgrading-from-sharepoint-2007-q-a.aspx
http://www.threewill.com/the-final-four-or-five-sharepoint-migration-tools/
Regards
Prasad Tandel

How to configure service endpoints of custom webservice in SharePoint 2013?

Hi,
I have created a custom webservice in SharePoint 2013. I placed it in a sub folder under the ISAPI folder. I followed the instructions of this article: http://msdn.microsoft.com/en-us/library/office/ff521581(v=office.14).aspx. The webservice works
great, however when I try to send a large file I get the message "413 Request entity is too large".
After some searching I found out that you can create a web.config in the subfolder and define the endpoints and bindings, after which I get an error that there is already an endpoint defined for the specified URI. I believe this has something to do with
the BasicHttpBindingServiceMetadataExchangeEndpointAttribute but I'm not sure.
Can anyone help me solve this issue?
Regards,
Sander

Hi,
According to your post, my understanding is that you want to configure service endpoints of custom webservice in SharePoint 2013.
Per my knowleadge, after you add a reference to Microsoft.SharePoint.Client.ServerRuntime, you can use the BasicHttpBindingServiceMetadataExchangeEndpointAttribute.
In VS go to the add reference and paste the following: C:\Windows\assembly\GAC_MSIL\Microsoft.SharePoint.Client.ServerRuntime.
In addition, please make sure you create the custom web service correctly.
For more information, you can refer to:
SharePoint 2013: Create a Custom WCF REST Service Hosted in SharePoint and Deployed
in a WSP
How to create Custom Web Service WCF (REST) in SharePoint 2013
Adding custom WCF services to a SharePoint 2013 farm solution using Visual Studio 2012
"BasicHttpBindingServiceMetadataExchangeEndpointAttribute" could not be found
Best Regards,
Linda Li
Linda Li
TechNet Community Support

How to upgrade the extended web application for FBA from MOSS 2007 to SharePoint 2010?

Hi All,
Currently my farm version is MOSS 2007 with SP3.
I have a web application on port 80, and is based on windows authentication, and i extend it on the port 90, and the authentication is FBA with SqlServer.
I know that SharePoint 2010 has a new claims based authentication, and in a single web application you can do both windows authentication and FBA.
Now i want to know, when i migrate the MOSS 2007 port 80 and port 90, which method should i choose?
1. in SharePoint 2010 farm, Create a classic based web application on port 80, and extend it on port 90, enable FBA on port 90. It is the same as MOSS 2007.
2. in SharePoint 2010 farm, Create a claims based web application, and enable both windows authentication and FBA.
Thanks.

FBA requires claims so you'll need to create a claims based web application. Whilst you might extend the site to give you a FBA portal the web application itself will have to be claims based.
I would definitely be looking at using a database attach upgrade path in your case to give you the opportunity for testing as moving between authentication providers can be painful.

Upgrade MOSS 2007 to SharePoint 2010

Hi,
I am doing an upgrade from MOSS 2007 SP2 to SharePoint 2010 SP1 by database attach method. I have three content databases named :-
I) WSS_A - 1 GB
II) WSS_B - 22 GB contains 50 lists (On Production database size is 120 GB)
III) WSS_C - 1 GB
Machine used to Upgrade :- 2 core processor & 12 GB RAM
Database WSS_A and WSS_C has been upgraded successfully. But WSS_B failing again & again with SQL-Exeception in the logs and on screen exception is "Action 4.0.5.0 of Microsoft.SharePoint.Upgrade.SPContent ........ to Rollback"
In the preupgrade check all the three database reports are green. Please let me know how to solve the issue..
Navdeep Madan
http://navdeep19.wordpress.com

Hi Navdeep,
I will suggest you to use ULS log viewer OR check upgrade log to see the root cause of this failure. Below are couple of things which can be checked in addition.
1. Normally such error indicates that you are out of disk space. Check the disk space and try it again.
2. Sometimes it’s due to that there is a hard limit set in SQL on the PRIMARY file group for that particula database.
I hope it helps.
MachPanel - Premium Cloud Automation Solution

Content movement from MOSS 2007 to SP 2013

Hi,
I have a site collection in MOSS, a site has a document library with OOB Approval workflow, and the library has documents too.
Now, I have requirement wherein I need to move the documents from Moss to SP 2013, and the document should persists the workflow state whatever was existing in MOSS.
Thanks
Senthu

ou 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
Follow below article:
http://technet.microsoft.com/en-us/library/ee947141.aspx

Move A Site From Moss 2007 To Sharepoint 2010

i have a site in sharepoint 2007 and i want to move it to a sharepoint 2010 server
not too sure what is the best method to do this ?
thanks

I landed in this thread because I had a similar need to Muthuvel's. I am wanting to bring over just one subsite out of several. My database in 2007 is around 7GB, and all I really want is just one site out of the many in it.
Ahmed's Ammar's steps were just right, and worked well for me in order to get the complete 7GB database over to SharePoint 2010, and later export\import that single site I was looking for.
For Muthuvel, here are my updated steps, starting with Ahmed's text (sorry for plagiarizing!). Steps 7 and 9 are for subsites. See links at the bottom for dealing with site collections.
1) Find the content Database; These are listed under Central Admin->Application Management->Site Collection List
2) Backup the content database. Just doing a backup in SQL Server Management studio.
3) Restore content database to the new server, I mean the DB server for your SP2010
Copy the BAK file to new server. Create an empty DB in Management Studio, restore from backup, you may need to change an option in the "options" tab of the restore dialog to get it to work. (Overwrite db).
4) Create a new Web App on SharePoint 2010
For Step 4, I created a new Web App, choosing to create it with a suggested port number, such as 4072. This was a temporary web application that I ended up deleting later.
5) Remove Content Database from the new web app.
I didn't find that you neeed to remove the Content Database first. You can add the content database by Central Admin or by STSADM, or by Powershell.
Central Admin would be Application Management > Web Applications > Manage Content DAtabases > Set the web application to your newly created web app > Add Content Database > specify the name of the database you just restored
STSADM is as Ahmed gave:
Now use STSADM to add restored DB to this web app
c:\program files\common files\microsoft shared\web server extentions\14\bin on new server is where you can find the STSADM.
run this command from there. Which will upgrade the content db to 2010?
stsadm -o addcontentdb -url http://yourwebapp:port -databasename yourcontentdb -databaseserver yoursqlserver
Powershell would be this command below. Be sure to run the "SharePoint 2010 Management Powershell" console, found under Programs\SharePoint 2010 Products. If you run just regular powershell this won't work.
Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication
http://sitename:port
6) Run ISSRESET from command prompt
I'm not sure this was necessary, but I did it anyway.
NOW, the rest of the part about getting that subsite you want.
7) Export the subsite. I did this with Powershell.
Export-SPWeb http://sitename:port/sites/subsitename –Path "subsitename.cmp"
8) Create a new site for you to import this subsite into, in the Web Application where you want it to go. This would be done with the regular Site Actions > New Site command. You can also do it from Powershell, but that requires knowing
site templates by name, something I'm just learning myself. The other thing here is that you have to create the subsite using the same template as the site you just exported. So if that was a Team site, be sure to use a team site when you create
this new area.
9) Import the subsite to where you want it to land permanently. Here I'm saying port 80 because that's the requirement Muthuvel mentioned.
Import-SPWeb http://sitename:80 –Path "subsitename.cmp" -Overwrite
10) Even after things say they are done on the server, the site may take an extra minute or two to come up when testing from a client. Give it a little time. Once it comes up, somehow I found a way to change the visual appearance from the old SharePoint
2007 to SharePoint 2010, but now that I flipped that switch, I can't find the option again. So I'm sorry that I am not documenting that here.
11) Delete that temporary web app you created in step 4. Again you can do this with Central Admin or Powershell. Here's the Central Admin way:
Central Admin would be Application Management > Web Applications > Manage Web Applications, land on the temporary web app, click Delete. Choose Yes to deleting the content database and the IIS web site.
GROAN!! I'm sorry, I just wrote all this out and realized Muthuvel was asking about a site collection, not a subsite. Then for Steps 7 and 9 you'd want to use
Backup-SPSite
http://technet.microsoft.com/en-us/library/ee748617.aspx
and
Restore-SPSite
http://technet.microsoft.com/en-us/library/ee748655.aspx
Good luck, hope someone else finds this as useful as I did!
Lady_M MCITP SharePoint 2010

Migrate Sharepoint 2007 to sharepoint 2013 questions

I am in the process of moving sp 2007 to 2013 using db attach/detach. I have some questions.
1) Should I do visual upgrade in 2010, then migrate to 2013 or wait until 2013 and do visual upgrade?
2) Should I convert to Claim in 2010, then migrate to 2013 or wait until migrate to 2013 then convert to claim.
3) What happen if i attached db that was ntlm to web application that currently use use claim?
4) any good article show step by step and things to look for?

1) You must do the visual upgrade to 2010 prior to migration to 2013. SharePoint 2013 does not support the 2007 UI look and feel.
2) Personally, I convert to Claims in SharePoint 2013. Given you're running 2013 SP1 with the April 2014 CU (I recommend Sept 2014 CU) or higher, the conversion will be quicker.
3) Windows Claims is just NTLM or Kerberos. You would need to re-covert. If you're converting in 2013, after you attach the Windows Classic-enabled db to the Claims-enabled web application, you would run Convert-SPWebApplication.
http://technet.microsoft.com/en-us/library/cc263299(v=office.15).aspx
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Need to upgrade service providers of Moss 2007 to SharePoint 2013

Similar Messages

Maybe you are looking for