The discussion revolves around the feasibility of migrating from vBulletin 3.8 to Discourse, focusing on challenges like improper bbcode and HTML migration. Juless reports issues with bbcode and HTML (e.g., tables, iframes) not transferring correctly. neounix confirms a successful migration but highlights the labor-intensive process due to years of nested bbcode and encoding issues. pfaffman notes that such migrations often require manual fixes, suggesting possible solutions like setting @bbcode_to_md = true or using the bbcode plugin. Juless asks where to configure this setting, indicating interest in resolving bbcode issues.
I’ve done a migration from vbulletin 3.8 to Discourse but have several major issues:
bbcodes did not migrate properly, having tons of bbcodes in the Discourse now
html strings (tables and many more, iframes) didn’t migrate (normal, but is there a way to properly migrate them to Discourse without having html tags anymore?
Has anyone done a proper migration from vb 3 to discourse fixing these problems?
It was very labor intensive and a very tiring process to get it nearly perfect because of 15 years of nested bbcode and a lot of mojibake, etc. over the years.
Hopefully, your forum is not “coding intensive” with over a decade of nested bbcode like ours.
I’ve done many, as imports are a considerable part of my living. They often require considerable fussing with the issues that you describe. It’s typically a matter of deciding how many of the issues that you have can be automatically fixed up. Often, the messages didn’t even display properly in the original forum!
Some of the bbcodes might be fixed if you set @bbcode_to_md = true. Others might be fixed with the bbcode plugin. The tables and iframes will be considerably more fussy, I imagine.