Moodle 1.6
If you have third party modules installed, not ready yet for Unicode migration, you'll be warned about these on this page. Go back and disable them or seek a later version. The migration script can only run once, so if have problematic thirth party modules disabled here, you will have to use another method to get the data migrated to utf8.
If you run your site in one language only, select this option to save a lot of time on the migration. Otherwise, Moodle will figure out how to do the migration for every piece of data based on the language of the user, course and your Moodle site.
Since the migration is a process which causes heavy processor and disk load and can take a long time to perform, you should choose the moment of the upgrade carefully. For an indication, Moodle.org had about 3 million bits of text and took 2.5 hours on a very fast dual-opteron server.
During the migration process, you'll see a progress bar which updates every now and then. Let it go all the way to 100%. If the migration is interrupted for some reason (browser closed or network failure) don't worry - just wait for a while to make sure the process is finished on the server (you might check processor load, caused by your webserver), and then start the migration again. The process is smart enough to take up where it left off and you'll see messages about this. Starting the migration script while a former process of the script is still running, might cause data corruption.
The migration process places the Moodle installation in maintenance mode, so non-admins cannot login. Once you start the migration it needs to finish all the way before the installation can be used by others. When the migration is done, Moodle gets automaticaly out of maintenance mode.
