<p>I ended up doing this the old-fashioned way... <strong>hire cheap labor to do a tedious repetitious task!</strong></p>

<p>Every other suggestion I got (here and in Slack) involved command line scripting and/or careful database manipulation. I wasn't really comfortable with either of those, especially since I had already started the drag &amp; drop process.</p>

<p>So in the end, I just hired one of my buddies (for dirt cheap) to manually drag &amp; drop each folder to the new source. Problem solved! :)</p>

CC BY-SA 3.0
2015-09-17T20:54:46.000Z
Despite the fact that this actually solved my problem, I won't officially mark it as the correct answer. It's certainly atypical for a programmer to solve a problem this way, and it won't necessarily be the best solution for other folks who discover this thread.
Lindsey D
CC BY-SA 3.0
2015-09-17T20:53:24.267Z
2015-09-17T20:53:24.267Z
Lindsey D
<p>I did this with <a href="http://gruntjs.com/" rel="nofollow">grunt</a>, using the <a href="https://github.com/MathieuLoutre/grunt-aws-s3" rel="nofollow">grunt-aws-s3</a> task. It worked beautifully. If you are a <a href="http://gulpjs.com/" rel="nofollow">gulp</a> person, I'm sure there is something similar for gulp.</p>

CC BY-SA 3.0
2015-09-17T06:53:59.273Z
Interesting... and that maintained all of the asset relationships? Or did you have to reindex your assets?
Lindsey D
CC BY-SA 3.0
2015-09-17T07:19:27.253Z
I may have reindexed afterwards. But it got rid of the tedium of moving them.
Marion Newlevant
CC BY-SA 3.0
2015-09-17T07:23:49.430Z
Hmm, I don't think that's gonna work for me. I'm not bothered by physically moving them. I need to maintain the existing relationships between these assets and thousands of entries.
Lindsey D
CC BY-SA 3.0
2015-09-17T08:00:09.153Z
Maybe you can move them by just uploading all assets to S3 manually. Then in the database go in and change the "Asset ID" for the current selection of assets to your new "S3 Asset folder". Since the paths are the same... this might work.
naboovalley
CC BY-SA 3.0
2015-09-17T18:24:25.870Z
@naboovalley Very interesting! I'll test that out and let you know if it does the trick. Would you mind submitting that as a separate answer?
Lindsey D
CC BY-SA 3.0
2015-09-17T20:46:07.413Z
@naboovalley Disregard my previous comment... I ended up going a different route.
Lindsey D
CC BY-SA 3.0
2015-09-17T06:50:00.983Z
2015-09-17T06:50:00.983Z
Marion Newlevant
<p>I'm moving all of my assets from a local folder to Amazon S3. I've got my S3 source all set up, and I've been migrating folders over to it by dragging &amp; dropping.</p>

<p>The problem is, I have <strong>thousands</strong> of asset folders. I did the math, and it'll take me 4+ hours to drag &amp; drop each of them.</p>

<p><strong>Is there some way to bulk move asset folders?</strong></p>

<p>If it's not possible in the CP, I'm open to plugin suggestions as well.</p>

CC BY-SA 3.0
2015-09-17T23:25:00.843Z
I discovered the **right** answer way too late... For future reference, [this is the right way to do it...](http://craftcms.stackexchange.com/questions/1212/is-it-possible-to-move-an-entire-asset-source/1215#1215)
Lindsey D
CC BY-SA 3.0
2015-09-18T02:10:19.183Z
Bookmark and use the information in this link:

http://craftcms.stackexchange.com/questions/1212/is-it-possible-to-move-an-entire-asset-source/1215
andrew.welch
<assets><migration><sources>
Bulk moving asset folders, from one source to another
# Bulk moving asset folders, from one source to another

(Asked by: username_0 on 2015-09-17)

I'm moving all of my assets from a local folder to Amazon S3. I've got my S3 source all set up, and I've been migrating folders over to it by dragging & dropping.

The problem is, I have **thousands** of asset folders. I did the math, and it'll take me 4+ hours to drag & drop each of them.

**Is there some way to bulk move asset folders?**

If it's not possible in the CP, I'm open to plugin suggestions as well.

**Tags:** assets, migration, sources

> **Comments:**
> **username_0**: I discovered the **right** answer way too late... For future reference, [this is the right way to do it...](http://craftcms.stackexchange.com/questions/1212/is-it-possible-to-move-an-entire-asset-source/1215#1215)  
> **username_1**: Bookmark and use the information in this link:
 
 http://craftcms.stackexchange.com/questions/1212/is-it-possible-to-move-an-entire-asset-source/1215  

---

## 2 answers

### Answer by username_0 on 2015-09-17. Score: 1

I ended up doing this the old-fashioned way... **hire cheap labor to do a tedious repetitious task!**

Every other suggestion I got (here and in Slack) involved command line scripting and/or careful database manipulation. I wasn't really comfortable with either of those, especially since I had already started the drag & drop process.

So in the end, I just hired one of my buddies (for dirt cheap) to manually drag & drop each folder to the new source. Problem solved! :)

> **Comments:**
> **username_0**: Despite the fact that this actually solved my problem, I won't officially mark it as the correct answer. It's certainly atypical for a programmer to solve a problem this way, and it won't necessarily be the best solution for other folks who discover this thread.  

---

### Answer by username_2 on 2015-09-17. Score: 1

I did this with [grunt](http://gruntjs.com/), using the [grunt-aws-s3](https://github.com/MathieuLoutre/grunt-aws-s3) task. It worked beautifully. If you are a [gulp](http://gulpjs.com/) person, I'm sure there is something similar for gulp.

> **Comments:**
> **username_0**: Interesting... and that maintained all of the asset relationships? Or did you have to reindex your assets?  
> **username_2**: I may have reindexed afterwards. But it got rid of the tedium of moving them.  
> **username_0**: Hmm, I don't think that's gonna work for me. I'm not bothered by physically moving them. I need to maintain the existing relationships between these assets and thousands of entries.  
> **username_3**: Maybe you can move them by just uploading all assets to S3 manually. Then in the database go in and change the "Asset ID" for the current selection of assets to your new "S3 Asset folder". Since the paths are the same... this might work.  
> **username_0**: @username_3 Very interesting! I'll test that out and let you know if it does the trick. Would you mind submitting that as a separate answer?  
> **username_0**: @username_3 Disregard my previous comment... I ended up going a different route.  

---

