> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/audiovisual/migration-from-img-arena-to-sportradar-streaming-platform.md). # Migration from IMG Arena to Sportradar Streaming Platform To ensure a smooth transition from IMGA to Sportradar streaming services, you should first review your current setup and determine whether you are already using Sportradar services. If so, parts of the technical foundation and entitlements may already be in place, which can simplify and accelerate the migration. You will also need to confirm your Bookmaker ID (BID), as this is the central identifier used to activate and manage streaming services within Sportradar. Ensuring that the correct BID is used from the outset is essential, as all content access and entitlements are linked to it. Based on your account structure, you should decide whether to activate streaming on your existing BID or whether a new BID is required. While using an existing BID is typically the fastest and most straightforward option, certain operational or structural setups may require a separate account. This decision should be made early, as it directly impacts the overall configuration and management of your services. In addition, you should review any dependencies on IMGA-specific products, such as the Event Center. If such components are in use, additional steps may be needed to ensure continued functionality, including transitioning to alternative solutions or adapting existing workflows. For efficient execution, you should assign a dedicated technical contact within your organisation who can coordinate the integration, testing, and validation activities with Sportradar. Clear ownership helps to avoid delays and ensures smooth communication throughout the migration. Finally, you should align on a migration timeline that fits your internal planning while taking into account that the IMGA API will be deprecated by the end of 2026. Early planning allows for proper prioritisation and helps ensure that your services transition without disruption. ### Technical & Operational Differences: IMGA vs. Sportradar AV Clients should note the following core differences between the two platforms to ensure a smooth transition: | Feature | IMG Arena (IMGA) Platform | Sportradar AV Platform | | ------------------------ | ----------------------------------------------------------- | -------------------------------------------------- | | **API Domains** | srarena.io (Operationally supported until **Dec 31, 2026**) | api.sportradar.com (AV API) | | **Management Interface** | Arena Live Streaming Console | Sportradar Status/Console | | **Event Discovery** | Specific IMGA Events API | AV API Events endpoint (max 1 request/min) | | **Analytics/CSID** | Varies by implementation | **Mandatory** submission of unique csid | | **Compliance** | IMGA-specific guidelines | Strict media rights rules (e.g., <33% screen size) | **Critical Migration Considerations** * **Domain Support Window:** Please note that while we are driving the migration to the Sportradar AV platform, the existing IMGA srarena.io domains will remain fully operational for current integrations until **December 31, 2026**. This provides a clear window for planning, though we recommend initiating the transition well ahead of this date to avoid end-of-year pressure. * **Mandatory Unique CSIDs:** Unlike some past implementations where user tracking may have been optional or configurable, the Sportradar AV platform requires the **mandatory submission of a unique csid (customer ID)** for every end-user. This is essential for both regulatory reporting and content entitlement validation. Clients should audit their current user tracking and ensure that a unique identifier is correctly passed in their API requests to prevent content access issues. * **Infrastructure Polling:** The Sportradar AV API requires strict adherence to request frequency to ensure platform stability. Clients must ensure their integration requests the AV Events endpoint **no more than once per minute**. * **Visual Compliance:** Sportradar enforces strict visual compliance rules—most notably, video player sizes cannot exceed 33% of the total screen area on desktop or tablet devices for standard content. If a client’s current UI design exceeds these limits, it must be adapted as part of the migration process. * **System Alerts:** Clients should transition their monitoring workflows to use the [Sportradar Status page](https://sr-status.sportradar.com/) to receive alerts regarding maintenance or updates, replacing the legacy notification workflows within the Arena Console. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.sportradar.com/audiovisual/migration-from-img-arena-to-sportradar-streaming-platform.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.