In pages/, one exported function per page fetches data and passes it as props. In app/, any async Server Component fetches what it needs, and Next.js infers the route's rendering mode from what the tree reads (the static-or-dynamic question). On Next.js 16.4.5, Cache Components off:
getStaticPropsbecomes data access in a Server Component; the page is still prerendered at build.revalidate: 60becomesexport const revalidate = 60orfetch(url, { next: { revalidate: 60 } }). Both versions sents-maxage=60, stale-while-revalidate=31535940.getServerSidePropsbecomes a component that reads the request:await headers(),cookies()orsearchParamsinstead ofreq. That read makes the routeƒ, not the fetch. Afetchwith no options isn't stored in the Data Cache, yet its route built as○, with the value frozen at build.getStaticPathsbecomesgenerateStaticParams, returning[{ id: '1' }]instead of{ paths, fallback }.dynamicParams = falsematchesfallback: false(404).true, the default, behaves likefallback: 'blocking': the first request renders the whole page, then it is cached.fallback: truehas no direct equivalent. Pages serves a skeleton at once withrouter.isFallback, then fetches the props as JSON. Inapp/, aloading.jsnever showed on that first document request. With Cache Components on, the App Shell fills the role.{ notFound: true }and{ redirect }becomenotFound()andredirect()calls, which throw rather than return. Both gave 404 and 307 as before.
Props go away too: each component fetches its own data instead of receiving it from one function per page.
The migration guide's own comments disagree on the fetch default (one says force-cache, one says uncached). The 16.4.5 build above is the tiebreaker: uncached data, prerendered route.