1. 1. Copy database tables and Mambo code from remote server to local system. I used WAMP to do all migration. By doing that the site was still online, while I was doing some research. If for some reason you don’t have access to phpMyAdmin or any other database client, use SIDU 3.2 DB Web GUI
2. 2. Convert SQL file to UTF8 encoding.You can do this using i.e. Notepad++ – use Convert to UTF8 (without BOM).
   Also change tables encoding to UTF8. This operation will cause problems with ‘ocp_core_acl_aro’ table "#1071, Specified key was too long; max key length is 1000 bytes". Rewrite it as below

   CREATE TABLE `ocp_core_acl_aro` (
   `aro_id` int(11) NOT NULL auto_increment,
   `section_value` varchar(240) NOT NULL default '0',
   `value` varchar(240) NOT NULL default '',
   `order_value` int(11) NOT NULL default '0',
   `name` varchar(255) NOT NULL default '',
   `hidden` int(11) NOT NULL default '0',
   PRIMARY KEY  (`aro_id`),
   UNIQUE KEY `ocp_gacl_section_value_value_aro` (`section_value`(100),`value`(75)),
   UNIQUE KEY `section_value_value_aro` (`section_value`(100),`value`(75)),
   KEY `hidden_aro` (`hidden`),
   KEY `ocp_gacl_hidden_aro` (`hidden`)
   ) ENGINE=MyISAM AUTO_INCREMENT=13 DEFAULT CHARSET=utf8
   

3. 3. Migrate to Mambo 4.5.2 Create local database for Mambo 4.5.2 and use utf8_general_ci for connection and comparison. Download and extract Mambo 4.5.2 to webserver directory. Change db settings in configuration.php and apply sql script upgrade451to452.sql from installation\sql direcotry
4. 4. Install Joomla 1.5 but do not load sample data
5. 5. Install mtwmigrator for Joomla 1.5 You can download it here mtwmigrator-v0-2-1. Run component and go to Preference. Set db name, location, login and password. Select data you want to migrate and launch migration process. After this step you should have all data from Joomla 1.0 availbale in new installation on Joomla 1.5
6. 6. Migrate to Joomla 1.6 using jUpgrade. You can download it here jUpgrade. All you have to do is to install it within Joomla 1.5 and start. If some problem occurs try enabling Debuging in jUpgrade

Now, you should have new installation of Joomla 1.6 created for you and available in jUpgrade dir in Joomla 1.5 directory. New tables were created in same database as Joomla 1.5, so depending on needs, final step might be to dump those tables and move to new, dedicated location.

WebsiteUser:
  tableName: website_users
  columns:
    UserId:   { type: integer(8), primary: true, autoincrement: true }
    GroupId:  { type: integer(8), notnull: true  }
    Username: { type: string(255), notnull: true }
    Password: { type: string(255), notnull: true }
    Email:    { type: string(255), notnull: true }
  indexes:
    uniqueusername: { fields: [Username], type: unique }
    uniqueemail:    { fields: [Email], type: unique    }
  relations:
    WebsiteGroup: { class: RuczajGroup, local: GroupId, foreign: GroupId }
  options: { type: INNODB, collate: utf8_polish_ci, charset: utf8 }

to ustawienia nazwy tabeli i pól wygląda dość dziwnie, mianowicie nazwa tabeli nie jest faktyczną nazwą tabeli tylko czymś w rodzaju nazwy encji. Pola też należy pisać dokładnie takimi samymi literami(chodzi o wielkość) jak w pliku YAML, mimo że tworzone tabele składają się wyłącznie z małych liter. W sumie wydaje się to logiczne, ale trochę czasu mi zajęło dojście co oni tak naprawdę chcą a wyjątek typu
('The supplied parameters to Zend_Auth_Adapter_Doctrine_Record failed to produce a valid sql statement, please check table and column names for validity'); nie podpowiada zbyt wiele.

Poprawny kod autoryzacji wygląda zatem tak:

$dbConnection = Doctrine::getConnectionByTableName('website_users');
$authAdapter = new Zend_Auth_Adapter_Doctrine_Table($dbConnection);
$authAdapter->setTableName('WebsitejUser')
                  ->setIdentityColumn('Username')
    		  ->setCredentialColumn('Password')
		  ->setCredentialTreatment('md5(?)');