Some fields in the evo_users table have become fields in the qp_plugin_sharedvalues table. For each user, near as I can tell, There might be 4 bits that move over to the new table. Moving means associating the current value with a user_ID and a fieldname. So something like this...
- Code: Select all
FOREACH USER IN evo_users {
IF ISSET user_aim THEN INSERT INTO qp_plugin_sharedvalues
{ psv_user_ID, psv_psf_fieldname, psv_userfieldvalue == user_ID, 'aol_aim', user_aim }
IF ISSET user_msn THEN INSERT INTO qp_plugin_sharedvalues
{ psv_user_ID, psv_psf_fieldname, psv_userfieldvalue == user_ID, 'msn_im', user_msn }
IF ISSET user_yim THEN INSERT INTO qp_plugin_sharedvalues
{ psv_user_ID, psv_psf_fieldname, psv_userfieldvalue == user_ID, 'yahoo_im', user_yim }
IF ISSET user_avatar_file_ID THEN INSERT INTO qp_plugin_sharedvalues
{ psv_user_ID, psv_psf_fieldname, psv_userfieldvalue == user_ID, 'avatar_ID', user_avatar_file_ID }
}
Free-typed so ...

Not sure how you're doing a migrator, but if it was my mission that's how I'd get it done. Look at each field in each table, find where it goes, figure out what it might need, take care of it, then move on. Probably not more than a couple of hundred fields overall but that's just a guess. Could be more. Dunno. hmmm... Can't hurt to learn eh?
Did an export of an evo333 and qp installation and left out the data then stripped out comments. Probably didn't need to strip out comments but what's done is done eh? Anyway that made it real easy to count stuff. evo has 43 tables, we have 42. Evo has 320 fields, we have 307. We then match almost exactly on all sorts of trivial little counting games. Primary keys, Unique keys, Keys, MyISAM tables, InnoDB tables. We're also still totally latin1 for DEFAULT CHARSET which I thought a long time ago was something we figured was good to change.