# Customer Go Live Checklist

When migrating to the DL Trading/IMGA golf pricing service (and away from the Mustard/Dijon service ahead of the 13th October 2025 cut-off date), here are some key steps to follow to ensure you are in the best possible position for a smooth transition:

### Mustard/Dijon SSH Integration

1. **Ensure you have transitioned from the IMGA staging to Production SSH service**

Depending on your existing Mustard/Dijon through the SSH service, and also with the Ryder Cup 2025 on the horizon (26-28th Sept), you may well opt to continue running the Mustard/Dijon service until that time and transition thereafter. Both SSH services will be available for Operators to transition when they see fit. A reminder that the Mustard/Dijon services will be turned off on the 13th October 2025 so please prepare your transition before that date.

<mark style="color:orange;">Current (Mustard/Dijon)</mark>

STAGING: `[username].golf-feed-staging.dijonsystems.com`

PROD: `[username].golf-feed.dijonsystems.com`

<mark style="color:$success;">**Future (DL Trading/IMGA)**</mark>

STAGING: **`[username]@golf-odds-distribution.staging.imgarena.dev`**

PROD: **`[username]@golf-odds-distribution.services.imgarena.com`**

Supported ports: 22 and 2093

{% hint style="info" %}
Please ensure you have migrated over to the DL Trading/IMGA production SSH service upon go live and not the staging SSH service to ensure the most accurate prices and service performance
{% endhint %}

2. **You have verified the coverage level and relevant tiers for the remaining golf tournaments across the specific tours for the rest of the 2025 calendar year. This can be obtained from either:**

* The /tournaments REST API in DDE (which will also provide the tournament id)
* The weekly email send via our Customer Success team (<customersuccess@updates.imgarena.com>) entitled ‘IMGA Weekly Golf Coverage Update’
* The below (downloadable xls file), showing the remaining tournaments in 2025 with coverage levels. LPGA uploaded now, DPWT and PGA will soon be added after consulatation with DL Trading.

{% file src="/files/gfKn2bvv4yU2PATdXL8b" %}

#### 3. You have then verified the golf markets you are interested in are available.

Please see the markets available detailed [here](https://docs.imgarena.com/imga-dl-trading-odds-distribution-service/odds-distribution-service/supported-market-types)

#### 4. Once you have instigated the init, this alone will not start the data flow process and at this point you should explicitly subscribe to either all or selected markets.

More Info [here](https://docs.imgarena.com/imga-dl-trading-odds-distribution-service/odds-distribution-service/feed-specification#subscription)

#### 5. For support related queries, what are the best channels for communication?

Depending on your existing communication with Mustard/Dijon and IMGA on the golf pricing service, we want to make the process as straightforward as possible and not change too much in terms of communication channels, whether that be raising email support tickets which are logged in Freshservice or utilising existing or new slack channels.

Upon go-live we will ensure the method of communication is clear to you. IMGA and DL Trading will have support staff and traders available to answer queries pre or during golf tournaments. We will also have tech support on call through the duration of tournaments to look into any any issues/outages that could occur.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sportradar.com/imga-dl-trading-odds-distribution/customer-go-live-checklist.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.