2015-09-11 14:41:01 +05:30
|
|
|
# Migrating projects to a GitLab instance
|
|
|
|
|
|
|
|
|
|
1. [Bitbucket](import_projects_from_bitbucket.md)
|
2015-12-23 02:04:40 +05:30
|
|
|
1. [GitHub](import_projects_from_github.md)
|
|
|
|
|
1. [GitLab.com](import_projects_from_gitlab_com.md)
|
|
|
|
|
1. [FogBugz](import_projects_from_fogbugz.md)
|
2017-08-17 22:00:37 +05:30
|
|
|
1. [Gitea](import_projects_from_gitea.md)
|
2015-12-23 02:04:40 +05:30
|
|
|
1. [SVN](migrating_from_svn.md)
|
2015-09-11 14:41:01 +05:30
|
|
|
|
2015-12-23 02:04:40 +05:30
|
|
|
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.
|
