<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with licensing]]></title><description><![CDATA[A list of topics that have been tagged with licensing]]></description><link>https://fusionauth.io/community/forum/tags/licensing</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 09:45:33 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/licensing.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[How do I migrate from FusionAuth Cloud to self-hosted for data residency?]]></title><description><![CDATA[<p dir="auto">To migrate from FusionAuth Cloud to self-hosted, follow this high-level process:</p>
Migration Steps

<strong>Request a database export</strong> from FusionAuth Support
<strong>Match versions</strong>: Ensure your self-hosted FusionAuth and database versions match your current Cloud deployment before migrating
<strong>Load the export</strong> into your PostgreSQL instance
<strong>Configure your self-hosted instance</strong> to connect to that database

<p dir="auto">Refer to the <a href="https://fusionauth.io/docs/migrate/hosting/from-cloud" rel="nofollow ugc">Migrate from FusionAuth Cloud</a> documentation for detailed steps.</p>
Licensing
<p dir="auto">Your plan includes both production and non-production license keys (available at <a href="http://account.fusionauth.io" rel="nofollow ugc">account.fusionauth.io</a>) :</p>

Use the <strong>non-production key</strong> across dev and staging environments
Use the <strong>production key</strong> for your production environment

Keeping Your Instance Updated

Most updates require <strong>no downtime</strong>
Releases with database schema changes are flagged in the <a href="https://fusionauth.io/docs/release-notes" rel="nofollow ugc">release notes</a> and need a brief pause during migration
<strong>Always back up your database</strong> before updating
By default, FusionAuth won't apply database schema changes automatically in production. You can either:

Enable <strong>silent mode</strong> for automatic migration on startup, or
Run migration scripts manually before upgrading


See <a href="https://fusionauth.io/docs/update/database-migrations" rel="nofollow ugc">database migrations documentation</a> for more details

Multi-node Deployment Updates
<p dir="auto">If running multiple FusionAuth nodes, you can update using:</p>

<strong>Rolling updates</strong>: Update nodes one at a time (<a href="https://fusionauth.io/docs/update/prod-instance#rolling-update" rel="nofollow ugc">details</a>)
<strong>Blue-green deployment</strong>: Switch traffic to a fully updated set of nodes (<a href="https://fusionauth.io/docs/update/prod-instance#blue-green-deployment" rel="nofollow ugc">details</a>)

<p dir="auto">Either approach limits downtime to the brief pause during database migration.</p>
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 <a href="https://fusionauth.io/docs/cloud/cloud-vs-self-hosted" rel="nofollow ugc">Cloud-hosted vs. self-hosted</a> comparison

]]></description><link>https://fusionauth.io/community/forum/topic/3419/how-do-i-migrate-from-fusionauth-cloud-to-self-hosted-for-data-residency</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3419/how-do-i-migrate-from-fusionauth-cloud-to-self-hosted-for-data-residency</guid><dc:creator><![CDATA[FASupportBot]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>