Migration guide
Migrate from Sentry
Errilo accepts events from the official Sentry JavaScript SDKs. You keep your SDK, your setup and your code: the DSN changes, and source map uploads point to Errilo.
Errilo is in development. This guide describes the setup our compatibility suite tests today; the private beta opens in summer 2027.
Before you start
Check that your SDK and its major version are in the table below. Each version is tested against Errilo by our compatibility suite, which runs the real SDK and checks that the error arrives.
| SDK | Tested versions | Guide |
|---|---|---|
@sentry/nextjs | 9.47.2, 10.78.0, 11.12.0 | Next.js |
@sentry/nuxt | 9.47.2, 10.78.0, 11.12.0 | Nuxt |
@sentry/sveltekit | 9.47.2, 10.78.0, 11.12.0 | SvelteKit |
@sentry/node | 9.47.2, 10.78.0, 11.12.0 | Node.js |
@sentry/browser | 9.47.2, 10.78.0, 11.12.0 | — |
Errilo tracks errors from JavaScript and TypeScript apps. Session replay, performance tracing, logs and native mobile apps are out of scope.
1. Create a project and copy its DSN
In Errilo, each project has its own DSN, in the same format as Sentry’s:
https://<key>@ingest.errilo.com/<project>Events sent with this DSN only ever go to that project.
2. Change the DSN
Wherever your app reads its DSN, usually an environment variable, replace the Sentry value with the Errilo one. Nothing else changes in Sentry.init().
| Framework | Server | Browser |
|---|---|---|
| Next.js | SENTRY_DSN | NEXT_PUBLIC_SENTRY_DSN, inlined at build time: rebuild |
| Nuxt | SENTRY_DSN | NUXT_PUBLIC_SENTRY_DSN, read at runtime |
| SvelteKit | SENTRY_DSN | PUBLIC_SENTRY_DSN, read at runtime |
| Node.js | SENTRY_DSN | — |
These are the names our test apps use; your project may use others. Start with one environment, such as staging, check that errors show up in Errilo, then switch production.
3. Point source map uploads to Errilo
In development: source map upload and readable stack traces will be ready for the private beta.
The Sentry build plugins (withSentryConfig for Next.js, the Nuxt module, the SvelteKit Vite plugin) and sentry-cli upload source maps as artifact bundles with debug IDs. Errilo implements the same upload API, so you keep the plugin and give it Errilo’s address and an Errilo token:
SENTRY_URL=https://app.errilo.com/
SENTRY_ORG=<your-errilo-organization>
SENTRY_PROJECT=<your-errilo-project>
SENTRY_AUTH_TOKEN=errilo_...Create the token in Errilo with the project:releases scope. Errilo then uses the source maps to show stack traces from your TypeScript source instead of the compiled code.
4. Turn off what Errilo doesn’t keep
If your setup enables tracing, session replay or logs, remove those options: Errilo doesn’t store that data, and your users’ browsers would send it for nothing.
Sentry.init({
dsn: process.env.SENTRY_DSN,
// Remove what Errilo doesn't keep:
// tracesSampleRate: 1.0,
// replaysSessionSampleRate: 0.1,
// replaysOnErrorSampleRate: 1.0,
// integrations: [Sentry.replayIntegration()],
// enableLogs: true,
});What stays in Sentry
Errilo starts with the events your app sends after the switch: past issues and their history stay in Sentry. Alert rules are set up again in Errilo.
Going back
Put the Sentry DSN and source map settings back. Since the SDK and its setup haven’t changed, there is nothing else to undo.