Study/docs/MIGRATION.md
Elijah 5fef59b07b
All checks were successful
Verify and publish V2 container / build-and-push (push) Successful in 30s
Remove the V1 database importer
The /api/import/v1 endpoint, server/services/v1import.ts and its test are
gone; Settings already restores full V2 backups in that place. MIGRATION.md
now covers V1 JSON exports and running the old importer from history
(7125dec), plus moving data between V2 installs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 12:35:51 -07:00

1.3 KiB

Moving data into V2

V2 has its own schema and must use its own data folder. It never opens or upgrades a V1 database.

From V1

V2 no longer imports V1 databases. The importer (server/services/v1import.ts and the /api/import/v1 endpoint) was removed on 2026-11-16, and Settings → Data now restores full V2 backups instead. Two ways remain for V1 content:

  • V1 JSON exports. V1 quiz and flashcard exports can be pasted or uploaded in a class's Import dialog. This brings content only: no attempts, schedules or activity.
  • The old importer. It is in git history, last as of commit 7125dec. Check that commit out into a separate working copy and run it against an empty V2 data folder. Point it at a consistent backup copy of the V1 database, never the live file. Make a full V2 backup afterwards, then restore that backup on the current version.

V1 code remains on main at 7bd0a9a and in history.

Between V2 installs

  • Full backup ZIP (Settings → Data → Download backup, then Restore a full backup on the other server): everything, including progress, documents, settings and AI credentials. See DEPLOYMENT.md.
  • Portable JSON export: classes, quizzes, flashcards and notes only, added alongside what the other install already has.