diff --git a/src/content/daily-email/2023-09-05.md b/src/content/daily-email/2023-09-05.md
new file mode 100644
index 00000000..093df338
--- /dev/null
+++ b/src/content/daily-email/2023-09-05.md
@@ -0,0 +1,24 @@
+---
+title: >
+  Spring clean before upgrading
+pubDate: 2023-09-05
+permalink: >
+  archive/2023/09/05/spring-clean-before-upgrading
+tags:
+  - drupal
+  - software-upgrades
+---
+
+One of the first things I do when reviewing whether an application can be upgraded is to look for anything that can be removed.
+
+If it has modules that aren't used, uninstall and remove them.
+
+A common one for Drupal projects is modules left from previous migrations, such as from Field Collections to Paragraphs that are no longer needed but still present.
+
+Remove any old themes that are no longer used.
+
+If you have content types, fields or views that aren't used, remove them, assuming you don't need the data.
+
+Remove unused routes, Controllers or other classes not used in custom modules, or any other unused custom code.
+
+Less moving parts means less to upgrade now and maintain in the future.