See this article on BitBucket (alternative to GitHub by Atlassian, it offers free private repos):
You have to adapt it, since it covers the migration from Atlassian OnDemand svn repo and BitBucket team account, and I never tried it.
Googling about SourceTree and SVN I found this: http://www.third-helix.com/2013/09/using-sourcetree-with-subversion-hint-dont/
It's dated Semptember 2013, and I suspect some or all the issues are still there in the latest version, but I don't know for sure.
In the past I migrated some old repos simply creating from scratch a new Git repo, and doing an initial commit of the current source tree, creating gitignore and gitattributes files, and so on. If I had several branches, I manually recreated the active branches in Git. Say goodbye to the history.
Pay attention to binary files: never store large binary files in git repos. If you have a big svn repo full of large binary files, don't migrate to git.
So, I've followed the tutorial that Stefan Saasen posted and after some tweaking I was successfull.
The repository I was migrating didn't follow any specific standard with the "trunk", "branches" and "tags" directories. It had no branches history and consisted only in a root folder and subfolders along with hundreds of commits.
What I did was point the "trunk" to the root of the repository, to "fake" the master branch. This apparently worked pretty well. :)
We’ve been building a plugin to integrate Bitbucket Server and Jenkins CI, and I’m excited to announce that our alpha is ready to download and install. It lets you seamlessly configure a Jenkins job ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events