diff --git a/packages/core/schematics/migrations/signal-migration/src/input_detection/input_decorator.ts b/packages/core/schematics/migrations/signal-migration/src/input_detection/input_decorator.ts
index 17db7ac5d18..c33715fa4bf 100644
--- a/packages/core/schematics/migrations/signal-migration/src/input_detection/input_decorator.ts
+++ b/packages/core/schematics/migrations/signal-migration/src/input_detection/input_decorator.ts
@@ -14,6 +14,7 @@ import {FatalDiagnosticError} from '@angular/compiler-cli/src/ngtsc/diagnostics'
 import {Reference, ReferenceEmitter} from '@angular/compiler-cli/src/ngtsc/imports';
 import {
   DecoratorInputTransform,
+  DirectiveMeta,
   DtsMetadataReader,
   InputMapping,
 } from '@angular/compiler-cli/src/ngtsc/metadata';
@@ -74,9 +75,20 @@ function extractDtsInput(node: ts.Node, metadataReader: DtsMetadataReader): Extr
     return null;
   }
 
-  const directiveMetadata = metadataReader.getDirectiveMetadata(
-    new Reference(node.parent as ClassDeclaration),
-  );
+  let directiveMetadata: DirectiveMeta | null = null;
+
+  // Getting directive metadata can throw errors when e.g. types referenced
+  // in the `.d.ts` aren't resolvable. This seems to be unexpected and shouldn't
+  // result in the entire migration to be failing.
+  try {
+    directiveMetadata = metadataReader.getDirectiveMetadata(
+      new Reference(node.parent as ClassDeclaration),
+    );
+  } catch (e) {
+    console.error('Unexpected error. Gracefully ignoring.');
+    console.error('Could not parse directive metadata:', e);
+    return null;
+  }
   const inputMapping = directiveMetadata?.inputs.getByClassPropertyName(node.name.text);
 
   // Signal inputs are never tracked and migrated.