migrate-custom-hooks-to-storefront-data

Migrate custom React hooks to storefront-data presets by centralizing the new preset seam first, then replacing feature code one block at a time. This unifies architecture and avoids dual data layers during feature cutovers.

A preset seam is the centralized integration point where storefront-data presets replace custom hooks. Establish this seam before replacing feature code to ensure callbacks are preserved and architecture stays unified during migration.

Avoid dual data layers during Medusa storefront migration by replacing custom hooks with presets one vertical feature at a time. This block-by-block cutover strategy minimizes risk and removes legacy wrappers after migration.

Yes, migrating to storefront-data presets preserves storefront-specific callbacks and UX. The migration proceeds block-by-block to maintain existing storefront patterns while centralizing the preset seam and aligning SDK usage.

Use storefront-data presets instead of custom hooks when unifying Medusa app architecture during feature cutovers. This approach enforces migration best practices, centralizes data layers, and enables systematic removal of legacy wrappers.

Block-by-block storefront-data migration requires proceeding one vertical feature at a time to minimize risk. It is limited to app architectures using Medusa storefront patterns and requires centralizing the preset seam before replacing feature code.