[SalesForce] How to deploy “Organization Business Hours” from one sandbox to another sandbox

I hope I have understood your requirement correctly here, but I would personally just copy the files that I wanted to deploy from the archived folder, into their respective folder on the operating system that the new project is deployed to. In Eclipse you can find out where the workspace folder is by selecting "Properties" from the right hand click context menu on the project name in the navigator, and then select "Resource":

Head over to this folder and copy in the "right" or "new" versions of the files you want into their relevant subfolders. New files will of course just copy, most operating systems will warn you of a file replacement.

Then in Eclipse, click on the new project title, and hit F5 to refresh it (or select Refresh from the right click context menu) this will re-scan the source folders for these changes. Once the project has pulled in all the new and updated files, you can "Deploy" the files to the server.

You can either whip through and select all the changed files by hand and then right click, and from the "Force.com" menu select "Deploy to Server" and then follow the easy deployment wizard.

or you can just right click on the project title and select the same deploy option and follow the wizard through.

This will push the local copies of the files up to the new Sandbox, and I hope, that is what you are trying to do?

Disclaimer: I work for Gearset.

You could use Gearset (http://gearset.com) - we built it for exactly this purpose! We do several things around tracking and migrating changes between orgs that might help in this scenario:

• Daily scheduled comparisons to show org changes over time (great for auditing changes that have happened to an org since you last "refreshed", to catch those pesky production hot-fixes, etc.)
• Comparisons with a deep understanding of the metadata (not just a straight xml diff - we break apart profiles into the constituent permissions, for example, and we do some dependency analysis to catch failures before you push a deployment)
• Some batching in our API requests to avoid hitting the API limits
• Really simple UI for picking changes that you want to deploy, from arbitrary org to arbitrary org (we use the metadata API behind the scenes - we automatically build the package.xml, destrictiveChanges.xml and the deployment package for you)
• Full history of all of your deployments, including the actual deployment package zip files themselves for download

There are other features too, but those seem like the most helpful based on what you've asked. There's a free 30-day trial, we use oauth and you don't have to install anything in your org, so you can give it a go absolutely risk free. I hope that helps, and good luck! :)