Bugsnag migration guide

Migrate from Bugsnag to AllStak

Errors, breadcrumbs, and releases all map directly. The Bugsnag migration is a short SDK swap plus one sprint of running both tools side by side.

Start free AllStak vs Bugsnag

What changes — and what stays familiar

If you are planning a Bugsnag migration, the day-to-day workflow barely changes: exceptions arrive grouped, breadcrumbs show what led up to the failure, and releases tell you which deploy introduced a regression. What changes is the scope of the platform around those errors. In AllStak, the same project also collects logs, distributed traces, uptime checks, infrastructure metrics, and session replay — so the question shifts from "what broke" to "why" without leaving the tool.

Bugsnag's stability score does not exist under that name in AllStak — instead you track error rates per release and watch release health directly, which answers the same underlying question: is this version safe to roll forward? This guide walks the full migration honestly, including the one constraint to plan around: historical Bugsnag data does not transfer.

Why teams switch from Bugsnag

The reasons behind most Bugsnag migrations come down to scope, billing, and region.

More than crash reporting

Bugsnag is focused on error and crash monitoring; logs, uptime, traces, and infrastructure all need other vendors. AllStak puts the whole picture in one platform, so error triage and root cause live in the same place.

Flat pricing, no event anxiety

Bugsnag bills by event volume, so an error storm has a billing dimension on top of the operational one. AllStak's flat plans mean a rough deploy costs you sleep, not budget.

Built for KSA and GCC teams

Saudi data residency, SAR pricing, and an Arabic-first dashboard alongside English. AllStak fits regional procurement and daily operations in a way global error trackers do not.

How to migrate from Bugsnag, step by step

Six steps, shown here for a React app — the same flow applies across all 25+ AllStak SDKs.

1
Create an AllStak project and copy the API key
Sign up at app.allstak.sa on the free tier — no credit card — create a project, and copy its API key. It replaces your Bugsnag API key as the credential the SDK sends events with.
2
Remove the Bugsnag SDK init
Remove Bugsnag.start and the Bugsnag error boundary from your app, or gate them behind an env flag for the duration of the parallel run. Note your current releaseStage and appVersion values — you will mirror them in AllStak.
3
Install the AllStak SDK for your stack
AllStak has 25+ SDKs with setup guides — React, Next.js, Node.js, Python, Laravel, Java, and more. For a React app, install the React SDK from npm.
terminal
```
npm install @allstak/react
```
4
Set release and environment, then upload source maps
Wrap your app with AllStakProvider and pass environment and release — the equivalents of Bugsnag's releaseStage and appVersion — so grouping and deploy tracking carry over. Upload source maps per release so minified stack traces resolve to your original code.
src/App.tsx
```
import { AllStakProvider } from '@allstak/react';

export function App() {
  return (
    <AllStakProvider
      apiKey={import.meta.env.VITE_ALLSTAK_API_KEY}
      environment={import.meta.env.MODE}
      release={import.meta.env.VITE_ALLSTAK_RELEASE}
      service="web"
    >
      <AppRoot />
    </AllStakProvider>
  );
}
```
5
Recreate your alert rules
Rebuild your Bugsnag alert integrations as AllStak notification rules. Slack, email, webhooks, PagerDuty, Opsgenie, and Telegram are supported, so on-call attention moves over without gaps.
6
Run both for a sprint, then cancel Bugsnag
Keep Bugsnag capturing in parallel for one sprint. Compare grouped errors and release health on real traffic, verify each notification route, then cancel the Bugsnag subscription.

Bugsnag concepts, mapped to AllStak

Most of the vocabulary carries straight over — one concept changes shape rather than name.

Bugsnag	AllStak
Errors	ErrorsGrouped by fingerprint with occurrence counts, the same triage model.
Stability score	Error rates & release healthAllStak does not compute a single stability metric; you track error rates per release to answer the same question.
Releases	Releases
Breadcrumbs	Breadcrumbs
Alert integrations	Notification rules

Bugsnag migration FAQ

Can I import my historical Bugsnag data?

No. There is no automated importer — historical errors and sessions stay in Bugsnag. You start collecting fresh data the moment the AllStak SDK goes live, which is exactly why we recommend running both tools in parallel during cutover.

What replaces the stability score?

AllStak tracks error rates per release rather than computing a single stability metric. You see how many errors each release produces and how that compares to the previous one — the same go/no-go signal, expressed as data you can drill into.

Do breadcrumbs work the same way?

Yes. AllStak SDKs attach breadcrumbs automatically and let you add custom ones, so every error still arrives with the trail of user actions, navigation, and requests that led to it.

Does AllStak cover web and backend like Bugsnag?

Yes — 25+ SDKs cover browser JavaScript, React, Next.js, Node.js, Python, PHP/Laravel, Java, Go, React Native, and more, each with a setup guide. Note that AllStak's session replay is for web; there is no mobile session replay.

How long does a Bugsnag migration take?

The SDK swap is usually under an hour per app, plus alert rules and source-map upload. Budget one sprint overall so AllStak and Bugsnag run side by side on real traffic before you cancel.

Explore more

Capabilities

By framework

Compare

Start your Bugsnag migration

Create a free project, swap one app, and see your errors arrive with logs, traces, uptime, and replay around them — on one bill.

Start free View pricing