Users migrating from the original MeshCore iOS app to MeshCore One may have an existing MeshCore backup file like:
meshcore_.db
MeshCore One currently appears to expect .mc1backup files for full restore/migration, while the old app exports a raw SQLite database. Renaming .db to .mc1backup does not work.
What the legacy database contains
The legacy backup is a valid SQLite DB and can include:
- contacts
- channels
- contact / DM messages
- channel messages
- device/config-related tables
One of the following would solve this:
- Direct import of legacy
.db backups
- A migration tool (
.db -> .mc1backup)
- Partial import (contacts + channels at minimum)
- Documentation of
.mc1backup format for community tooling
When switching to MeshCoreOne, one effectively losees their chat history and has to rebuild everything manually, despite having a full backup.
A migration path would massively improve adoption and prevent data loss.
thanks, MeshCoreOne is awesome and this would make it a complete upgrade path 🙏
Users migrating from the original MeshCore iOS app to MeshCore One may have an existing MeshCore backup file like:
meshcore_.db
MeshCore One currently appears to expect
.mc1backupfiles for full restore/migration, while the old app exports a raw SQLite database. Renaming.dbto.mc1backupdoes not work.What the legacy database contains
The legacy backup is a valid SQLite DB and can include:
One of the following would solve this:
.dbbackups.db->.mc1backup).mc1backupformat for community toolingWhen switching to MeshCoreOne, one effectively losees their chat history and has to rebuild everything manually, despite having a full backup.
A migration path would massively improve adoption and prevent data loss.
thanks, MeshCoreOne is awesome and this would make it a complete upgrade path 🙏