Currently there is no ability to check access rights on an entry without the use of a custom Script. This is not part of the initial questions but a very important consideration for some companies to be aware of if it's needed. I think it's fair to assume in this example that we have folders generated that inherit the rights from the parent folder/are the same as the other numbered folders as they are all meant to be used the same.

Kristina,

Look at the slightly less dark text underneath the activities. Miruna has done a fairly great job adding into the comments the information you seek in setting up the workflow like she has laid out. 

What the workflow Miruna is suggesting does is do a pattern match on the Entries path, to find the new path that you want to move the documents in. The starting Entry is any document inside a folder with a number at the end, or rather, you can publish the workflow and select the "Play" looking button in the top toolbar and select it to run on a folder and check the option for it to run on each entry that is in the folder. (Or set a similar rule in the Rule Manager).

After it has done the Pattern matching, you have a token with your new filepath. What you do from there is move this entry to its new filepath. 

Then you need to get rid of this potentially empty folder, but we need two activities for that. The first being to find the entries original folder using the "Find Parent Folder" activity. 

Once we have that, we can use the "Delete Entry" activity to clean up the repository, but setting the option for only deleting folders when they are empty will ensure we do not get rid of anything we shouldn't be deleting. 

If this is not clear at this point, I hope you can explain to us what is unclear so we can make sure to address that for you.