Data Compatibility Migration

Patterns for safely consuming API responses that may contain old field names, new field names, or both during a domain cutover. Derived from the Phase 4 mc→creator frontend migration.

When to Use

• Frontend must render data from an API that is mid-cutover (old and new field names coexist).
• Building fallback helpers to centralize dual-field access instead of scattering ?? chains.
• Deciding when to remove compatibility reads after cutover stabilization.

Core Pattern: Centralized Fallback Helpers

Create a single utility file per domain that encapsulates all field-access logic:

// src/lib/creator-utils.ts

export type CreatorIdentity = {
  id?: string | null;