kingofseo As a plugin, by API, SQL? What do you have in mind?
XenForo to Flarum Importer
It will a php class which can be implemented in the flarum core/extension as well.
- Edited
Here is my Flarum story. I am running a Xenforo community and for the past 6 months around 30 users helped me with testing a new Flarum forum to see if it would be a good idea to switch our website from Xenforo to Flarum in the future. The new test forum gained some content that is worth keeping. And I think I will be converting the old forum to Flarum as well. I would like to merge the old with the new, hopefully without any painful manual SQL editing.
I would be amazing if the importer could merge the existing content with the content imported from Xenforo.
jacko migrate to phpbb then to flaurm using https://discuss.flarum.org/d/1117-phpbb-migrate-script-updated-for-beta-5
Davis Thanks Davis, I'm gonna wait a few more months for the Flarum stable release and hopefully we will see Xenforo importer by then. If it's not released, I will follow your advice. I suspect it will create URL redirection issues though... URL redirection will be very important for a good importer (old Xenforo URLs should point to the corresponding discussions in Flarum).
- Edited
Merging is non-trivial.
If both sites started with auto-increment at 1 you'll have a lot of collisions for topic/post IDs. You'll have to consolidate accounts, after you've done that there will be quite a few changes in the DB when it comes to user IDs.
Nothing is impossible, but it's a lot of work for a situation that's fairly unique.
If you first want to test Flarum and keep that content after a conversion a bit of planning makes everything much easier. I.e. make sure the User IDs are the same between the two systems and make sure that topic/post IDs of the Flarum setup start at IDs quite a bit higher than MAX(topic_id) and MAX(post_id) of your old system. If you do that merging should be fairly doable.
Regarding the API of SQL question; I would prefer SQL by a very large margin. The API route is a no-go if you have a larger database (I.e. more than a few hundred thousand posts).
@jacko; what did you end up doing? Have you converted/merged? Or are you still waiting for stable?