The author details their migration from GitHub to Codeberg, highlighting both the challenges and successes of the process. Initially, they spent about an hour setting up their profile on Codeberg, followed by manually migrating repositories using Codeberg’s “migrate from GitHub” feature. One significant hurdle was GitHub’s API rate limits, which complicated the import process when attempting to migrate multiple repositories simultaneously. The author appreciated the ability to transfer issues, pull requests, wikis, and releases, making it easier to eliminate reliance on GitHub. Repointing links to Codeberg involved using command line tools to replace GitHub URLs within their repositories. They created a script to update their GitHub repositories, making the process manageable. The migration included considerations for continuous integration (CI), where the author decided to streamline their CI requirements, focusing only on essential projects. Codeberg offers two CI solutions, and they opted for Forgejo Actions, which closely resembles GitHub Actions. However, they noted differences in available resources and runner setups, leading to adaptations in their CI configurations. The final step involved re-hosting their website, previously on GitHub Pages. After finding Codeberg Pages inadequate due to maintenance issues, the author discovered git-pages, which offers similar functionality without downtime during migration. This service allows for server-side redirects and supports custom headers, enhancing their website management. Ultimately, they find this new setup more satisfactory than GitHub Pages and express enthusiasm for future developments in Codeberg’s offerings.