realm-migration-ref

Migrate Realm to SwiftData by converting Realm Object models to SwiftData @Model classes, mapping relationships, and transitioning threading from Realm's dispatch to Swift Concurrency. The Skill covers schema translation, relationship patterns, and phased rollout strategies for production iOS apps.

SwiftData relationships differ from Realm's approach. Convert one-to-many and many-to-many relationships using inverse relationships, apply proper indexing strategies, and validate bidirectional links during migration testing to ensure data integrity.

Yes. SwiftData uses CloudKit for sync instead of Realm Device Sync. The migration covers sync transition patterns, including how to move subscription logic, conflict resolution, and account-tied data to SwiftData's CloudKit integration model.

Replace Realm's dispatch-based threading with async/await patterns. The Skill covers safe conversion strategies, identifying thread-safety boundaries, and testing concurrent access to ensure data races don't occur post-migration.

Phased rollout runs Realm and SwiftData in parallel during transition. Strategies include dual persistence during staging, data verification between stores, gradual user cohort migration, and rollback plans for production safety.

Not completely. Identify model conversion patterns first, then systematically migrate data access layer components. The Skill provides a test harness and migration phases to reduce rewrites and validate correctness incrementally.