diff --git a/_docs/migrate_module.md b/_docs/migrate_module.md
index ac0a6d52..d0552647 100644
--- a/_docs/migrate_module.md
+++ b/_docs/migrate_module.md
@@ -14,6 +14,7 @@ You will have someone by your side in this process. The general flow is to…
     * If this module was created with PDK delete .sync.yaml.
     * Ensure that the module has a correct `LICENSE` file in the docroot that matches the mentioned license in the `metadata.json`.
     * If the repo is a fork, to ensure pull requests go to the correct repo, [detach it from the fork network](https://docs.github.com/pull-requests/collaborating-with-pull-requests/working-with-forks/detaching-a-fork).
+    * Rename the default branch to `main` if it is not already named `main`.
 * At this point you can [transfer your own repository](https://docs.github.com/repositories/creating-and-managing-repositories/transferring-a-repository).
 * Ask an admin to
     * Verify that all webhooks are disabled.
diff --git a/_posts/2026-03-20-master-to-main.md b/_posts/2026-03-20-master-to-main.md
new file mode 100644
index 00000000..c418bce0
--- /dev/null
+++ b/_posts/2026-03-20-master-to-main.md
@@ -0,0 +1,32 @@
+---
+layout: post
+title: Group Project: Switching from `master` to `main`
+date: 2026-03-20
+github_username: rwaffen
+---
+
+Hi @everyone 👋, we have a large number of repositories, and we want to establish a clear and consistent standard for how we name our default branches across the organization.
+
+The reason for this change is to align with current defaults on GitHub, upcoming changes to Git itself, as well as standardizing language, improving clarity, and reducing confusion of having different repositories with different defaults.
+
+Since this change can involve a fair amount of work, we’d like to approach it collaboratively and involve everyone in the process.
+
+If you touch any repository and got some extra time to spend, please switch the default branch to `main` and update your local clones accordingly.
+
+<!-- TODO: Can everyone do this or do we need some special rights to do this? -->
+If you are a repository maintainer you can switch the default branch in the repository settings on GitHub.
+See the [GitHub documentation](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch).
+
+The commands to update your local clone are as follows:
+
+```shell
+git branch -m master main
+git fetch origin
+git branch -u origin/main main
+git remote set-head origin -a
+```
+
+Thx for your help! If you have any questions, feel free to ask.
+
+Cheers,
+@rwaffen