diff --git a/content/en/containers/guide/datadogoperator_migration.md b/content/en/containers/guide/datadogoperator_migration.md
index 4a506b2a5c41f..67dd31ebd8c5f 100644
--- a/content/en/containers/guide/datadogoperator_migration.md
+++ b/content/en/containers/guide/datadogoperator_migration.md
@@ -1,5 +1,14 @@
 ## Migrating to version 1.0 of the Datadog Operator
 
+<div class="alert alert-warning">
+The <code>v1alpha1</code> <code>DatadogAgent</code> reconciliation in the Operator is deprecated since v1.2.0+ and will be removed in v1.7.0. After it's removed, you will not be able to configure the Datadog Operator to reconcile the <code>v1alpha1</code> <code>DatadogAgent</code> CRD. However, you will still be able to apply a <code>v1alpha1</code> manifest with the conversion webhook enabled using <code>datadogCRDs.migration.datadogAgents.conversionWebhook.enabled</code>.
+</div>
+
+<div class="alert alert-warning">
+<code>DatadogAgent</code> <code>v1alpha1</code> and the conversion webhook will be removed in v1.8.0. After it's removed, you will not be able to migrate unless you use earlier version of the Operator.
+</div>
+
+
 Datadog Operator v0.X uses `v1alpha1` of the DatadogAgent custom resource. Datadog Operator v1.X reconciles `v2alpha1`.
 
 This guide describes how to migrate to the `v2alpha1/DatadogAgent` custom resource from `v1alpha1/DatadogAgent`.