To build the UWC use ANT (http://ant.apache.org/):
Note: you do not need to build the UWC to run it; only if you're doing development work with it.
To run the newly built UWC
mvn install:install-file -DgroupId=com.atlassian.confluence \ -DartifactId=confluence-xmlrpc \ -Dversion=5.2.0 \ -Dfile=lib/confluence-xmlrpc-wrapper-v5.2.0.jar \ -Dpackaging=jar mvn install:install-file -DgroupId=net.antonioshome.swing \ -DartifactId=treewrapper \ -Dversion=220.127.116.11 \ -Dfile=lib/treewrapper.jar \ -Dpackaging=jar mvn install:install-file -DgroupId=org.jvnet.substance \ -DartifactId=substance \ -Dversion=2.3final \ -Dfile=lib/substance.jar \ -Dpackaging=jar
More details and documentation is here: https://migrations.atlassian.net/wiki/display/UWC/Universal+Wiki+Converter
This code is open source and is up to date with Atlassian's latest storage format of Atlassian Confluence (introduced in Confluence 4). We successfully use/run the UWC for Confluence 5.X releases, however, there are many flavors and versions of MIGRATE_FROM wikis.
As such, we feel it is accurate to say that this is “a tool”, yet not always the end-to-end solution or silver bullet. Wiki formats are varied, and so please understand that the UWC will get you further along, but there may be post-processing, additional scripting, username database merging, or other things required to assist in the process.
Please refer to the Wiki Migration Checklist (http://www.appfusions.com/display/Dashboard/Wiki+Migration+Checklist) to educate yourself on what is invoived in a migration. The checklist is not to suggest that all content elements are problematic. They aren't. But some are, and not always the same between different flavors of wikis that are being migrated from.
We do provide paid ongoing small and big support for migrations, depending on needs. Email us at firstname.lastname@example.org and let us know what you are trying to do and we can see if we can help you! We have many client references too.