diff --git a/migrations_lockfile.txt b/migrations_lockfile.txt
index bd41aa6bf450bc..1de210179abdfb 100644
--- a/migrations_lockfile.txt
+++ b/migrations_lockfile.txt
@@ -23,4 +23,4 @@ tempest: 0002_make_message_type_nullable
 
 uptime: 0030_status_update_date
 
-workflow_engine: 0035_action_model_drop_legacy_fields
+workflow_engine: 0036_action_remove_legacy_fields
diff --git a/src/sentry/workflow_engine/migrations/0036_action_remove_legacy_fields.py b/src/sentry/workflow_engine/migrations/0036_action_remove_legacy_fields.py
new file mode 100644
index 00000000000000..2b156d6491511c
--- /dev/null
+++ b/src/sentry/workflow_engine/migrations/0036_action_remove_legacy_fields.py
@@ -0,0 +1,43 @@
+# Generated by Django 5.1.5 on 2025-03-07 00:47
+
+from sentry.new_migrations.migrations import CheckedMigration
+from sentry.new_migrations.monkey.fields import SafeRemoveField
+from sentry.new_migrations.monkey.state import DeletionAction
+
+
+class Migration(CheckedMigration):
+    # This flag is used to mark that a migration shouldn't be automatically run in production.
+    # This should only be used for operations where it's safe to run the migration after your
+    # code has deployed. So this should not be used for most operations that alter the schema
+    # of a table.
+    # Here are some things that make sense to mark as post deployment:
+    # - Large data migrations. Typically we want these to be run manually so that they can be
+    #   monitored and not block the deploy for a long period of time while they run.
+    # - Adding indexes to large tables. Since this can take a long time, we'd generally prefer to
+    #   run this outside deployments so that we don't block them. Note that while adding an index
+    #   is a schema change, it's completely safe to run the operation after the code has deployed.
+    # Once deployed, run these manually via: https://develop.sentry.dev/database-migrations/#migration-deployment
+
+    is_post_deployment = False
+
+    dependencies = [
+        ("workflow_engine", "0035_action_model_drop_legacy_fields"),
+    ]
+
+    operations = [
+        SafeRemoveField(
+            model_name="action",
+            name="target_display",
+            deletion_action=DeletionAction.DELETE,
+        ),
+        SafeRemoveField(
+            model_name="action",
+            name="target_identifier",
+            deletion_action=DeletionAction.DELETE,
+        ),
+        SafeRemoveField(
+            model_name="action",
+            name="target_type",
+            deletion_action=DeletionAction.DELETE,
+        ),
+    ]