diff --git a/apps/website/src/content/posts/how-we-rebuilt-a-legacy-ui-with-zero-downtime.md b/apps/website/src/content/posts/how-we-rebuilt-a-legacy-ui-with-zero-downtime.md
index d5143917..4bbdbec9 100644
--- a/apps/website/src/content/posts/how-we-rebuilt-a-legacy-ui-with-zero-downtime.md
+++ b/apps/website/src/content/posts/how-we-rebuilt-a-legacy-ui-with-zero-downtime.md
@@ -46,7 +46,7 @@ To embed migration into the existing codebase, we built seamless bridges between
 <blockquote style="quotes: none; font-style: normal;">
   <p>
     💡 If you are interested in how we handle framework migrations, you can read about our experience migrating from Angular to React at <strong>sevdesk</strong>: 
-    <a href="/blog/from-angular-to-react" target="_blank" rel="noopener noreferrer">
+    <a href="/blog/migrating-an-enterprise-app-from-angularjs-to-react" target="_blank" rel="noopener noreferrer">
       “How We Migrated an Enterprise App from AngularJS to React Without Downtime”
     </a>.
   </p>
@@ -108,4 +108,4 @@ Modernizing a large frontend doesn’t have to mean hitting pause on everything
 
 By co-developing a strategy tailored to the client’s needs, along with shared libraries, solid patterns, and internal support, teams are able to move beyond legacy code gradually, confidently, and without disruptions.
 
-If your team is facing a legacy migration, let’s talk! We’ll help you modernize without slowing down—one component at a time.
\ No newline at end of file
+If your team is facing a legacy migration, let’s talk! We’ll help you modernize without slowing down—one component at a time.