Skip to main content

How will my DSN change during the self-hosted migration?

Issue

I am migrating from self-hosted Sentry to SaaS, and I want to know whether my DSN changes and what I need to update in my SDKs.

Applies to

  • Customers moving from self-hosted Sentry to SaaS

  • Relocation

  • DSN

Resolution

After you relocate to SaaS, every project gets a new DSN. Your old self-hosted DSNs do not point at SaaS Sentry, so SDKs that still use them will not send events to your relocated organization.

DSN keys are not included in relocation. You must copy the new SaaS DSN into each app that reports to Sentry.

  1. Open your relocated SaaS organization.

  2. Go to Settings → Projects → [your project] → Client Keys (DSN).

  3. Copy the new DSN for that project.

  4. Update Sentry.init (or your SENTRY_DSN / equivalent environment variable) in every service that uses that project.

  5. Deploy the change.

  6. Repeat for each project.

After the new DSN is live, new events should appear in the matching SaaS project. Historical events from self-hosted are not relocated.

For the full relocation flow, see Moving to SaaS and How can I migrate my self-hosted organization to SaaS Sentry?. For what a DSN is, see the DSN explainer.

Related Articles
Did this answer your question?