Context: JSS enters EOL in June 2026 -- 3 months from now. JSS npm downloads are still 2-4x higher than Content SDK equivalents, indicating the majority of the Sitecore Next.js developer ecosystem has not yet migrated. Community partners (Fishtank, AgencyQ) are publishing migration guides, but no official automated tooling exists. Content SDK, as the strategic successor, should own this migration narrative.
Steps:
1. Create `packages/codemod/` in the Content SDK monorepo (or a standalone `@sitecore-content-sdk/codemod` package)
2. Implement jscodeshift transforms for:
- `@sitecore-jss/*` import renaming to `@sitecore-content-sdk/*`
- `middleware.ts` to `proxy.ts` file rename and content migration
- HOC removal (`withSitecoreContext`, `withPlaceholder`) and replacement with hooks
- `images.domains` to `remotePatterns` in `next.config`
- `SITECORE_EDGE_URL` to `SITECORE_EDGE_PLATFORM_HOSTNAME` env var rename
3. Make it runnable via `npx @sitecore-content-sdk/codemod`
4. Include a dry-run mode that reports what would change
5. Write migration guide documentation referencing the codemod
6. Test against a fresh JSS 22.12 Next.js App Router project
Acceptance criteria:
Codemod handles the 5 core transforms listed above
Dry-run mode works without modifying files
Migration guide published alongside the tool
Tested against JSS 22.12 App Router and Pages Router projects
Risks: JSS and Content SDK have API surface differences beyond import renaming. The codemod should handle the mechanical parts and clearly document what requires manual intervention (e.g., component refactoring for Server Components).