Migration timeline
The migration is underway. During the week of September 1, 2026, we began gradually moving workloads to OCI. We migrate in three waves. The simplest workloads move first:
Before your account moves, we email you your exact migration schedule, so you always know what is coming and what is needed from you.
Check your wave in the Migration notice
The Migration notice in the top right corner of your Sevalla dashboard shows:- Which wave your account is in.
- The OCI data center each of your services moves to.
- The new egress IP address of each of those data centers.
- Every TCP proxy and database external connection in your account that still has a legacy hostname and port, listed as a required action with the legacy and the new endpoint side by side and the October 15, 2026 deadline.
Action required before your migration
Complete the steps that apply to your account before your migration starts. The Migration notice in your dashboard shows exactly which ones apply to you. If none of them apply, there is nothing to do. Switching your TCP proxies and database external connections has its own fixed deadline of October 15, 2026, independent of your migration date. Until then, existing TCP proxies and external connections have two endpoints that both work: the legacy hostname and port, and the new one. You can move your clients to the new endpoint at any time without downtime. Any TCP proxy you create or database external connection you enable now only gets the new endpoint and needs no action.Allowlist your new egress IP address
Once your applications run on OCI, their outbound traffic comes from a single fixed IP address per data center. If a third-party service, such as an external database, a payment provider, a private API, or a mail provider, restricts access by IP, add your new egress IP address to its allowlist before your migration. The Migration notice shows the address for each of your data centers. You can also find your new location in the server location table, then look up its address in the list of Oracle Cloud egress IP addresses. Keep the current Google Cloud ranges in your allowlists until your migration is confirmed, then remove them.Switch your TCP proxies to the new endpoints
If any of your applications expose a process through a TCP proxy that still has a legacy hostname and port, the proxy currently works on both the legacy and the new endpoint. The Migration notice lists each of these proxies as a required action, and each application’s Networking page shows the legacy endpoint and the new one. TCP proxies you create now only get the new endpoint and need no action. Update every client that connects through the proxy to the new hostname and port before October 15, 2026, when the legacy hostname and port are disabled. Because both endpoints work until then, you can switch without downtime. This deadline does not depend on your migration date.Update your database external connections
This step applies to accounts with databases. If you connect to a Sevalla database from outside Sevalla, for example from a database client, a CI job, or an application hosted elsewhere, and its external connection still has a legacy hostname and port, the connection currently works on both the legacy and the new endpoint. If you enable the external connection on a database now, it only gets the new endpoint and needs no action. The Migration notice lists every affected database as a required action with its legacy and new endpoint. If the new endpoint is not shown yet, open the database’s Networking page to enable it. Update your clients to the new endpoint before October 15, 2026, when the legacy hostname and port are disabled, regardless of your migration date. Internal connections between your Sevalla applications and databases are not affected.The pre-migration steps for Wave 2 may be extended as we finish testing the stateful migration path. We will email you about any additions ahead of time, but please check the Migration notice in your dashboard regularly.
What to expect during the migration
Your day-to-day workflow stays the same. Your applications, your deployment workflows, and your dashboard experience do not change. This is a change to the infrastructure underneath the platform, not to how you use Sevalla. The network details that do change are covered in Action required before your migration, and some regions move to a new server location. We migrate company by company. All services belonging to an account move to OCI together. Until your migration takes place, any new services you spin up continue to be provisioned on our current infrastructure, and the new OCI capabilities become available to you once your account has moved. The only exception is static site builds, which already run on OCI for all customers since Wave 0 was completed on September 1, 2026. If you run stateful services, rest assured. Databases and applications with persistent storage require individual migration scheduling, and we will handle them with the utmost care and attention. Your services are part of the final wave, and we will reach out well ahead of time with your schedule and any additional steps. In the meantime, complete the pre-migration steps that apply to your account.Frequently asked questions
Do I need to do anything right now?
Only if your account uses IP allowlists on external services, TCP proxies, or database external connections. In that case, complete the pre-migration steps that apply to your wave. Move your clients to the new TCP proxy and database external connection endpoints before October 15, 2026, even if your migration happens later, and allowlist your new egress IP address before your migration starts. The Migration notice in your dashboard shows exactly what applies to your account. If none of these apply, there is nothing to do.Will my workloads go down?
Static sites are served from the edge and are not expected to experience downtime. Other services may experience a brief period of downtime during their migration. We plan each migration to keep any impact to a minimum, and we share your migration schedule with you ahead of time. Connections that depend on details changed by the migration are the exception. Clients using the legacy hostname and port of a TCP proxy or database external connection lose their connection on October 15, 2026, when the legacy hostnames and ports are disabled. Clients already using the new endpoint are not affected. External services that only allowlist the current Google Cloud ranges lose their connection after the migration until they are updated. Complete the pre-migration steps to avoid this.How long will my services be offline?
In most cases, your services will be offline for a short period. We work to ensure that any downtime is as brief as possible. This may vary depending on the dependencies of your workloads and the specific nature of the migration. We will share what downtime to expect ahead of each migration wave. Customers running persistent workloads may experience longer downtime if their workloads require additional steps to migrate or reconfigure.How will I know if my workloads have been moved already?
We will notify you via email once your workloads have been successfully moved to the new infrastructure. Until then, the Migration notice in your dashboard shows your wave and target data center. Once your account has moved, the dashboard shows the updated data location of your workloads.Can I opt out of the infrastructure migrations?
No, it isn’t possible to opt out. OCI will become the infrastructure underneath the entire platform, so workloads cannot remain on the current infrastructure permanently.Will my server location change?
You can expect some changes to your server location as part of the infrastructure migration if your services are currently hosted in one of the following regions:
All other regions keep their current location. We include the updated data center mappings in the communication sent before each migration wave.
Our full list of locations on OCI can be found here.