Converting from NitroBB

[rolltidega]

OK I know that the official converters are listed but I wanted to ask if anyone has tried to import NitroBB into Xenforo. NitroBB is built on the guts of SMF so I am hoping that a conversion from SMF would work. Any chance there is a way to test that before purchasing?

 

[rainmotorsports]

You could contract someone to try the import for you prior to purchase. They might help or might want a few bucks. There are people who have dedicated import services regardless.

The next step is to import into something that can import NitroBB and then be imported into Xenforo if it can't be. But it's down to the table structure and if there are any changes to things like the password crypto's. If all of that is exactly the same there is a good chance you can import with little to no changes. Might have to forgo all steps that aren't related to essential data.

 

[Paul B]

Any chance there is a way to test that before purchasing?

In general it isn't possible to test importing without purchasing a license.

If there are any database schema changes between SMF and NitroBB, chances are the importer won't work.

 

[rolltidega]

Thanks for the info, Brogan

 

[Chris D]

I don't mind checking the DB schema for you. I suspect we'd be somewhat lucky if it was completely cross compatible though.

 

[rolltidega]

I don't mind checking the DB schema for you. I suspect we'd be somewhat lucky if it was completely cross compatible though.

Chris I would love if you could do that. How do I export the database schema and get it to you? I have access to phpmyadmin to get to the mysql database for my NitroBB install.

 

[Chris D]

In PHP My Admin you can load the database and click Export.

I believe if you go to Custom you will get more options. You should be able to export the schema with just the tables only, skipping the data. That should then save it as a SQL file.

You can then start a conversation with me here and attach the file to a message and I'll download it from there. I actually assumed it was free and open source like SMF otherwise I would have just downloaded it to save you the trouble of exporting it.

If it's easier you can Contact Us and provide log in details and I will export the tables myself.

 

[rolltidega]

Nah I can export the stuff. I will get it to you as soon as I am able. Thanks for looking!

 

[Chris D]

Just for posterity, removing differences in collation which shouldn't matter:

* Table nbb_alerts missing from DB git_smf.
* Table nbb_alerts_notify missing from DB git_smf.
* Column nbb_ban_items.ip_high5 missing from DB git_smf.nbb_ban_items.
* Column nbb_ban_items.ip_high6 missing from DB git_smf.nbb_ban_items.
* Column nbb_ban_items.ip_high7 missing from DB git_smf.nbb_ban_items.
* Column nbb_ban_items.ip_high8 missing from DB git_smf.nbb_ban_items.
* Column nbb_ban_items.ip_low5 missing from DB git_smf.nbb_ban_items.
* Column nbb_ban_items.ip_low6 missing from DB git_smf.nbb_ban_items.
* Column nbb_ban_items.ip_low7 missing from DB git_smf.nbb_ban_items.
* Column nbb_ban_items.ip_low8 missing from DB git_smf.nbb_ban_items.
* Column nbb_ban_items.is_ipv6 missing from DB git_smf.nbb_ban_items.
* Column nbb_boards.allow_likes missing from DB git_smf.nbb_boards.
* Column nbb_boards.board_type missing from DB git_smf.nbb_boards.
* Column nbb_boards.locked_to_bottom missing from DB git_smf.nbb_boards.
* Column nbb_boards.new_icon missing from DB git_smf.nbb_boards.
* Column nbb_boards.no_new_icon missing from DB git_smf.nbb_boards.
* Column nbb_boards.notice_description missing from DB git_smf.nbb_boards.
* Column nbb_boards.notice_title missing from DB git_smf.nbb_boards.
* Column nbb_boards.only_like_first missing from DB git_smf.nbb_boards.
* Column nbb_boards.passwd missing from DB git_smf.nbb_boards.
* Column nbb_boards.pretty_name missing from DB git_smf.nbb_boards.
* Column nbb_boards.rating_allowed missing from DB git_smf.nbb_boards.
* Column nbb_boards.redirect_icon missing from DB git_smf.nbb_boards.
* Column nbb_boards.require_prefix missing from DB git_smf.nbb_boards.
* Column nbb_boards.sitemap_priority missing from DB git_smf.nbb_boards.
* Column nbb_boards.sort_method missing from DB git_smf.nbb_boards.
* Column nbb_boards.sort_order missing from DB git_smf.nbb_boards.
* Table nbb_canned_replies missing from DB git_smf.
* Column nbb_categories.description missing from DB git_smf.nbb_categories.
* Column nbb_custom_fields.position missing from DB git_smf.nbb_custom_fields.
* Table nbb_email_templates missing from DB git_smf.
* Table nbb_friends missing from DB git_smf.
* Table nbb_hashtags missing from DB git_smf.
* Table nbb_likes missing from DB git_smf.
* Table nbb_log_cpfloodcontrol missing from DB git_smf.
* Column nbb_log_errors.stack_trace missing from DB git_smf.nbb_log_errors.
* Table nbb_log_mentions missing from DB git_smf.
* Column nbb_log_packages.credits missing from DB git_smf.nbb_log_packages.
* Table nbb_log_ratings missing from DB git_smf.
* Column nbb_log_topics.ignored missing from DB git_smf.nbb_log_topics.
* Table nbb_mbm_buttons missing from DB git_smf.
* Table nbb_member_logins missing from DB git_smf.
* Column nbb_membergroups.badge missing from DB git_smf.nbb_membergroups.
* Column nbb_membergroups.is_staff missing from DB git_smf.nbb_membergroups.
* Column nbb_members.activation_time missing from DB git_smf.nbb_members.
* Column nbb_members.aim missing from DB nitro_bb.nbb_members.
* Column nbb_members.cover_photo missing from DB git_smf.nbb_members.
* Column nbb_members.disregarded missing from DB git_smf.nbb_members.
* Column nbb_members.facebook_id missing from DB git_smf.nbb_members.
* Column nbb_members.facebook_preferences missing from DB git_smf.nbb_members.
* Column nbb_members.google_id missing from DB git_smf.nbb_members.
* Column nbb_members.google_preferences missing from DB git_smf.nbb_members.
* Column nbb_members.icq missing from DB nitro_bb.nbb_members.
* Column nbb_members.ignored_signatures missing from DB git_smf.nbb_members.
* Column nbb_members.is_spammer missing from DB git_smf.nbb_members.
* Column nbb_members.last_like missing from DB git_smf.nbb_members.
* Column nbb_members.last_pwd_update missing from DB git_smf.nbb_members.
* Column nbb_members.liked missing from DB git_smf.nbb_members.
* Column nbb_members.likes_given missing from DB git_smf.nbb_members.
* Column nbb_members.mentions_only_friends missing from DB git_smf.nbb_members.
* Column nbb_members.mentions_send_mail missing from DB git_smf.nbb_members.
* Column nbb_members.mentions_send_pm missing from DB git_smf.nbb_members.
* Column nbb_members.msn missing from DB nitro_bb.nbb_members.
* Column nbb_members.prevent_ignored_users missing from DB git_smf.nbb_members.
* Column nbb_members.privacy_last_activity missing from DB git_smf.nbb_members.
* Column nbb_members.profile_privacy missing from DB git_smf.nbb_members.
* Column nbb_members.tfa_backup missing from DB git_smf.nbb_members.
* Column nbb_members.tfa_secret missing from DB git_smf.nbb_members.
* Column nbb_members.timezone missing from DB git_smf.nbb_members.
* Column nbb_members.twitter_id missing from DB git_smf.nbb_members.
* Column nbb_members.twitter_preferences missing from DB git_smf.nbb_members.
* Column nbb_members.yim missing from DB nitro_bb.nbb_members.
* Column nbb_messages.body differs in COLUMN_KEY value ( vs MUL).
* Column nbb_messages.edit_reason missing from DB git_smf.nbb_messages.
* Column nbb_messages.likes missing from DB git_smf.nbb_messages.
* Column nbb_messages.mood missing from DB git_smf.nbb_messages.
* Table nbb_messages_history missing from DB git_smf.
* Table nbb_pages missing from DB git_smf.
* Column nbb_polls.show_voters missing from DB git_smf.nbb_polls.
* Table nbb_post_drafts missing from DB git_smf.
* Table nbb_prefix missing from DB git_smf.
* Table nbb_profile_comments missing from DB git_smf.
* Table nbb_profile_visitors missing from DB git_smf.
* Table nbb_qanda missing from DB git_smf.
* Table nbb_redirect_expire missing from DB git_smf.
* Table nbb_related_subjects missing from DB git_smf.
* Table nbb_related_topics missing from DB git_smf.
* Table nbb_sa_ads missing from DB git_smf.
* Table nbb_sa_positions missing from DB git_smf.
* Table nbb_shoutbox missing from DB git_smf.
* Table nbb_shoutbox_ban missing from DB git_smf.
* Table nbb_shoutbox_settings missing from DB git_smf.
* Column nbb_topics.id_prefix missing from DB git_smf.nbb_topics.
* Column nbb_topics.likes missing from DB git_smf.nbb_topics.
* Column nbb_topics.rating missing from DB git_smf.nbb_topics.
* Column nbb_topics.solved missing from DB git_smf.nbb_topics.

I had an old smf database back up (git_smf) which I renamed all of the table prefixes in that to nbb_ just so I wasn't getting the script I used complaining about different table names.

I would actually say, at first glance, this could work.

There's obviously a lot of additions to NitroBB that aren't in SMF, but those additions shouldn't really matter as we'll only be looking for what we expect to see in a normal SMF database. That said, it would mean some data loss, e.g. things like "likes". And as far as I can gather, though I've only skimmed it a few times, none of the default SMF stuff is actually missing apart from a couple of custom fields - I think the importer would skip these. The only two tables that even look considerably different, based on additional columns, are ban_items and boards.

I wouldn't like to stake any money on it, but it looks to me like it would work. There is of course a hidden facet here which we wouldn't know until the import is done. That being that although it seems like all of the SMF tables and columns are there, and their format is the same, we don't actually know if the data is stored the same. For example, if there's any data we expect to be in a comma separated string, but in Nitro BB they've serialized it instead -- that kind of thing. Another thing that concerns me is that although the tables are the same as SMF, if the storage of avatars and attachments is different, then this could be problematic.

Ultimately I'm quietly confident, but not so much that I would be able to guarantee it would work. I would also have to add the condition that if you tried it and it didn't work, we wouldn't necessarily be able to properly support that scenario, essentially making it an "at your own risk" type thing. So it would be worth a try, but you should certainly have a back up plan, ready.

Not sure if this helps

 

[rolltidega]

Do you think a backup of this database (with tables renamed to smf_ )could be restored into a fresh SMF install? I was thinking about trying that as an option. Just a thought.

 

[Chris D]

Well, that's possible. If you can get a fully working SMF install by loading in your NBB database then that could well mean the import into XF would work. It's worth noting that you can install SMF and give it any table prefix you like, so when you install SMF I think you could tell it to expect that the tables will be prefixed with nbb_.

Of course other solutions could involve finding a migration path from NitroBB to XF via another platform. For example if you can "properly" migrate a Nitro BB database to SMF or another platform such as PhpBB or MyBB then you should be able to go from them to XF. A lot of people do this - it's not perfect as you will likely have to reset everyone's passwords.

 

[Robust]

The easier option is to change the table prefix in SMF to nbb_ and directly use that database Then try an import to XF.

 

[Chris D]

That's basically what has already been suggested.