Simple Machines Community Forum

SMF Support => Converting to SMF => vBulletin => Topic started by: mercelo on February 07, 2019, 02:37:30 PM

Title: vBulletin 4.2.3 to SMF 2.0.15
Post by: mercelo on February 07, 2019, 02:37:30 PM
Hi, is possible migrate vBulletin 4.2.3  to SMF 2.0.15 ?

Thanks
Title: Re: vBulletin 4.2.3 to SMF 2.0.15
Post by: vbgamer45 on February 07, 2019, 02:46:44 PM
Latest convertor we have is 3.7 https://github.com/SimpleMachines/converters/tree/master/SMF2.0/Vbulletin/3.7
But we can give that a shot and correct issues as we find them.
Title: Re: vBulletin 4.2.3 to SMF 2.0.15
Post by: mercelo on February 07, 2019, 02:57:58 PM
Thanks, and tutorial ?
Title: Re: vBulletin 4.2.3 to SMF 2.0.15
Post by: vbgamer45 on February 07, 2019, 02:58:49 PM
Install SMF 2.0.15
upload the convert.php and .sql file to SMF then run via your browser.
Title: Re: vBulletin 4.2.3 to SMF 2.0.17
Post by: Seeker-Smith on January 11, 2020, 04:07:11 PM
Trying to convert from 4.23 to SMF 20.1.7 and it runs fine until attachments and I get this error.
Converting posts (this may take some time)...
Successful.
Converting polls... Successful.
Converting poll options... Successful.
Converting poll votes... Successful.
Converting personal messages (step 1)... Successful.
Converting personal messages (step 2)... Successful.
Converting topic notifications... Successful.
Converting board notifications... Successful.
Converting smileys... Successful.
Converting attachments... Unsuccessful!
This query:

    SELECT
    postid AS id_msg, counter AS downloads, filename, filedata, userid,
    attachmentid
    FROM `bsxk5_groups`.attachment
    LIMIT 0, 500;

Caused the error:

    1054
Title: Re: vBulletin 4.2.3 to SMF 2.0.15
Post by: magicbus on February 19, 2020, 09:14:05 AM
I had lots of MySQL timeout errors. Try running the sql query in phpMyAdmin (you'll need to edit the FROM clause)

If you get exactly the same error there (as I did) it looks like a problem with the vbulletin table rather than the conversion process. I re-installed the vb tables and fixed the problem.