Migrating from mautrix-facebook
MrAnno opened this issue · comments
Hi,
Last week, a migration path from mautrix-facebook to mautrix-meta was published by upstream:
https://github.com/mautrix/docs/blob/master/bridges/go/meta/facebook-migration.md
I couldn't find anything similar in the playbook, so I thought it might be worth opening an issue and discussing the current migration method.
I've added a link to that documentation in #3254, but have been unsuccessful in completing it. A few issues:
- The migration feature isn't there in v0.2.0, so it needs the latest Docker image (which makes my doc link misleading).
- Database permissions need to be manually altered in order to run the migration, and it's still not straightforward to modify the mautrix-meta-messenger service etc. as needed.
- Migration requires identical bot name and username prefixes, which I think is only partially supported by the playbook variables.
hs_tokenandas_tokenmay or may not have to be identical, I didn't manage to get it running either way.
At this point, I'm very curious about people who have made the switch already, did you get any message history without db migration? A meta bridge issue mentions backfill, does that pull in old messages?
Migration did not work for me and i had to manually remove each room from my matrix element session and then re-add the chats... it was painful but fine in the end
@Joshndroid But did you get chat history? 😱
@jswetzen no I lost all history. I am not too concerned with the Facebook messages history though so was okay.
I was more annoyed that I ran everything and it never did the clean up/out. It was weird at first as I thought that the new bridge was broken until I realised that it was the old Facebook bridge rooms and I needed to find the new ones created by the new meta bridge and delete the old ones
I lost all history as well, but got hundreds of extra rooms.
The old bridge only created rooms as they were used, this one pulled out to I think at least 6 months.