5a20716c7e
* Rename map topic * Delete map topic * Rename map topic * Add redirect * Remove last two map topics * Move article on adding a remote into a long-form guide * Move article on changing a remote's URL * Move articles on renaming and removing remotes * Move remote URL article * Fix typo * Remove category index file * Move a few articles to the new category * Move a few more files * Move managing remote repos article * Move the rest of the getting started with git map topic * Move the first half of the using git map topic * Move the rest of the articles and 🔥 the directory * Fix failing test * Remove Using Git from product index * Apply suggestions from code review Co-authored-by: Laura Coursen <lecoursen@github.com> * Apply suggestions from code review Co-authored-by: Laura Coursen <lecoursen@github.com>
57 lines
2.2 KiB
Markdown
57 lines
2.2 KiB
Markdown
---
|
|
title: Source code migration tools
|
|
intro: You can use external tools to move your projects to GitHub.
|
|
redirect_from:
|
|
- /articles/importing-from-subversion/
|
|
- /articles/source-code-migration-tools
|
|
versions:
|
|
free-pro-team: '*'
|
|
enterprise-server: '*'
|
|
github-ae: '*'
|
|
---
|
|
|
|
{% if currentVersion == "free-pro-team@latest" %}
|
|
|
|
We recommend using [GitHub Importer](/articles/about-github-importer) to import projects from Subversion, Mercurial, Team Foundation Server, or another Git repository. You can also use these external tools to convert your project to Git.
|
|
|
|
{% endif %}
|
|
|
|
### Importing from Subversion
|
|
|
|
In a typical Subversion environment, multiple projects are stored in a single root repository. On GitHub, each of these projects will usually map to a separate Git repository for a user account or organization. We suggest importing each part of your Subversion repository to a separate GitHub repository if:
|
|
|
|
* Collaborators need to check out or commit to that part of the project separately from the other parts
|
|
* You want different parts to have their own access permissions
|
|
|
|
We recommend these tools for converting Subversion repositories to Git:
|
|
|
|
- [`git-svn`](https://git-scm.com/docs/git-svn)
|
|
- [svn2git](https://github.com/nirvdrum/svn2git)
|
|
|
|
### Importing from Mercurial
|
|
|
|
We recommend [hg-fast-export](https://github.com/frej/fast-export) for converting Mercurial repositories to Git.
|
|
|
|
### Importing from Team Foundation Server
|
|
|
|
We recommend these tools for moving changes between Team Foundation Server and Git:
|
|
|
|
- [git-tfs](https://github.com/git-tfs/git-tfs)
|
|
- [Git-TF](https://gittf.codeplex.com/)
|
|
|
|
{% tip %}
|
|
|
|
**Tip:** After you've successfully converted your project to Git, you can [push it to {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
|
|
|
|
{% endtip %}
|
|
|
|
{% if currentVersion == "free-pro-team@latest" %}
|
|
|
|
### Further reading
|
|
|
|
- "[About GitHub Importer](/articles/about-github-importer)"
|
|
- "[Importing a repository with GitHub Importer](/articles/importing-a-repository-with-github-importer)"
|
|
- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})
|
|
|
|
{% endif %}
|