# Migrating to KORE Super SIM Connection Events

Super SIM Connection Events are currently delivered via [Twilio's Event Streams](https://www.twilio.com/docs/events) product. As part of our process of separating from Twilio, we will stop publishing events to Twilio Event Streams on **November 1, 2024**. In order to continue to receive Super SIM Connection Events without interruption, you will need to subscribe to KORE's replacement [event streaming product](/developers/event-streams.md) before then.

You will use the [KORE Developer Portal](https://build.korewireless.com/event-stream/destination) to configure destinations and streams and send test events so you can confirm that you are able to receive events from KORE.

We have provided various guides for you to get started

* [Get started with AWS Kinesis](/developers/get-started/event-streams/aws-kinesis-quick-start.md)
* [Get started with Webhooks](/developers/get-started/event-streams/webhook-quick-start.md)
* [Send Test events](/developers/how-to/event-streams/test-my-destination.md)

We will **simultaneously** publish events to both KORE's event streaming product and Twilio's Event Stream if you have configured event streams at KORE and Twilio.

The object within the event that contains the Super SIM Connection Event specific data will remain unchanged. The metadata around that object will be different depending on if it came from KORE or Twilio. 

To ensure that you don't miss any events during the migration process, you can subscribe to both KORE's Super SIM Connection Events and Twilio's at the same time as all events will be published through both systems; however, you will need to consolidate the events and dedupe them. 

You will be able to use the `event_sid` property to dedupe events. The same event that was sent over both KORE's and Twilio's stream will have the same `event_sid`. 

{% hint style="danger" %}
If you use Super SIM Connection Events to record data usage and bill your customers, it is critical that you properly deduplicate your events, even when receiving them via just Twilio or KORE. Please ensure you have considered this in your design.
{% endhint %}

## Key Differences

### Resource Names

| Twilio Event Streams                                                                | KORE Event Streams                                                 |
| ----------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| [Event Types](https://www.twilio.com/docs/events/event-streams/event-type-resource) | [Event Types](/developers/event-streams/events.md#event-types)     |
| [Sinks](https://www.twilio.com/docs/events/event-streams/sink-resource)             | [Destinations](/developers/event-streams/destinations.md)          |
| [Subscriptions](https://www.twilio.com/docs/events/event-streams/subscription)      | [Streaming Rules](/developers/event-streams/streaming-rules.md)    |
| [Schemas](https://www.twilio.com/docs/events/event-streams/schema-resource)         | [Event Schemas](/developers/event-streams/events.md#event-schemas) |

### Event Schema

Whether you are sending events to [Kinesis](https://www.twilio.com/docs/events/webhook-quickstart#read-and-parse-the-data) or [Webhook](https://www.twilio.com/docs/events/webhook-quickstart#read-and-parse-the-data), Twilio follows the same format defined by [Cloud Events](https://github.com/cloudevents/spec/blob/v1.0/spec.md), which KORE also follows. 

The properties which will change when moving to KORE are identified below.

{% hint style="success" %}
The data schema object will remain unchanged
{% endhint %}

#### type

Your types were usually like `com.twilio.{suffix}`, which will be changed to `com.kore.{suffix}`.

#### dataschema

The data schema will be available at a different URL. 

`https://events-schemas.korewireless.com/...`

### Validating Webhook Events on Event Stream

KORE [validates ](/developers/how-to/webhooks/validate-webhook-signatures.md)Webhooks the same way for callbacks and event streams. 

### Streaming Events to Destinations

You will be able to receive events via [AWS Kinesis](/developers/get-started/event-streams/aws-kinesis-quick-start.md) or [webhooks](/developers/get-started/event-streams/webhook-quick-start.md). 

{% hint style="danger" %}
**Twilio Segment** will **not** be an available destination type. If you use this Sink type today, plan to use one of the other destination types and forward events into Twilio Segment yourself.
{% endhint %}


---

# 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.korewireless.com/twilio-iot-acquisition/migration-guides/migrating-to-kore-super-sim-connection-events.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.