> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squasher.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Better Stack to Squasher

> Cut over from Better Stack to Squasher with a staged forwarding and alert migration plan.

The safest migration is to forward one Better Stack source into Squasher, confirm that incident quality and context hold up, then move alerts and runbooks over in small steps.

## Setup

<Steps>
  <Step title="Identify the first source group">
    Pick one service, environment, or log source with clear ownership and regular traffic.
  </Step>

  <Step title="Create the connector">
    Follow the [Better Stack integration](/integrations/betterstack) guide and add Squasher as an
    additional destination.
  </Step>

  <Step title="Mirror before cutover">
    Keep Better Stack live while Squasher learns the same stream and your team validates grouping
    and alerts.
  </Step>
</Steps>

## Verify

* Compare recent error events in both tools.
* Confirm fields needed by on-call responders still exist in Squasher.
* Confirm incident noise does not increase when warning and info logs are included for context.

## Migrate

* Move alert routing after Squasher issue quality is stable.
* Recreate the dashboards or saved searches your team uses during incidents.
* Repeat the process for the next source group instead of switching everything at once.

## Hot-swap

* Disable duplicate notifications only after responders trust Squasher.
* Keep an overlap window through at least one deploy cycle.
* Rotate the connector key after the old forwarder is retired.

## Agent handoff

```text theme={null}
Run a Better Stack to Squasher migration plan for project <project_id>. Pick one source group, mirror it, compare fields and error grouping, recreate essential alerting, and ask before disabling duplicate notifications or rotating keys.
```