Sticky Warning for phpBB and SMF migrators (creating new users into Joomla sends emails!!)

We did a new install joomla 1.7, kunena 1.7, migrated data from phpbb3,08, during migration started to send out mails, sent 250 of nearly 12000 before webhost disabled site for spamming, lol

Hi
I'm new to Kunena - have been using phpBB3 for a well established forum, but we are updating our website to use Joomla & JomSocial and would prefer to use the most recent version of Joomla so am moving away from PHPBB3 as I'd need to stick with v1.5 to use the extensions which connect phpbb3.

We have a large database for phpBB3 (180MB!!!) and a large userbase so was wondering has anyone used the migrator successfully with such a large database?

Really need to avoid this issue others have reported of having emails sent out enmasse too - would cripple the server to send so many!
Many thanks,
Sadie

the database we converted was 250+MB, it will do it with ease just be aware of the mailing issue, also we had issues where £ . / - that were on the phpbb3 DB came out as a load of crap a couple of sql queries fixed that if you need them ill post them in here for you o// AS FOR MAIL ISSUE do the conversion at local level then transfer to a sql file upload via ftp then do a big dump, it will be faster and will avoid the mailing issue

Hiya, Thanks for the help.
How would you go about doing the conversion at a local level? Did you use XAMPP or similar or will the convertor run on my windows machine?

Having issues at the moment importing the big sql dump back into phpMyAdmin (I exported so as to not work on the live db & domain) so have a copy on my local machine which I can work on easily!
Sadie

yuppers XAMPP is the easiest way to go, also if you have or can get it use NAVICAT we have found it to be far better than phpmy admin for working with mysql.

(UPDATE) forgot that runing migrator on local will cause a error due to mail function not being instantiated, so there is a fix for this that also kills the mailing issue on a live server site as well.
Its nasty but it works found this on joomla forum linky at bottom

make sure to make copy's of original files befor attempting this so you can replace back to original state when you have done the migration, it does work i have tried it :evil:

mailing work around

we have the same mailing problem in joomla! 1.7, trying to migrate from SMF2.0. We do get more errors about duplicate primairy keys, on which the migration stops. I guess I first have to find a way to fix the PKs otherwise a migration won't be possible, right?

btw, thanks for the mailing workaround!