# Switching from another SDK

Source: https://pulse.mightys.dev/docs/switching/

The ingest endpoint also accepts the TelemetryDeck v2 and Aptabase v0 request formats. You keep the SDK and the signal calls you have. You change the address it sends to and use the compatibility key of your app.

## Steps

1. Create an app in Pulse. In App settings, Keys, copy the key in the format of the SDK you ship.
2. Point your SDK at the Pulse address, as in the example below, and use that key.
3. Run the app. The setup page shows the first signal arriving.

TelemetryDeck JavaScript SDK:

```
const td = new TelemetryDeck({
  appID: "YOUR_COMPATIBILITY_KEY",
  clientUser: "anonymous",
  target: "https://in.mightys.dev/v2/", // the new line
});
```

Aptabase web SDK:

```
init("YOUR_COMPATIBILITY_KEY", {
  host: "https://in.mightys.dev", // the new line
});
```

- The recipes apply to @telemetrydeck/sdk 2.x and @aptabase/web 0.5.
- The SDK you keep still decides how it identifies users and batches signals. To use our own format, move to a Pulse SDK when it suits you.
- Each app has three keys, one per format. All three write to the same app, so you can move platform by platform.

[Getting started](https://pulse.mightys.dev/docs/)
