Migration Path from Synapse #23
My current homeserver is on Synapse, and I would love to be able to bring all my data over to Telodendria when it's stable. Some sort of way to automatically migrate all (or even most) of the Synapse database over to Telodendria would significantly lower the barrier to entry for Telodendria, and as far as I know, it would be a totally unique feature, because no other homeserver can import data from another homeserver.
There may be MSCs in the future that are designed to provide a standardized migration path. If those are accepted, we should implement them. Otherwise, we may want to explore options for extracting data from the Synapse database, either by directly making a connection, or using the Matrix APIs. I'm actually not entirely sure what this will look like.
This isn't something that needs to happen until after the stable release, I just want to make an issue for it so we can discuss it and keep an eye on potential solutions.
@array-in-a-matrix No, because #24 specifically addresses upgrades from one Telodendria release to the next. This issue is about migrating from Synapse to Telodendria.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?