Gitlab/Gitlab-Migrations.md

@@ -24,14 +24,14 @@ If the clients' self-managed instance is not accessible by HTTPS, you must follo
 2. Find the project/group you are looking for, select on the left Settings > General > Advanced
 3. Scroll down to Export Project/Group and generate an export. Wait a few minutes, you may need to refresh the page.
 4. Download the export and keep the archive where you can easily access it.
-5. On the destination instance, select the group you want to export project/group to, and click on New Project
+5. On the destination instance, select the group you want to export the project/group to and click on New Project
 6. Select Import Project
 7. Select GitLab export
 8. Fill in the details for the project/group
 9. The project will be imported after a few minutes
 
 ## Migrating from SAAS to Self-Managed
-This details migrating from gitlab.com to a self-manged VM. 
+This details migrating from gitlab.com to a self-managed VM. 
 Before beginning with the migration you need to know these details:
 - The client must specify which cloud they wish to host their instance in.
 - You must have admin access to the target instance
@@ -41,4 +41,12 @@ In the newly-created instance, you should be able to access as an admin. This al
 1. On the target instance, select New Project.
 2. Select Gitlab.com
 3. Fill in the details for the project
-4. The project will be imported after a few minutes
+4. The project will be imported after a few minutes
\ No newline at end of file
+
+## Migrating from GitHub to GitLab
+If you are migrating to a self-managed GitLab instance, you can use the GitHub import rake task detailed [here](https://docs.gitlab.com/ee/administration/raketasks/github_import.html).
+
+### GitLab Enterprise Migrations
+To migrate from GitLab Enterprise, you must enable GitHub integration, found [here](https://docs.gitlab.com/ee/integration/github.html).
+
+To import projects, you can use the import [API](https://docs.gitlab.com/ee/api/import.html).