Subversion to Git Migration as a Service
Your chance to re-write history
modernize your software development practice
Migrating from subversion to git can be complicated and time consuming. Let us help.
Refactor
Microservices you say?
Create multiple git repos from one subversion repo, each with distinct content and full history.
Does anyone even understand this?
Get out of the weeds
Everyone has an opinion, yet there are very few answers for your exact situation. Most suggestions require arcane command-line foo and trial and error that we found to be unreliable and very time consuming. Devs don't care about the details. It just needs to work.
Keep (Relevant) History
It's all in there. The full copy of dojo someone committed back in '04. That 50MB PDF from your digital design firm. The 100MB data file that was going to help with integration testing. That huge binary you needed to ship.
Trim the bloat. Keep what you want. Do it responsibly.
FORKZERO blog
Thoughts, musings, and ruminations.3 de febrero de 2017312,567 commits, 49GB of compressed repo, and stackoverflow. That is how the migration began....Contact Us
We are enrolling for our private beta. Tell us about your repos.
Don't be afraid to reach out. You + us = awesome.