diff --git a/migrations_lockfile.txt b/migrations_lockfile.txt
index 39d7b49cc7d455..7e736f898ae0b9 100644
--- a/migrations_lockfile.txt
+++ b/migrations_lockfile.txt
@@ -13,4 +13,4 @@ replays: 0004_index_together
 sentry: 0759_remove_spanattributeextraction_tables
 social_auth: 0002_default_auto_field
 uptime: 0011_remove_uptime_whois_columns_db
-workflow_engine: 0004_workflowactions
+workflow_engine: 0005_datacondition
diff --git a/src/sentry/workflow_engine/migrations/0005_datacondition.py b/src/sentry/workflow_engine/migrations/0005_datacondition.py
new file mode 100644
index 00000000000000..66adb1b024e2a3
--- /dev/null
+++ b/src/sentry/workflow_engine/migrations/0005_datacondition.py
@@ -0,0 +1,63 @@
+# Generated by Django 5.1.1 on 2024-09-12 21:15
+
+import django.db.models.deletion
+from django.db import migrations, models
+
+import sentry.db.models.fields.bounded
+from sentry.new_migrations.migrations import CheckedMigration
+
+
+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", "0004_workflowactions"),
+    ]
+
+    operations = [
+        migrations.CreateModel(
+            name="DataCondition",
+            fields=[
+                (
+                    "id",
+                    sentry.db.models.fields.bounded.BoundedBigAutoField(
+                        primary_key=True, serialize=False
+                    ),
+                ),
+                ("date_updated", models.DateTimeField(auto_now=True)),
+                ("date_added", models.DateTimeField(auto_now_add=True)),
+                ("condition", models.CharField(max_length=200)),
+                ("threshold", models.FloatField()),
+                ("condition_result", models.JSONField()),
+                ("type", models.CharField(max_length=200)),
+                (
+                    "detectors",
+                    models.ForeignKey(
+                        on_delete=django.db.models.deletion.CASCADE, to="workflow_engine.detector"
+                    ),
+                ),
+                (
+                    "workflow_action",
+                    models.ForeignKey(
+                        on_delete=django.db.models.deletion.CASCADE,
+                        to="workflow_engine.workflowaction",
+                    ),
+                ),
+            ],
+            options={
+                "abstract": False,
+            },
+        ),
+    ]
diff --git a/src/sentry/workflow_engine/models/data_condition.py b/src/sentry/workflow_engine/models/data_condition.py
index 8cffbfe8bfc938..176004a73d947d 100644
--- a/src/sentry/workflow_engine/models/data_condition.py
+++ b/src/sentry/workflow_engine/models/data_condition.py
@@ -2,7 +2,8 @@
 
 from sentry.backup.scopes import RelocationScope
 from sentry.db.models import DefaultFieldsModel, region_silo_model, sane_repr
-from sentry.workflow_engine.models import Detector, WorkflowAction
+from sentry.workflow_engine.models.detector import Detector
+from sentry.workflow_engine.models.workflow_action import WorkflowAction
 
 
 @region_silo_model