Skip to content

Please add support for importing legacy MeshCore iOS app backups exported as raw SQLite .db files #294

@PrimeDeep1

Description

@PrimeDeep1

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:

  1. Direct import of legacy .db backups
  2. A migration tool (.db -> .mc1backup)
  3. Partial import (contacts + channels at minimum)
  4. 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 🙏

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions