@ pyragony54
It seems that you are basing your decision not to convert your forum to SMF at least in part on a misunderstanding about SQL databases: there is no 128 MB cap on their size. It is possible, however, that your hosting provider has imposed such a limit.
A few years ago, I moved my website and forum from a web hosting provider to my own virtual private server (VPS) running cPanel to avoid what I considered an unreasonable restriction (the blocking of visitors using the Tor network). The monthly cost is modest (about €30 per month), and I'm very glad now to have full control over size quotas and other limitations.
Before converting my forum from YaBB to SMF, I was encountering an issue that perhaps could be addressed in YaBB 2.7: the forum index would frequently become corrupted, which would result in some forum pages becoming inaccessible, and the list of recent posts would instead display very old posts. I would have to rebuild the forum index every few days.
I have noted a few advantages of SMF over YaBB with my own forum. Perhaps the most important is that the forum is now "mobile-responsive" and is easily readable on a smartphone. I've also been able to use an SMF mod (Optimus) to help optimize the forum for search engines. I also had Claude AI Opus 4.7 write a modification of the default SMF template to implement microdata tags to make message threads eligible for Google's Search's "rich results."
I imagine it would be possible to do all these things in YaBB 2.7 as well, and the AI tools you're using would presumably facilitate that.
I wish you many more years of health and happiness! (I'm 62 myself.)
One more thing about the conversion script that I mentioned earlier in this thread: it has a bug that causes regular users to be unable to post messages. Claud AI's Opus 4.7 helped me to quickly troubleshoot and fix the problem on my own forum, but the conversion script I've linked to on my website (georgemaschke [dot] net) still has the bug. Here is a summary that Claude generated for me:
Quote:The YaBB-to-SMF 2.1 converter incorrectly assigned imported users' post-count group ID to both id_group and id_post_group in smf_members, rather than setting id_group = 0 (Regular Members) and letting id_post_group carry the post-count tier independently. The result: 6,000+ users had their primary group set to a post-count group like "New User," which doesn't carry the standard Regular Members permissions — so they couldn't view profiles, reply to posts, etc. The fix was a single UPDATE setting id_group = 0 for everyone in groups 12–17, followed by SMF's built-in post-group recount.
If you eventually decide to report this upstream, the SMF developers might appreciate knowing — it's the kind of bug that affects every YaBB migration silently, since admins (with id_group = 1) never experience the symptoms themselves.