Skip to content

Migration notes

Synthezia opens and evolves its local SQLite schema as part of the application runtime. The repository does not provide a published end-user migration matrix, data-export migration tool, or rollback procedure for every beta version.

  1. Keep source recordings in a location you manage.
  2. Save any generated summaries you need outside the application before a significant upgrade experiment.
  3. Try a safe test session after installing a candidate build.
  4. Preserve the exact error, application version, and macOS version if a stored session no longer opens.

Do not edit synthezia.db manually as a normal migration step. A reset destroys session and index records and is not a rollback mechanism.