Resources
🤖 For AI agents: The complete documentation index is available at /docs/llms.txt. A markdown version of this page is available at /docs/cloud/operate/emigrate.md.

Emigrate

Edit on GitHub
View Markdown

To emigrate from FusionAuth Cloud to a self-hosted instance, please request a database export, as documented in User Data. After you have the data, install it in a PostgreSQL database and configure your self-hosted instance to point to that database.

Ensure your self-hosted instance uses the same FusionAuth and database versions as those used by your Cloud deployment. You can view your FusionAuth version in the administrative user interface.

To find your deployment's database version:

  • If you are running a version of FusionAuth before 1.30.2, open a support ticket.
  • If running a version >= 1.30.2, navigate to System -> About to view the version.

Once you've tested your self-hosted installation, destroy your FusionAuth Cloud deployment as outlined in Destroying a Deployment.

Migrate Data From a Deployment#

FusionAuth can be run in a variety of environments, but you may want to migrate between them because:

  • You want to let the FusionAuth team operate your auth server.
  • You started out in FusionAuth Cloud but now want to run the software on internal systems for performance, compliance or control.
  • You started out running FusionAuth locally for cost reasons, but now have launched and want to have someone else run it for you.

You can migrate the user data FusionAuth holds for you in a number of ways:

  • From a self-hosted FusionAuth instance to a FusionAuth Cloud deployment.
  • From a FusionAuth Cloud deployment to a self-hosted FusionAuth instance.
  • From a different auth provider into FusionAuth.
  • Away from FusionAuth to a different auth provider.

If you want to retrieve your user data from FusionAuth Cloud in order to migrate to a different auth provider, see Accessing User Data. To retrieve user data from a self-hosted FusionAuth instance, query the database.