Dependency Walker

http://www.johanpaul.com/blog/2011/07/deploying-qt-and-qt-quick-applications-on-windows/

http://www.dependencywalker.com/

I first recommend you to install a great tool for figuring out the required .dll files that you need to include in your package: Windows Dependency Walker. It's a neat free utility that will create a hierarchical tree of the .dll dependencies that an application uses. When you run your application, in the machine that has Qt installed on it, through Dependency Walker you can easily see which Qt .dll files it uses and you need to package with your application.If  you are curious, you'll find that Dependency Walker will show you a lot more information about what  methods the application used and from which .dll file, which methods are available in the .dll but were not used and a lot more detailed information about each .dll that the application loaded.

When you run your application through Dependency Walker on the machine that does not have Qt installed on it and when it did not run as expected, you can then see which .dll files your app failed to find. This is really a life saver when it comes to application deployment for Windows.

A word on warning, though. Dependency Walker is really good at finding libraries that your application is dynamically linked against. But it will not spot issues when it comes to Qt plugins. If a plugin is not found, there will not be any trace of it in Dependency Walker since Qt will just inform the app that this plugin is not available. So it is important to understand which plugins Qt will need and Dependency Walker cannot help you here.