Remember that LR does non-destructive editing. That means the files you're working on aren't actually being changed by LR. The "changes" you make to the images as you work on them recorded as data in the catalog but are not applied to the image file itself on disk. When you export that image or print it, the changes to it recorded in the database are applied to the copy exported or as it goes to the printer but the image file in storage on the disk is the same as when you first captured it into LR. Development changes are stored in the database but not written to the image itself so the files you're copying will NOT reflect any development work you've done in LR when you view them in some other program. If you think about your workflow, you might find that some of the steps of putting the image in a working folder for editing, then subsequently moving to a storage folder when they're fully 'cooked' are unnecessary. If you're going to work in LR for the entire process, place the files into their permanent online location as you bring them into LR as they come off the camera or card, with a backup copy stored offline. Next batch to import, create the new folder where these files are going to live permanently and send them directly there during the first import. If you've already made a backup of the originals during the import process, there's no reason to have one folder where you store them as they are developed and another folder to move them to once editing is completed. Put them in the folder that's to be their permanent home right from the get-go and be done with it.
