Creation of an SH-based database

You want to create a new SH-based database but you don't know how it works? Guess what, you are about to know everything there is to know. You'll see, it's easy.

How long does it take

Depends on how fast the client tests and when they want to schedule the downtime, but usually between 1 and 2 weeks.

1. Ask for a SAAS to SH migration

The very first thing to do is to create a ticket under the Saas-Customization project. In this ticket, you have to provide the following mandatory information. A ticket missing these will be refused.

• The subscription code
• SAAS URL
• The Github Login(s) to link to the SH DB (Yours and your clients')
• The staging(s) names and number to be created
• The customer has a custom domain name linked to their SAAS DB

To help you save some time, here is a template you can copy-paste and fill

Subscription code:
SAAS URL:
Github Login(s):
# of staging(s):
Staging name(s):
Customer has a custom domain name:

Also, make sure to complete the following:

• Set the Sales Order Item and Parent Task
• Check the "No maintenance cost" and "No count as dev hour" boxes in the Extra Info tab
• Do not assign yourself

2. Wait for your ticket to be assigned

The Quickstart team is generally quite fast at assigning consultant on their ticket but some of them might take more time than others, it depends on the availability of consultants.

3. FIRST STEP: A consultant has been assigned

A consultant has been assigned and will migrate the database from SAAS to SH. The first step consist in a "fake"/"dummy" migration used only to make sure everything is ok. The consultant will let you know when the DB has been migrated and you can let your client know. The client cannot work on the DB, it will be deleted!! This step is used only to make sure everything is ok

4. The client confirmed everything is ok

You can let the consultant know that they can move onto the second step. The consultant will provide you will their disponibilites to arrange a precise time where they will proceed to the real migration. During this time, the client cannot touch their database and everything they do on it will be lost.

5. SECOND STEP: Consultant confirmed migration is done

When the consultant confirms the migration is done, you can go ahead an let the client know that they can use the database as usual. Their database will be hosted on SH now.