Hi All,
I run a technical community in the UK and we run our conversations on Yammer, but I am looking to move that to Discourse going forward.
Has anyone managed to do a user and conversation export from Yammer and import to Discourse, so that I do not lose our existing conversations?
Thanks
Not aware of any yammer imports off the top of my head, but first things first. You need to get some sort of backup off yammer.
I should be able to get the data export, either from the toolset or I can wrote a quick export utility that uses the API.
Is there a “import schema” that I could use to make it import ready?
Not really, we have a base importer that does lots of heavy lifting, you would need to write about 100-500 lines of Ruby to create a new importer.
That was my thinking. If I process my export to fit the data model of the base importer, then jobs a good 'Un.
Afaik, 3 years later, still no Yammer importer
Rats! I’d really like one as there are 3 Yammer networks that I would love to import. I guess that if someone wants one badly enough they will just have to write it themselves.
If you have a budget, I can help. See Discourse Migration – Literate Computing, LLC for some basic information on imports.
6年后，至少问一下是否有 Yammer 导入器，感觉有点小气。
有人知道吗？
有一个开放的 PR 存在一些未解决的问题：
C’mon @pfaffman，你太棒了！！！
顺便说一句，感谢你对导入的帮助——我仍然从中受益。
嗯，感觉一点也不接近。
我会再花一个小时试试。
我看到这个是在 2023 年 1 月合并的。@pfaffman 那最后是正常工作了吗？
我认为是的。你试过吗？
我们正在运行企业版，所以还不行，但我已联系团队，看看他们最近是否使用过。我不会惊讶于微软在上次更新导入程序后进行了糟糕的更改。
如果我能在下周左右拿到我们的数据库，我会看看我们是否可以尝试一下并提供相应的反馈
所以，我们这边有个更新：我认为我们可能要放弃这个导入器了。
手动迁移大约需要 80 小时，团队认为导入器可能需要做一些工作，再加上与内部采购和法务部门协调，最终对我们来说收益甚微。而且从 IT 部门获取数据库并不那么简单 
认为手动迁移80小时比更新脚本“更容易”的想法确实很有趣，但我猜我能理解让IT、法务和采购部门协调工作比更新脚本要难得多。