Moving to SaaS

Sentry offers a cloud-hosted, software-as-a-service (SaaS) solution in addition to a self-hosted solution, which are both functionally the same. However, many customers find that self-hosted Sentry can quickly become expensive to maintain, scale, and support, making our SaaS product the better and less costly option. To facilitate moving from self-hosted to SaaS, we provide a self-serve process known as instance "relocation".

For additional reading on considering SaaS, take a look at:

• Self Hosted or Cloud Sentry?
• XS:Code > Open Source is Free - But Expensive
• Frequently asked migration questions

Relocating to Cloud

If your organization started with self-hosted Sentry, you've invested time and effort in configuring and customizing your Sentry org. Once you decide to move to a SaaS account, it's important to know that you can relocate a lot of that investment into your new account instead of starting from scratch.

To make this relocation as seamless as possible, Sentry has a workflow that allows you to retain most of your account's settings and configurations as you move to SaaS. All you'll need is owner access to your self-hosted install, and a way to access it via the terminal.

What you'll keep

All of the configurations, team and project structure, and most metadata will be relocated. Specifically, for every organization you choose to relocate this includes:

• All of the organization settings
• The user accounts and options for all of the organization's members
• Projects and their settings
• Teams and their settings
• Alert rules
• Crons
• Dashboards
• Enabled data scrubbers
• Repositories
• Recent and saved searches

What gets left behind

Any data related to specific issues, events, stack traces, or files like replays and source maps won't be coming along. Additionally, for security reasons, you'll need to reconnect and re-authenticate all of your integrations, and your users will need to re-connect their 2FA and mint new API tokens after relocating.

One thing to note is that while we won't be able to transfer over historical event data, new incoming events will populate the projects in your relocated organization as soon as you update your DSNs. All relocated organization members will be automatically notified and re-invited via email once the relocation completes.

Version support window

Self-serve relocation is only possible from any of the last two minor self-hosted releases. That is, if the latest self-hosted release is 24.2.3, your self-hosted install must be on at least 24.1.0 to be successfully relocate.

If you'd like to relocate from an earlier release, we ask that you update your self-hosted install to the latest version first. If there is some reason that this is not possible, please contact support for more guidance.

Data security

Your data will be encrypted end-to-end during the relocation process. The only file that will pass over the network will be an encrypted tarball that we'll never store in plaintext, and will delete within 30 days of the start of your relocation.

How to Relocate

1. Sign up with a promo code

Before you begin the relocation process, sign up for a new account on Sentry. If you already have a Sentry account, login and navigate to the relocation landing page. In either case, you should see a page like this:

To receive a $100 credit, make sure to use the promo code relocate100 on this page.

2. Choose which organizations to relocate

Your self-hosted installation may have had multiple organizations, each identified by a unique slug. You'll need to collect those from your installed instance, and decide which ones you'll want to keep. You can always change these to whatever you like post-relocation on the organization settings page.

3. Follow the relocation instructions

The remaining pages in the relocation instructions will contain specific details on how to export your self-hosted instance's relocatable data. This will require terminal access to the machine running your self-hosted instance. In brief, you'll save a public key that we generate for you on your self-hosted machine, which you'll then use to execute a command that we provide to generate an encrypted tarball containing your data. You'll then upload this tarball, and we'll take it from there!

Most relocations complete in under an hour, though certain large or complex cases can take a bit longer. If you don't get an update from us within 24 hours, please contact support for further assistance.

4. Choose a plan

Once your relocation succeeds, you can take a look at our plans and select one that suits your needs based on the different features and capabilities. Note that plan pricing varies based on the type of Contract and Monthly Event Volume, so make sure you are familiar with your current/expected monthly usage (number of events per month).

If you're expecting higher volumes or you're interested in our Enterprise capabilities (priority support and SLAs, and single-tenant options, for example), please contact us regarding our Enterprise Plan.

5. Update your DSNs

Though your project data has been fully relocated, the DSNs for all of your projects will have changed, as they are now located at https://sentry.io rather than your prior self-hosted domain name. This means that you'll need to update the DSN you use in each of your SDKs for each relevant project. Once you complete this step, you'll should start to see issues and events (though hopefully not too many!) appearing as before.