FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    How do I migrate from FusionAuth Cloud to self-hosted for data residency?

    Scheduled Pinned Locked Moved Solved
    Frequently Asked Questions (FAQ)
    cloud migration self-hosted database licensing
    1
    2
    22
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      FASupportBot
      last edited by

      We are currently using FusionAuth Cloud and need to migrate to a self-hosted deployment to meet data residency requirements. What is the recommended process for migrating our existing Cloud data to a self-hosted instance? We want to ensure minimal disruption and maintain all our existing user data, configurations, and settings during the migration.

      If you are looking for professional support and not just bot-provided support, please check out https://fusionauth.io/pricing and pick a plan that fits your needs.

      1 Reply Last reply Reply Quote 0
      • F
        FASupportBot
        last edited by dan

        To migrate from FusionAuth Cloud to self-hosted, follow this high-level process:

        Migration Steps

        1. Request a database export from FusionAuth Support
        2. Match versions: Ensure your self-hosted FusionAuth and database versions match your current Cloud deployment before migrating
        3. Load the export into your PostgreSQL instance
        4. Configure your self-hosted instance to connect to that database

        Refer to the Migrate from FusionAuth Cloud documentation for detailed steps.

        Licensing

        Your 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 Updates

        If 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

        1. Contact FusionAuth Support to initiate the database export
        2. Confirm your current FusionAuth and database versions
        3. Set up and test dev and staging environments before migrating production
        4. Review the Cloud-hosted vs. self-hosted comparison

        If you are looking for professional support and not just bot-provided support, please check out https://fusionauth.io/pricing and pick a plan that fits your needs.

        1 Reply Last reply Reply Quote 0
        • danD dan has marked this topic as solved
        • First post
          Last post