Migration from Gerrit 2.13 to 3.9
Change-Id: I853fb0306a46830161691b8280c773ee031be9ef
diff --git a/schedule.md b/schedule.md
index 6b9ab03..3453534 100644
--- a/schedule.md
+++ b/schedule.md
@@ -34,6 +34,7 @@
| 08:30 | Breakfast / Check-in
| 09:30 | [Sustaining Git repo performance under heavy load](sessions/sustaining-git-repo-performance-under-heavy-load.md)
| 10:15 | [Qualcomm's Gerrit management overview from Devops/SRE](sessions/devops-qcom.md)
+| 11:00 | [Migration from Gerrit 2.13 to 3.9: Challenges and Lessons](sessions/migrating-from-2.13-to-3.9.md)
| 12:30 | Lunch & Networking
| 17:00 | End of the day
diff --git a/sessions/migrating-from-2.13-to-3.9.md b/sessions/migrating-from-2.13-to-3.9.md
new file mode 100644
index 0000000..f81e62e
--- /dev/null
+++ b/sessions/migrating-from-2.13-to-3.9.md
@@ -0,0 +1,18 @@
+# Migration from Gerrit 2.13 to 3.9: Challenges and Lessons Learned
+
+The migration from Gerrit 2.13 to 3.9 presents a significant shift,
+involving deep structural changes that can be challenging to navigate.
+One of the key hurdles is the transition from the legacy ReviewDB to NoteDB,
+which fundamentally changes how data is stored and managed.
+In this talk, I will discuss our experience migrating across these versions
+on a per-project basis to minimize downtime and ensure a smooth transition
+for teams.
+
+We’ll explore the technical challenges faced during the migration,
+including data integrity issues, performance impacts, and the complexities
+introduced by the major architectural shift. By sharing insights from this
+process, attendees will gain a clearer understanding of how to plan,
+execute, and mitigate risks when undertaking such a large-scale Gerrit
+upgrade, especially when dealing with long-lived versions like Gerrit 2.13.
+
+*[Fabio Ponciroli, Senior Engineer / GerritForge](../speakers.md#fponciroli)*
\ No newline at end of file
