Technical Background
Programming Languages
The IZ_Migration package is written using PL/SQL, its installation script uses Unix Shell. Shell script eases the initial setup, since the user can provide some information (such as storage paths and login data) before the execution of the SQL code. Finally, the tool itself is installed into the database as a package of stored procedures, and so it will be available independent from the client used to execute them exactly at the place where they are needed.
Requirements

The requirements can directly be derived from the above paragraph and the intended goal: First, you need an Oracle Database Server up and running, otherwise you won't need any of the IZ_Migration scripts :) Second, the instance(s) of this Database Server you want IZ_Migration to work on need to have PL/SQL installed, otherwise the package cannot be processed by them. And last but not least, you need a Unix Shell (the IZ_Migration installation script has been successfully tested with the Bash Shell). This does imply that the IZ_Migration installation script runs in *nix environments (Linux, Solaris, AIX, etc. - but it is not tested on all platforms, so reports are welcome). There are Shell environments available for Windows as well, like CygWin - but since I didn't test any scripts in those environments I cannot guarantee that they will run with those; again, reports are welcome.

In the worst case, if you are running Windows only you can take the Shell script and extract the SQL code from it. There are just very few variables to replace.

Limitations
These scripts have not been approved by a "beta tester team" or the like, so you should consider them still in beta stage. This may change if people like you work with the scripts and send me their reports - not only if they encounter problems, but also if everything works well. I'm always happy to receive reports on where my tools are running fine. This not only encourages a developer - it also helps the user who needs approvement. And if I can add in this documentation that the package has successfully been used by 187 users in 243 different environments, this may lower the fear of other ones thinking about it. Of course, if there are any errors/problems, you should report them as well - so either we can fix/solve them, or at least add a "troubleshooting" section to this documentation to help users identifying possible hazards in advance and work around them.