Challenge
Data ownership, publication state, media access, and legacy identifiers had to move without treating an unverified import as a successful migration.
Backend engineering
Django platform and data migration foundation
A controlled migration path from Supabase-backed application data and storage to an authoritative Django, PostgreSQL, and S3-compatible platform.
Technical response
Build idempotent management commands, provenance records, validation constraints, private media controls, and an explicit reconciliation and rollback playbook.
Outcome
The local migration foundation is implemented and tested. Production cutover remains intentionally labelled as pending until a real export is reconciled.
04
Architecture
The delivery path.
- 01Verified export
- 02Idempotent import commands
- 03Django domain models
- 04PostgreSQL
- 05Private/public object storage
05
Security
Controls in context.
- Disguised-file rejection
- Path traversal protection
- Private media isolation
- Staff-only publication controls
06
Evidence map
Where the claims can be inspected.
These repository paths are references, not public downloads. They make the scope of each statement explicit.
- docs/data-migration-inventory.md
- docs/supabase-to-django-migration.md
- docs/storage-migration.md