Gitlab/Gitlab-Migrations.md

@@ -44,11 +44,38 @@ If the clients' self-managed instance is not accessible by HTTPS, you must follo
 6. The project will be imported after a few minutes.
 
 ## Migrating from SAAS to Self-Managed
-This details migrating from gitlab.com to a self-managed VM. 
+This details migrating from gitlab.com to a self-managed VM. This involves integrating your GitLab instance with gitlab.com, detailed [here](https://docs.gitlab.com/ee/integration/gitlab.html).
 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.
 
+### GitLab Integration
+Integrating with gitlab.com allows you to connect your website account with your private instance.
+1. Sign into gitlab.com and select your profile in the top right.
+2. Click on edit profile.
+3. On the right sidebar, select "Applications."
+4. Fill in details for adding a new application, selecting a name and a Redirect URI:
+```
+# You can also use a non-SSL URL, but you should use SSL URLs.
+https://your-gitlab.example.com/import/gitlab/callback
+https://your-gitlab.example.com/users/auth/gitlab/callback
+```
+5. Select "Save Application" and save the completed details for later.
+6. Open the configuration file for your private GitLab instance: `sudo nano /etc/gitlab/gitlab.rb`
+7. Add in these configuration details: 
+```
+gitlab_rails['omniauth_providers'] = [
+  {
+    name: "gitlab",
+    # label: "Provider name", # optional label for login button, defaults to "GitLab.com"
+    app_id: "YOUR_APP_ID",
+    app_secret: "YOUR_APP_SECRET",
+    args: { scope: "read_user" } # optional: defaults to the scopes of the application
+  }
+]
+```
+8. Save the configuration file and run `sudo gitlab-ctl reconfigure`.
+
 ### Group Import
 In the newly-created instance, you should be able to access it as an admin. This allows you to use the project and group import tool. 
 1. On the target instance, select New Group.