I need my workflow to move library documents into a folder in the same document library. I can copy items, then delete the original item. I'm not seeing how to specify a folder or sub-folder, just the list itself. I'm just not seeing it (therefor it is probably right in front of my nose!)


If you use SharePoint 2010 designer, you can try to use this activity.

| improve this answer | |
  • While this looks like an EXCELLENT solution, I'm not sure how to implement. I'm assuming I need to have access to the Admin side of the SP farm? I have never tried to add anything like this ... I have asked our administrators for assistance, but have not gotten word back yet. I have looked at these two sites for assistance: Creating Custon Workflow Activity and Custom Activity Workflow – Pᴀᴜʟsᴛᴇʀ2 Jun 26 '13 at 14:11
  • 1
    @Paulster2, you need to install this activity and create workflow in SharePoint designer.For example you can look at this post – Alexander Jun 26 '13 at 14:25
  • I guess my follow-up question was not clear. I know how to create workflows ... I don't know how to install the activity. Sorry for any confusion. – Pᴀᴜʟsᴛᴇʀ2 Jun 26 '13 at 14:41
  • 1
    go to downloads. In the zip package you will find installation guide. – Alexander Jun 26 '13 at 16:06
  • 1
    this solution requires deployment to the farm. if you develop own solution you need to deploy it too. I do not have any proposal for you now ( – Alexander Jun 26 '13 at 18:41

I know this is an old thread, but after spending a good while looking about I found an OOTB SharePoint Designer 2010 solution for this problem.

To move a document to a different folder

  1. create an SPD2010 workflow and use the Update Item action to change the path and name of the document.
  2. After inserting the update list item action click on the "this list" link and set the dropdown to Current Item.
  3. Then click Add, select the "Path and Name" field click on the "...", type in your folder name followed by a /,
  4. then click "Add or Change Lookup", select Current Item as the data source and the field as Name.
  5. The stringbilder should then show yourfoldername/[%Current Item:Name] (where yourfoldername is relevant to the library root). Click OK and publish the workflow in the normal way.
  6. When you run the workflow it will move the doc to the specified folder.

Many thanks to Move items into a SharePoint list folder for this solution.

| improve this answer | |
  • can this be used to move documents between two different libraries?!?! – Josh Sharkey Jul 1 at 15:20

I don't understand why there is so much confusion about how to implement a custom workflow action (I'm confused as well). I found numerous guides on how to do this and they all required deployment to the GAC and registering smart controls in the Web.Config. I couldn't get this to work. Then I found a blog with steps on how to implement a custom action in a sandboxed solution (preferable for me anyway) and it was easy peasy. I created a workflow that takes an input parameter for the folder path from the workflow designer and moves the item to the folder. This thread is old, but I just want everyone to know this is super easy as a sandboxed solution. I used the below guide and just added my logic for moving to a folder. I recommend creating a list receiver that moves the items to a folder first because troubleshooting a list receiver is a thousand times easier than troubleshooting a workflow. So, validate your code in a list receiver then add it to the workflow based on the guide below.


| improve this answer | |
  • For me, if it involves creating an event receiver, it's no good. Because our farm/system is so closed down to external input, I cannot even add SP templates for Visual Studio onto our system, which is needed in order to create the event receiver in the first place. Ugly, ugly, ugly. Thanks for your input, as I believe it will help others in the future. Something you may want to do is actually input the steps here (duplicate your entry), so the information is not lost through a link change or something unforseen in the future. – Pᴀᴜʟsᴛᴇʀ2 Jul 16 '14 at 17:01
  • yes, I created an list receiver first, but a workflow action is more flexible as the conditions and parameters can be changed with recompiling and redeploying your solution. Again, this was done in a sandbox solution. It doesn't require deploying to the GAC. If you can deploy a list receiver, you should be able to deploy this custom action to the sandbox as well. – Duper508 Jul 18 '14 at 15:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.