Migrate to Flarum

AMEXEU

The title should already indicate what I am looking for. ?

It is not like I do not used the search function or didn't read the other topics from the devs or the GitHub roadmap. However, most of the replies I have found were already a bit old.

So is there any update on this subject? I saw a FluxBB and phpBB importer, however I am wondering about a NodeBB importer, especially since it is using Redis/MongoDB. Will Flarum provide any support for these in the future?

I do know very well that you won't give any ETAs, but is there a "time" (e.g. beta 7) when we could expect this to be realized?

jordanjay29

I don't expect importers to be developed until after the stable release.

FBI

yes, wait stable release is the only choice

kaktux

What about this:

the biggest open source forums ((active community + developers) i know of) are phpbb and discourse.

phpbb is a bit outdated and most stuff is widespread in my opinion.

So that leaves discourse. They already got a lot of importerst for several forums - and as to my knowledge have full-time developers - will probably keep those up-to-date.
I couldnt find any license information - but if they are open source like the software - maybe flarum and discourse can cooperate in that area (well flarum profiting from the work done).

https://github.com/discourse/discourse/tree/master/script/import_scripts
There are about 40 of those.

So basically my point is:
- use the available importers -> possibility to get discourse ready format for 40 or so forum softwares
- create an importer converting that format into flarum-ready format

I am not programmer - so its just an idea for you to process.

ChristopherKhawand

kaktux
That's impossible right now because Flarum and Discourse are made with two different languages.

Pollux

ChristopherKhawand

Importers don't need to care about the language of the source or destination software, importers can even use a third language. The importer just needs an abstraction layer to access both databases, so it can process and move the data around and in some cases recombine it in new ways.

kaktux

The idea sounds intriguing, and often it is indeed the only way to convert the data. But it's not always the best solution. If you migrate from one software to another, you will often face the problem, that some data is missing in the source which is used in the destination, and other data from the source can't be used in the destination.

Let's assume, your source software has the features A, B and C, your intermediary software (discourse) knows A, B and D, and your final software of choice uses A, C and E. If you have a dedicated migration tool from source to destination, you can convert A and C, B will be lost and E is just not there. If you use the two step path via the intermediary, you will loose B and C, only A will be converted.