16
I'm going to go over this in a bit more detail, because none of the above answers were clear to me.
How to Move a SharePoint List from One Site to Another
1. Go the the List Settings of the list you want to move
2. Click Save list as template
3. Give the list template a descriptive file name, template name, and description
4. Go to the site's List ...
13
First of all, you should be aware of The new Microsoft SharePoint Migration Tool doesn't support SharePoint 2010 yet, it only supports SharePoint 2013.
Ref: Check the MSFT reply on 15/11/2017 (Planned to be supported in the future).
So, if you need to use The new Microsoft SharePoint Migration Tool, you will need to first migrate from SharePoint 2010 to ...
answered Dec 16 '17 at 9:57
12
The Content and Structure worked fine for me. Moving individual documents from one library to another captures all versions. Assuming, of course, versioning is configured the same on both libraries. That bit me the first time - the destination had Major, but the source had Major/Minor. Once the destination was switched to Major/Minor, documents came over ...
11
The critical component when failing over a Workflow Farm to a New SharePoint Farm (In the same domain or otherwise) is that the new SharePoint Farm must have the same Realm as the original one. Realm is by default identical to the SharePoint Farm ID, but can be changed using Set-SPAuthenticationRealm -Realm FarmIDoftheOriginalFarm.
Few Caveats:
You will ...
8
I know this is old, but I was also frustrated, that nobody had done this before. I decided to write my migration script in powershell. If you ever need something like this again, give it a try: http://memyselfandbenchase.blogspot.de/2015/07/migrate-your-wordpress-blog-to.html
Hope it helps someone else.
Here is the script. Sorry that it is so long.
#...
8
Unfortunately, you have to migrate to 2013 first. The only ways to do it directly ie skipping 2013 is by doing it manually or by using some third party tool or building a tool by yourself.
See this official Microsoft Post
Extract from above Post.
Upgrade and Migration
SharePoint Server 2016 will support upgrade from
SharePoint Server 2013. To upgrade from ...
7
The Metalogix has a very cool tool. With this tool you can migrate lists, sites, libraries and others items.
Refer to Content Matrix Product Page
Also refer to Introducing Content Matrix Console - SharePoint Edition
7
The best approach IMO would be to:
Setup the new server with OS and SP
Launch the SP configuration Wizard on this new server
Make it join the existing farm, i.e. make it point to the same config DB (and obviously same SQL server) as the first Web-front.
Don't forget to choose to host the Central Admin on this new server (you're asked for this during ...
7
You will have to run a STSADM script to move users from the OLD-AD to the NEW-AD, like this:
STSADM –o migrateuser –oldlogin OLDDOMAIN\user1 –newlogin
NEWDOMAIN\user1 –ignoresidhistory
This will do just fine on SharePoint Foundation. But if you have a User Profile Service Application, you may run into trouble. My experience tells me it doesn't work ...
7
Couple of things can change the database size.
If There is any unused or white space inside the content database then during the backup and restore method database automatically shrink it.
If there is any orphan items inside the content db then during db restore method it may clear those.
There are possibility that you deleted data in SharePoint 2013 or may ...
6
For future reference: there's a legacy API used by SharePoint Designer, called FrontPage RPC, and there's a bunch of methods, including move document that accepts a put_option parameter with migrationsemantics flag to preserve the information about who created a document, who modified it, and when it was created, and this could be used from advanced workflow ...
answered Dec 29 '14 at 15:54
Alexey Krasheninnikov
2,7602 gold badges22 silver badges42 bronze badges
6
I always employ the drag and drop method suggested by Tom. Easiest enough for my end users to do themselves and I still have the version history.
6
I found it. The missing DLL was in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.ServerRuntime.dll
But wasn't registered on VS, so you need to manually browse to the file.
6
I can show how to get this using JavaScript and REST:
$.ajax({
url: _spPageContextInfo.webAbsoluteUrl + "/_api/web/RoleDefinitions/getByName('Contribute')",
async: false,
headers: {
'accept': 'application/json;odata=nometadata'
},
complete: function (request) {
var basePermissions = new SP.BasePermissions();
...
5
Our method was uploading the infopath form to the destination libary and deselecting "Enable this form to be filled out by using a browser". This way the content types in the from library matched the content types in the to library.
5
Using Export and Import, you can migrate list from SP 2010 to SP 2013 but you have to make some manual changes.
Export the list from SharePoint 2010 using either the Central Administration or PowerShell (Export-SPWeb). In the Central Administration, go to Backup and Restore > Export a site or list. Choose your list, and click Start Export
Copy the exported ...
5
Their are couple of ways to download the documents from SharePoint Document library.
Using the Explorer view, you can drag and drop the documents to local directory.
UNC mapping to the SharePoint document library and drag/drop documents to a file share. You could refer this blog for details. This is simplest way but it will not display files that exceed the ...
5
Set the DocumentSet.Folder.Item.ProgId to "SharePoint.DocumentSet". Right now it will be empty. See this for more information:
http://www.sharepointnadeem.com/2011/08/sharepoint-2010-document-sets.html
UPDATE
Here is the sample PowerShell code. I haven't however tested it:
$web = Get-SPWeb http://yoursite
$list = $web.Lists["YourList"]
$docSetName = "...
5
In reality, no. You will need a content migration tool to effectively do this without loss of data fidelity or metadata. For example, if you were to copy documents using the Explorer view, you would lose the modified time, who the document was created by, and so forth.
5
The available option to move subsite in SharePoint Foundation is using Import-SPWeb/Export-SPWeb Cmdlets.
Export-SPWeb CMDLET
Export-SPWeb http://site -Path "site export.cmp"
Import-SPWeb CMDLET
Import-SPWeb http://site -Path export.cmp -UpdateVersions Overwrite
Note: You should be aware of Exporting / Importing site does not preserve workflows, ...
answered Jul 7 '17 at 21:53
5
First, you should be aware of the SharePoint 2007 (MOSS) is not supported edition for upgrading to SharePoint 2013! So you must
Migrate from SP 2007 to SP 2010.
Then Migrate from SP 2010 to SP 2013.
For more details check, Review supported editions and products for upgrading to SharePoint 2013
Second, to know What can be migrated and what cannot be ...
answered Oct 10 '17 at 11:44
5
The approach for this scenario is: don't. None of what you're suggesting is supported.
Instead, build a new farm and restore the Content Databases/Service Application databases.
5
Your best option is to move the site collection you want to migrate into it's own content DB with the Move-spsite command. Then use the DB attach method to migrate the site. Another option would be to use a third party tool, like ShareGate or Metalogix Content Matrix to migrate the site collection.
4
Migration of controls developed using custom code has always been a problem, not when you migrate to newer versions but also when you move them to another server or on another farm.
The only reason "I KNOW OF or Experienced" Site Definitions create problems while migrating is because they can have different components in them, so when you deploy them to a ...
4
You cannot migrate from 2007 to 2013. You need to migrate to 2010 first and then migrate to 2013. More on this :-
http://technet.microsoft.com/en-us/library/cc262483(v=office.15).
4
There's a new solution in Office 365.
You can now select a file or group of files in the modern experience in OneDrive or SharePoint and select Move to. A file or group of files moved this way will retain version history.
This change is currently marked "Rolling Out" on the Office 365 Roadmap and their are more details about the roll-out schedule on the ...
4
//To move file from source library to destination through Event handler
SPFile sourceFile = properties.ListItem.File;
SPFile destFile = null;
SPUser userCreatedBy = sourceFile.Author;
DateTime dateCreatedOn = sourceFile.TimeCreated.ToLocalTime();
int countVersions = properties.ListItem.File.Versions.Count;
for (int i = 0; i <= countVersions; i++)
{
...
4
Migration of the SSP is not required. In many cases I had clients that were not really using the user profiles extensively in 2007 so in those cases we configured a user profile service fresh and did not upgrade the SSP.
The things to think about that could be lost are:
Custom User Profile Properties that were defined; they would have to be defined again.
...
4
Are you missing custom solutions in your new 2010 farm, that exist in the 2007 farm? Compare the installed features/solutions in both farms.
However, you really should upgrade to SP2. The preupgradecheck stsadm command was added in SP2 and is very good at identifying where you're going to have issues. The upgrade alone may even solve your problems.
4
To upgrade from SharePoint 2010 Products to SharePoint 2013, you use the database-attach method to upgrade. In the database-attach method, you first create and configure a SharePoint 2013 farm. Then you copy the content and service application databases from the SharePoint 2010 Products farm, and then attach and upgrade the databases. This upgrades the data ...
Only top voted, non community-wiki answers of a minimum length are eligible
