Most Next.js teams have a Pages Router → App Router migration sitting in their backlog. It's mechanical but careful work, and it keeps getting deprioritized. I built migrate-bot to automate it end-to-end, and this post is about how it works under the hood.
What the migration actually involves
App Router isn't just "move files to a new folder". The semantic changes:
getStaticProps / getServerSideProps → async Server Components
getStaticPaths → generateStaticParams






