The dbunload utility copies everything... tables, views, procedures, functions, triggers, user ids, passwords, database options, everything. The technique shown here results in a Version 11 database with all of the functionality of the original version 5.5 database: http://sqlanywhere-forum.sap.com/questions/574/how-do-i-upgrade-a-version-5-5-database-to-version-11

Now, the technique may fail in certain rare cases, especially when dealing with such a large leap and so many behavior changes. My "favorites" are undiagnosed validity errors in the source database. Exceptions thrown by dbunload need to be dealt with on a case by case basis.

Also, applications may no longer work properly because of behavior changes... that's why every single bit of the "Behavior Changes" documentation in the Help, from Version 6.0.0 to 11.0.1, must be studied carefully to see what action must be taken. It's a boring task, especially when it blathers on about later changes to features that didn't exist in 5.5, but ya gotta do it.