We changed our privacy policy. Read more.

Hot answers tagged

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 ...


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


6

public void CopyDocuments(string srcUrl, string destUrl, string destLibrary) { ClientContext srcContext = new ClientContext(srcUrl); ClientContext destContext = new ClientContext(destUrl); Web srcWeb = srcContext.Web; List srcList = srcWeb.Lists.GetByTitle(srcLibrary); Web destWeb = ...


5

Thanks for the help with this, though for my use case the answer was a bit more simple. Here is the code I used to move files from one document library to another (on the same web) function moveFiles(sourceLib, destLib){ var context = new SP.ClientContext.get_current(); var web = context.get_web(); var folderSrc = web.getFolderByServerRelativeUrl(sourceLib)...


4

You can move document sets either by using "Manage Content and Structure". Make sure use "Move To" actions in that, don't use copy, it will move document sets to another library without changing its document id. Another way is to do programmatically, in that case consider document sets as folder to move into another library where Migrate1 is document set ...


4

Use following code to copy documents : public static void CopyDocuments(string srcUrl, string destUrl, string srcLibrary, string destLibrary, Login _login) { // set up the src client SP.ClientContext srcContext = new SP.ClientContext(srcUrl); srcContext.AuthenticationMode = SP.ClientAuthenticationMode.FormsAuthentication; ...


4

You can open this library in explorer mode (works on in IE) ==> Then cut the files from the PDF_Files folder and paste it one level up , just like in normal windows folder.


3

As you said you can use the command Move-SPSite on more site collection. Select the site collection (by matching the url) and then move them. Get-SPSite -Limit All | Where-Object {$_.Url -match "mySiteName" -or $_.Url -march "mySiteName1" } | Move-SPSite -DestinationDatabase ContentDb2 To create a new content DB, you can use New-SPContentDatabase New-...


3

Here is a script which copies documents across site collection http://blogs.msdn.com/b/rcormier/archive/2012/11/16/how-to-copy-sharepoint-documents-between-site-collections-using-powershell.aspx $ver = $host | select version if($Ver.version.major -gt 1) {$Host.Runspace.ThreadOptions = "ReuseThread"} if(!(Get-PSSnapin Microsoft.SharePoint.PowerShell -ea 0)) ...


3

I did not see any drawbacks as in this method all your versioning and metadata field preserve. Only thing i found you cannot move the folder or list itself. You have to create blank list and then move the items. http://blog.henryong.com/2008/01/21/how-to-movemigrate-sharepoint-list-itemsdocuments-and-preserve-metadata-properties-at-the-same-time/ Another ...


3

When you run the move command it will preserve all the ids. It is a simple move operation from one db to the other. I always recommend that you perform a test in lower environment and check after it.


3

Use Backup-SPSite/Restore-SPSite. This method will generate a new Site ID for the restored site so you can use it within the same farm (sites within farms must have unique IDs).


3

You have tree options to do: Solution 1- Using content and structure page to move files with version and metadata: Go to Site setting-->Click 'Content and Structure' link under Administration section Pick the items/files to be moved, Click on Actions >> Move Select the target list or library and click "OK" to complete move operation. Solution 2- Move ...


2

#region global variables SPListItem item_disp; SPWeb source_web; SPWeb destination_web; bool flag1 = false; bool flag2 = false; #endregion protected void Page_Load(object sender, EventArgs e) { using (SPSite site = new SPSite(SPContext.Current.Site.Url)) { try { foreach(...


2

Add a hidden field in the destination list. Name it MovedBy and set default value to empty. Make this field hidden so normal user will not see this. On Workflow A, when you move the document set the field MovedBy to WorkflowA. Now to identify the documents you just need to look into the field MovedBy


2

Well the simplest and easiest solution would be to go to Computer > Add Network Location and copy-paste the address of the List (address can be found in the List's Settings). Reapeat for the other list as well. Now you have two folder shortcuts pointing to the contents of each list, on your SP Server. From then on it's simple cut and paste from one folder ...


2

1 - The Move-SPSite cmdlet moves the data in the specified site collection from its current content database to the content database specified by the DestinationDatabase parameter. A no-access lock is applied to the site collection to prevent users from altering data within the site collection while the move is taking place. Once the move is complete, the ...


2

try this way, i am sure it will work. $user = Get-SPUser -web http://my.website.url -Identity "OLD_DOMAIN\OLD_USERNAME" Move-SPUser -IgnoreSID -Identity $user -NewAlias 'NEW_DOMAIN\NEW_USERNAME'


2

A no-access lock is applied to the site collection to prevent users from altering data within the site collection while the move is taking place. Reference : https://technet.microsoft.com/en-us/library/ff607915.aspx


2

from the error, its looks like you are moving a subsite not a site collection. Move-spsite only works with site collections and it Moves site collections from one content database to another. for verification you can run get-spsite "intranet/depts/research" and see if it returns an error or site id.


2

I figured it out. You can use SPFile to check if the file exist in the library and then move it if it does. SPFile file = site.GetFile("/Final Candidates/" + CName); if (file.Exists) { file.MoveTo("Draft Candidates/" + CName, true); } Reference: https://stackoverflow.com/questions/359672/how-to-determine-if-a-file-exists-in-a-sharepoint-spfolder


2

Alternate approach, SharePoint has"Manage content and Structure" that lets you to move files/list items. Please see reference link here http://community.bamboosolutions.com/blogs/sharepoint-2013/archive/2013/07/29/how-to-use-the-site-content-and-structure-manager-in-sharepoint-2013.aspx http://mroffice365.com/2013/05/sharepoint-2013-manage-content-and-...


2

You can do this: Go to Site Settings. Under Site Administration, you have Site Content and Structure Create a folder named "Folder1" inside your destination folder/library. Open your source folder which is "Folder1", check all contents and click on Actions, from there select MOVE and choose your desination folder which is "Folder2". You don't need any ...


2

Yes, Move To is currently only available within the same document library. You can also move by dragging and dropping files to a sub-folder. Microsoft has earlier announced support for move across sites. I quote "Finally, we will also add the ability to move files, as well as copy files, among SharePoint Team sites as well as OneDrive sources." I have not ...


2

If you mean to move a site from one site collection to another, there is no 100% "safe" way. Easiest: use a 3rd party tool, such as ShareGate. These tools turn this job into a couple of mouse clicks. However, it's still not "safe", as the following can still come up: JavaScript with hard-coded paths Workflows with hard-coded paths, in email actions for ...


2

When a file is assigned to a content type, the metadata was linked to the file and not the library. The Content Type must be on the destination Library. You had to first add the Content Type to the new library in order not to lose the metadata. Then you can move your files without getting this warning. Reference: Moving files between libraries removes ...


2

You need update folder metadata for the root folders after run the MoveTo method, modify the code as below. if (currentItem.ContentType.Name.ToLower().Contains("project")) { Console.WriteLine(currentItem["ID"]); SPFolder folder = omsWeb.GetFolder(omsWeb.ServerRelativeUrl + "/Shared Documents/"+currentItem["ID"].ToString()); var modified = folder....


2

Amending this path “/_layouts/15/sitemanager.aspx” at the end site collection URL. Then you can move site pages:


1

I and my co-worker found that it works better when you pipe Get-SPUser into Move-SPUser: Get-SPUser -web http://siteURL -Identity "DomainA\UserA" | Move-SPUser -IgnoreSID -NewAlias "DomainB\UserB"


1

From an administrative and cost savings perspective, this makes total sense. I'd try make sure that each of the old farms has their own host name to give them the feeling nothing has changed regardless of where the farm and content resides. The biggest barrier that you said is really the organizational and political aspect. It is technically possibly to ...


Only top voted, non community-wiki answers of a minimum length are eligible