New answers tagged

0

What kind of performance issue you are seeing, did you check your 2013 farm, i.e ram usages, database performance, are u using the Cache i.e object cache? There are many things which can cause the upgrade Performance issue. Orphan items /List/ Sites Orphan Users and others Cache Settings Solution / Customization deployed in 2007( not compatibile to 2013) ...


0

You may also get help from this blog for migrating SharePoint on-premises to SharePoint Online natively, which involves usage of Azure Storage: http://sharepoint-content-migration.blogspot.in/2016/05/a-4-step-guide-for-migrating-sharepoint.html


0

The key in a SharePoint migration are the customs. When SharePoint does not have customs, migration is almost trivial and can take hours or days. When you have customs, it may take weeks or months. What kind of customs may exist? Branding (master page and CSS) Client side (client object model) SharePoint designer Server Side With Visual Studio (event ...


0

Its depends on, Every company is different. if you ask 3rd party consultant company if they place their migration expert then they charge you per hour(they calculate the hours in advance as per the amount of Data). As per our recent experience, Metalogix charge you for the amount of data while ShareGate is charge you for the number of users(who will perform ...


0

IMHO calculating a migration based solely on data size is ridiculous. If your farm is vanilla SharePoint, i.e. zero customizations, migration is "trivial", you just install SP2016, restore your content and service app data DBs on the new DB Server and attach them to the new ShareePoint farm. Barring any use of functionality made obsolete in SP2016 you ...


2

It is a site collection level feature so you can not do it on site-level. Site Collection Upgrade: One the benefits of upgrading to SharePoint 2013 is that it all happens behind the scenes. This means that your site collection administrators can upgrade the look and feel – not to mention, handle the change management – on their own ...


0

Apart of the customization's you have done with your SharePoint, no need to copy any element from 12 hive. Simply install SharePoint on new server and follow the same steps you mentioned (backup/restore database and then reattach to SharePoint). In case you have any customization's in SharePoint (i.e custom solutions, web parts etc), you have to deploy the ...


0

The solution I eventually found combined the SharePoint REST API, web services (as suggested by this answer) and a cunning Python script. It worked a treat. I requested a list of files in the library using the REST API endpoint https://example.sharepoint.com/_api/web/getFolderByServerRelativeUrl('/Test Library')/Files, then looped through each result, ...



Top 50 recent answers are included