The migration on a technical level is easy. I did spend multiple hours though fixing non-fast-forwarded merges, accidentally created merges after pulling, inco

The migration on a technical level is easy. I did spend multiple hours though fixing non-fast-forwarded merges, accidentally created merges after pulling, incorrect author names and one accidental force-push. All of these I could have prevented using policy on the server, but I would still have had to help explaining the underlying issues in order to a) get the broken commit in and b) make sure it doesn't happen again. Explaining takes much longer than just fixing. The problem isn't technical. It's human. The more employees/team members you have, the more complicated it will become to put all on the same boat. My experience above comes from a team with 4 people of which two were already git users (one of them was me). I don't want to think what this migration would have meant if we were 10 or even 100 people.