From e7ee00514b34d2e75975cb2d63775a0595fbdc48 Mon Sep 17 00:00:00 2001
From: Camila Macedo <7708031+camilamacedo86@users.noreply.github.com>
Date: Tue, 26 Nov 2024 20:03:56 +0000
Subject: [PATCH] doc: add clarification about current state of OLMv1 at
 upstream

---
 docs/index.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/index.md b/docs/index.md
index 373345caa..567669207 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -37,3 +37,12 @@ For more details on the evolution of OLM and the roadmap for v1, explore the fol
 
 - [Multi-Tenancy Challenges, Lessons Learned, and Design Shifts](project/olmv1_design_decisions.md)
 - [OLM v1 Roadmap](project/olmv1_roadmap.md)
+
+## Can I Migrate from OLMv0 to OLMv1?
+
+There is currently no concrete migration strategy due to the [conceptual differences between OLMv0 and OLMv1](project/olmv1_design_decisions.md).
+OLMv1, as of writing, supports a subset of the existing content supported by OLMv0.
+For more information regarding the current limitations of OLMv1, see [limitations](project/olmv1_limitations.md).
+
+If your current usage of OLMv0 is compatible with the limitations and expectations of OLMv1, you may be able to manually
+transition to using OLMv1 following the standard workflows we have documented.