To migrate from FusionAuth Cloud to self-hosted, follow this high-level process:
Migration Steps Request a database export from FusionAuth Support Match versions: Ensure your self-hosted FusionAuth and database versions match your current Cloud deployment before migrating Load the export into your PostgreSQL instance Configure your self-hosted instance to connect to that databaseRefer to the Migrate from FusionAuth Cloud documentation for detailed steps.
LicensingYour plan includes both production and non-production license keys (available at account.fusionauth.io) :
Use the non-production key across dev and staging environments Use the production key for your production environment Keeping Your Instance Updated Most updates require no downtime Releases with database schema changes are flagged in the release notes and need a brief pause during migration Always back up your database before updating By default, FusionAuth won't apply database schema changes automatically in production. You can either: Enable silent mode for automatic migration on startup, or Run migration scripts manually before upgrading See database migrations documentation for more details Multi-node Deployment UpdatesIf running multiple FusionAuth nodes, you can update using:
Rolling updates: Update nodes one at a time (details) Blue-green deployment: Switch traffic to a fully updated set of nodes (details)Either approach limits downtime to the brief pause during database migration.
Recommended Next Steps Contact FusionAuth Support to initiate the database export Confirm your current FusionAuth and database versions Set up and test dev and staging environments before migrating production Review the Cloud-hosted vs. self-hosted comparison