Migrate from Sentry to Vakt360
Vakt360 speaks the Sentry ingest protocol, so moving over is a DSN swap, not a re-instrumentation. Your existing SDKs, breadcrumbs and context all keep working.
Create your Vakt360 project
Sign up and create one project per app or environment, mirroring how your Sentry projects are split. Copy each project's DSN.
texthttps://<your-key>@ingest.vakt360.com/<project>Swap the DSN
Change the dsn in your existing Sentry.init call to your Vakt360 DSN. Everything else (integrations, sample rates, tags, before-send hooks) stays exactly as it is.
tsSentry.init({ dsn: "https://<your-key>@ingest.vakt360.com/<project>", // was your Sentry DSN tracesSampleRate: 1.0, });Re-point your source map upload
If your build uploads source maps, upload them to the new project's Releases area instead so minified stack traces stay readable. See the source-maps guide.
Recreate your alert rules
Alert rules don't transfer between services. Set up your email, Slack and webhook alerts in Vakt360, with the new-issue, regression and spike rules you rely on.
Deploy, verify, then cut over
Redeploy and trigger a test error to confirm events land in Vakt360. If you want a zero-risk cutover, run both DSNs in parallel for a day before removing the old one.
Start monitoring on the free plan
100,000 events a month, no card required. Point your existing SDK at Vakt360 and see your first event in minutes.
