2017-08-16 07:05:13 -04:00
|
|
|
# Migrating projects to a GitLab instance
|
|
|
|
|
|
|
|
|
|
1. [From Bitbucket.org](bitbucket.md)
|
2017-09-06 10:59:07 -04:00
|
|
|
1. [From ClearCase](clearcase.md)
|
|
|
|
|
1. [From CVS](cvs.md)
|
|
|
|
|
1. [From FogBugz](fogbugz.md)
|
2017-08-16 07:05:13 -04:00
|
|
|
1. [From GitHub.com of GitHub Enterprise](github.md)
|
|
|
|
|
1. [From GitLab.com](gitlab_com.md)
|
|
|
|
|
1. [From Gitea](gitea.md)
|
2017-08-29 06:56:59 -04:00
|
|
|
1. [From Perforce](perforce.md)
|
2017-09-06 10:59:07 -04:00
|
|
|
1. [From SVN](svn.md)
|
2017-08-30 11:57:45 -04:00
|
|
|
1. [From TFS](tfs.md)
|
2017-08-16 07:05:13 -04:00
|
|
|
|
|
|
|
|
In addition to the specific migration documentation above, you can import any
|
|
|
|
|
Git repository via HTTP from the New Project page. Be aware that if the
|
|
|
|
|
repository is too large the import can timeout.
|
|
|
|
|
|
|
|
|
|
## Migrating from self-hosted GitLab to GitLab.com
|
|
|
|
|
|
|
|
|
|
You can copy your repos by changing the remote and pushing to the new server,
|
|
|
|
|
but issues and merge requests can't be imported.
|
|
|
|
|
|
|
|
|
|
If you want to retain all metadata like issues and merge requests, you can use
|
|
|
|
|
the [import/export feature](../settings/import_export.md).
|
