Skip to main content

Migrate from cloud to self hosted

This guide provides detailed steps to migrate your applications and configuration from DronaHQ Cloud to a self-hosted deployment. Before you begin, make sure to review your self-hosted plan's features to ensure they meet your requirements, as self-hosted plans may have different feature sets and billing structures compared to Cloud plans.


To perform this migration, you will need:

  1. A functional DronaHQ Cloud instance.
  2. A working self-hosted instance of DronaHQ. To set up a self-hosted instance, obtain a license key from your DronaHQ account manager or use the Self-hosted Portal. Refer to the Self-Hosted deployment guides for additional instructions.
  3. Administrative permissions for both the Cloud and self-hosted instances.

Before proceeding, ensure that your self-hosted instance is upgraded to the latest version of DronaHQ.

Configure Self-Hosted premise for Applications

  1. Recreate Connectors and Environment Resources

    • Manually configure Environments (prod, dev,etc.) in Self-Hosted to use them according to your application for running efficiently.

    • Migrate connectors and environment resources in your self-hosted instance, ensuring that both instances use the same connector and resource names. Differences in names may cause issues with imported applications.

      • Export your connector configuration as JSON files. These exports include queries and configuration options.
      • Import these JSON exports into your self-hosted environment.

    Sheets are not currently supported in the self-hosted version. If migrating from the cloud version, please consider alternative solutions for your sheet-related needs. Stay tuned for updates on sheet support in self-hosted.

    Self-hosted instances can use environment variables to securely store sensitive credentials. Consider migrating credentials such as database passwords or API keys to this method for enhanced security.

  1. Export and Import Applications


    BPM Flows aren't supported in self-hosted as of yet. Please take this into consideration when planning your migration. Adjustments to your existing processes may be required. Stay tuned for updates on the availability of BPM Flows in the self-hosted environment.

    • Export your applications as JSON files. These exports include queries and configuration options.
    • Create individual exports for each application.
    • Import these JSON exports into your self-hosted instance. To import, click Create new and select From JSON.
  2. Reconfigure SSO and Other Settings

    Reconfigure single-sign-on (SSO) and other configuration settings in your self-hosted instance to match your Cloud instance. This includes:

    • Setting up SSO authentication if used in your Cloud instance.
    • Recreating custom themes, branding, and other organization-wide settings.
    • Checking and updating any other necessary configuration settings, including feature flags.
  3. Testing Applications

    After recreating connectors, importing applications, and configuring SSO and other settings, thoroughly test the most critical applications on your self-hosted instance to ensure they function correctly in the new environment.

Update Your Organization Settings

After migrating your applications, update your self-hosted deployment settings as follows:

  1. Invite Users

    • After migrating applications, add users to the new instance using single-sign-on (SSO) or email and password authentication. DronaHQ recommends using SSO for enhanced security and user management.
    • Provision users: If you use SSO with JIT user provisioning, configure SSO and JIT provisioning on the new instance for automatic user migration. For email and password authentication, manually migrate users by sending email invitations.
  2. Migrate Permission Groups

    • Migrate permission groups with role mapping or manually recreate them. Use role mapping if your identity provider supports it with an OIDC or SAML-based identity provider.
  3. Copy Settings

    • Copy custom branding, and any org-wide settings from your Cloud instance to your self-hosted instance.
    • Check the Settings page for any other necessary settings.
  4. Usage Analytics

    Usage Analytics

    Usage Analytics are not currently available in the self-hosted version. Stay tuned for updates on Usage Analytics support in self-hosted. :::