<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Migration on Dmitry Sheiko&#39;s Web Development Blog</title>
    <link>https://dsheiko.com/tags/migration/</link>
    <description>Recent content in Migration on Dmitry Sheiko&#39;s Web Development Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 02 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://dsheiko.com/tags/migration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrating Legacy Apps to Next.js with Claude Code</title>
      <link>https://dsheiko.com/weblog/migrating-legacy-apps-to-nextjs-with-claude-code/</link>
      <pubDate>Thu, 02 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/migrating-legacy-apps-to-nextjs-with-claude-code/</guid>
      <description>Over the past year I migrated several legacy projects to Next.js with the help of Claude Code. Along the way I found a workflow that consistently produced good results, and it&amp;rsquo;s worth sharing because it saved a surprising amount of time.&#xA;Migrating functionality and content Most of the legacy projects I worked on were PHP applications. Claude Code wasn&amp;rsquo;t just copying templates. It analyzed the legacy codebase, extracted business logic, content, UI components, and even parts of the admin interface, then rebuilt them as a clean Next.</description>
    </item>
  </channel>
</rss>
