I re-ran the export/import with Discourse (1612818).
The only apparent difference was that the importer reported which emails it was invalidating during the import. The result of the process was still the same - only 5 posts got imported, and post ownership is still mismatched.
Checking the status of the code - does this mean not everything made it into tests-passed?
If IMPORT_SOURCE still only created 5 posts, then I don’t know what’s happening. At this point someone needs to compare the data (post id’s, user emails, etc.) in the exported data with what’s in the target db and figure out why there’s a collision (user_custom_fields, post_custom_fields).
No, it never looks at name. If you’re using the new IMPORT_SOURCE support, then email address is the only thing that it looks at. If there’s a duplicate username but different email address, then a number will be put on the end, like “omar1”.
With @pfaffman’s guidance, deleting import_id from both Discourses before export/import worked:
This did not work: discourse import_category /category-export-2017-10-25-225306.json
but this did: bundle exec discourse import_category /category-export-2017-10-25-225306.json
Having to delete import_id from the Discourse that was converted with the phpBB importer prevents me from doing a leisurely initial import first and an incremental import later, but I can live with that.
I want to merge a smaller discourse forum into a single category within my larger discourse forum. Both forums are native to discourse. I did not import anything from any other forum software. Both forums are running as separate stand-alone DO droplets (and are up-to-date). Naturally, I want all user logins, avatars, and data to transfer. Will the process laid out by @pfaffman work for this? Or, would a different process be more appropriate for putting the smaller forum into a single category?
I did. The only challenge I encountered was the usernames and email accounts merging - which wasn’t perfect. It was probably an error on my part because it was more complicated than I anticipated. After a ton of work, and hard conversations with established members, we decided to leave the past behind and start over (we originally merged from vBulletin which went well). In retrospect it was the best decision. We use AWS for all of our media uploads now instead of keeping any content on site which has kept costs down significantly. Full disclosure…I made the mistake back in the days of BBS to operate a political forum and continue to do so (I may switch to hockey or something a bit less stressful). Stale political conversations and bickering weren’t really worth saving…since the banter and bickering never stops and getting to thousands of threads isn’t so tough.
I could see how someone buying an existing community, merging separate knowledge bases, or combining corporate communities of practice would absolutely need a flawless merge. For my purpose it wasn’t a big deal. Apologies to all for not providing an update. When things didn’t go as planned and I couldn’t figure it out, I didn’t want to be a pain.