22 lines
1.5 KiB
Markdown
22 lines
1.5 KiB
Markdown
# Importing V1 safely
|
|
|
|
V1 code remains on `main` at `7bd0a9a` and in history. V2 has a separate schema and must use
|
|
a separate data folder. It never upgrades a production V1 database in place.
|
|
|
|
1. Use V1's backup facility to make a consistent SQLite copy. If copying files yourself,
|
|
stop V1 first; copying only a live WAL-mode `.db` can omit recent writes.
|
|
2. Keep the original and a verified backup untouched. Start V2 with an empty V2 volume.
|
|
3. In V2 Settings → Data → V1 import, select the **backup copy** and preview it.
|
|
4. Review the reported counts/skipped items, then explicitly import. V2 opens the submitted
|
|
SQLite file read-only and creates new IDs in one transaction. A failed import rolls back.
|
|
5. Compare class/folder/deck/quiz counts and representative questions, rationales, attempts and
|
|
scheduling. V1's passwords, provider settings and share URLs are not reused. Recreate links
|
|
deliberately. Running the import again creates another set of content.
|
|
|
|
The importer supports V1 classes, material groups, decks/cards, quiz sets/questions/options,
|
|
completed attempts, spaced-repetition card state and activity where present. It reports
|
|
unsupported/skipped records. Older optional game features are not migrated as games.
|
|
V1 JSON quiz/flashcard exports can also be pasted/uploaded in a class's Import dialog.
|
|
|
|
Portable V2 JSON exports are useful for migration between apps; full ZIP backups are needed
|
|
to preserve progress, documents, settings and credentials. See DEPLOYMENT.md for recovery.
|