The FusionAuth Cloud team handles all required database migrations when upgrading your hosted instance to a new version. This is managed on your behalf as part of the cloud service. When you initiate an upgrade through your FusionAuth Account dashboard, the migrations run automatically during the upgrade process.

For HA Cloud (multi-node) deployments, nodes are upgraded one at a time. When the first upgraded node connects to the database, it locks the database and runs the required migrations while other nodes continue serving traffic, resulting in only seconds of downtime.

For Basic/Business Cloud (single-node) deployments, the entire instance goes offline during the upgrade, with downtime ranging from 5 to 60 minutes depending on the amount of data and schema changes required.

If you are running a self-hosted FusionAuth instance, you would need to follow the upgrade guide and apply any required out-of-band migrations manually (or configure Silent Mode for automatic migrations). However, for cloud-hosted instances, this is handled automatically by FusionAuth.

Note: You cannot downgrade a FusionAuth Cloud deployment version after upgrading, so it's recommended to test upgrades in a non-production environment first if possible.

Related Documentation

• FusionAuth Cloud - Upgrading a Deployment - Details on the Cloud upgrade process and downtime expectations
• Upgrade FusionAuth - Upgrade Options - Overview of different upgrade strategies including HA deployments
• Out-of-Band Database Upgrades - Information on manual migrations for self-hosted instances
• Silent Mode - Automatic migration handling for self-hosted deployments