Podia migration input
The importer accepts the shared normalized CSV described in the import guide. It does not parse arbitrary Podia exports or promise compatibility with a particular native export. Start from a copy and manually reshape a sanitized representative into the supported normalized fields.
Example synthetic input using the documented aliases course, section,
lesson, and video:
email,course,section,lesson,video,purchased_atlearner-one@example.test,Workshop Basics,Prepare,Choose an outcome,https://media.example.test/old/outcome.mp4,2026-09-30learner-two@example.test,Workshop Basics,Prepare,Choose an outcome,,2026-10-01This creates a free draft course at
src/content/courses/workshop-basics/, a prepare module, and one lesson stub.
Repeated course and lesson rows do not duplicate that lesson. A supplied video
URL is kept only as a commented reference in the stub; re-host the video before
publishing. Student email rows are written to a private migration CSV under
.stratolms-private/migrations/<run-id>/students.csv.
Preview and run the import, then validate the generated content:
pnpm stratolms import --from podia --file=./podia-normalized.csv --dry-run --jsonpnpm stratolms import --from podia --file=./podia-normalized.csvpnpm stratolms checkThe importer does not transfer payments, entitlements, hosted video, refunds, or content absent from the normalized CSV. Review generated files, finish the course, re-host media, and deliberately publish it. Any replacement access for existing learners is a separate owner action. See the shared guide for collision, cleanup, and private-record handling.