Services engagements can take three forms. These include SKUs, standard SOWs, and custom SOWs. For custom SOWs, the workflow for SOW creation involves a partnership between the SA/TAM and the Professional Services Engineering team.
This page is designed to collect details around the types of questions that are valuable in discovering the customer's required capabilities. That will help the team align the SOW with the positive business outcomes the customer is looking for with a services engagement. While not an exhaustive list, these questions, and suggestions will help spark the discovery conversations.
Migrations are one of the most complex types of services in any technical field. Systems store data in a variety of ways that evolves. Also, customers and users often use the same data model and system to represent completely different logical units to their teams. To ensure a transition that meets the customer's needs, we want to make sure we understand their usage of their current systems.
The following questions are about bringing multiple GitLab instances together into a single "parent" instance:
SVN to Git Questions:
Repository Project 1 branches/trunks/tags Project 2 branches/trunks/tags
Trunk Project 1 Project 2 Tags tag name Project 1 Project 2 Branches Branch name Project 1 Project 2
Note: We have currently suspended the offering for Professional Services to help customers migrate from self-managed to GitLab.com. The Product team is looking to better support these transitions in an upcoming release. Once that import/export capability is released, we will reconsider our ability to provide this service.
Self-Manged to GitLab.com Questions:
For scoping infrastructure implementation, we have several questions that can help us understand the scope. To get started, make a copy of the spreadsheet below and fill in the answers. If there are questions you want to add, ping the
@ps-team in Slack channel #professional-services. Then you can attach this document to the issue created by the GitLab Services (SoW) Calculator.
Note: This document contains tabs for various public and private cloud providers - AWS, GCP, Azure, OpenShift and other on-prem deployments - you should only have to fill out the tab(s) relative to your customer.