Umbraco Cloud
CMSHeartcoreDXPMarketplace
  • What is Umbraco Cloud?
  • Frequently asked questions
  • Security
    • Web Application Firewall
  • Sustainability Best Practices
  • Getting Started
    • Explore Umbraco Cloud
    • The Cloud Portal
      • Organizations
      • Sustainability Dashboard
    • Project Overview
    • Environments
    • Flexible Environments
    • Baselines
      • Baseline Merge Conflicts
      • Break Reference between Baseline and Child Project
      • Handling configuration files
      • Pushing Upgrades to a Child Project
    • Plans
    • Migrate to Umbraco Cloud
    • Repositories in a Cloud Project
    • Best Practice for Working in Teams
    • Migrate between regions
  • Set up
    • Ready to Set Up Your Project?
    • Working with a Local Clone
      • Legacy Umbraco Visual Studio Setup
    • Manage Environments
    • Project Settings
      • Managing Transport Security
      • CDN Caching and Optimizations
      • Dedicated Resources
      • Upgrade your Plan
      • Public Access
      • Managing Hostnames
        • New Certificate Authority for custom hostnames
        • Rewrite rules
        • Custom Certificates
      • Management API Security
      • Umbraco CI/CD Flow
        • Cloud API For CI/CD Flow
        • Configuring a CI/CD pipeline
          • Azure DevOps
          • GitHub Actions
        • Troubleshooting
        • Known Limitations and Considerations
      • External Services
      • Usage
        • Bandwidth
      • Availability and Performance
      • Hostname Monitoring
      • Team Members
        • Technical Contact
      • Secrets Management
      • Project History
    • Private NuGet Feed on Umbraco Cloud
    • Going Live
    • Media
    • External Login Providers
    • Azure Blob Storage
      • Connect to Azure Storage Explorer to upload files manually
      • Connect and Upload Files Programmatically to Azure Blob Storage
    • Users
    • Multi-Factor Authentication
    • Application Insights
    • Config Transforms
    • SMTP Settings
    • Payments
    • Power Tools (Kudu)
      • View the Files on your Cloud Environments
      • Generate UDA files
      • Manually run Extractions on your Cloud Environments
  • Deployments
    • Deployment
    • Deploying between environments
    • Transferring Content, Media, Members, and Forms
    • Deploying Deletions
    • Deployment Webhook
    • Deploying Changes
    • Umbraco Forms on Cloud
    • Deploy Dashboard
    • Hotfixes
      • Apply hotfix by manually moving files
      • Apply hotfix by using Git
    • Restoring Content
      • Partial Restores
  • Databases
    • Keep Your Data Secure and Accessible
    • Working with databases
    • Database backups
    • Database
      • Connecting to the Database on Mac
    • Working with a Cloud database locally
  • Product Upgrades
    • Stay Up to Date with Umbraco Cloud
    • Product Upgrades
    • Major Upgrades
    • Minor Upgrades
    • Version Specific Upgrades
      • Migrate from Umbraco 8 to the latest version
      • Migrate from Umbraco 7 to Umbraco 8 on Umbraco Cloud
    • Upgrade your projects manually
      • Manual upgrade of Umbraco CMS
      • Manual upgrade of Umbraco Deploy
    • Dependencies on Umbraco Cloud
  • Troubleshooting
    • Resolve Issues Quickly and Efficiently
    • Troubleshooting FAQ
    • Log files
    • The Umbraco Backoffice
    • The Frontend
    • The Umbraco Cloud Portal
    • Site Performance checklist
    • Troubleshooting deployments
      • Extraction error: Config transforms failing
      • Extraction error: Data Type collisions
      • Dependency Exception
      • Merge Conflicts on Flexible Environments
      • Troubleshooting deployments failing with no error message
      • Troubleshooting duplicate dictionary items
      • Troubleshooting language mismatches
      • Path too long Exception
      • Schema Mismatches
      • How to resolve collision errors
      • Extraction error: "Type not found! "
    • Cloud Errors
  • Release Notes
    • Overview 2025
      • June 2025
      • May 2025
      • April 2025
      • March 2025
      • February 2025
      • January 2025
    • Overview 2024
      • December 2024
      • November 2024
      • October 2024
      • September 2024
      • August 2024
      • July 2024
      • May 2024
      • April 2024
      • March 2024
      • February 2024
      • January 2024
    • Overview 2023
      • December 2023
      • October 2023
      • September 2023
      • August 2023
      • June 2023
      • May 2023
      • April 2023
      • March 2023
      • February 2023
      • January 2023
    • Overview 2022
      • December 2022
      • November 2022
      • September 2022
      • August 2022
      • June 2022
      • May 2022
      • April 2022
      • March 2022
      • February 2022
      • January 2022
Powered by GitBook
On this page
  • How Forms are handled on Umbraco Cloud
  • Recommended workflow
  • Upgrades
  • Version-specific changes
  • Version 9+
  • Common issues with Umbraco Forms on Cloud
  • The Forms tree is missing

Was this helpful?

Edit on GitHub
Export as PDF
  1. Deployments

Umbraco Forms on Cloud

PreviousDeploying ChangesNextDeploy Dashboard

Last updated 2 months ago

Was this helpful?

In this article, you can learn about how Umbraco Forms is handled on Umbraco Cloud and read about the workflow and best practices.

Umbraco Forms is a package that is included with your Umbraco Cloud project. It gives you a nice integrated UI, where you can create Forms for your website. The package is built specifically for Umbraco and is maintained by Umbraco HQ.

Read more about the product in the documentation.

How Forms are handled on Umbraco Cloud

Forms are handled like content and media. This means that you can transfer your Forms between environments, using the same workflow you use for content and media.

Definitions for each specific Form, its fields, workflows, and prevalues are all stored in the Umbraco database.

Entries submitted are not transferred to the next environment, as they are environment-specific. If you need to move entries from one environment to another, you need to run an export/import script on the databases.

Recommended workflow

You can work with Forms in an environment of your choice. When you need to test or use your Forms in another environment you can:

  • Transfer the Forms to the next environment using Queue for transfer or

  • Restore the Forms on an environment lower in the workflow.

For more information on how to handle content transfer/restores on Umbraco Cloud, check out the following articles:

Upgrades

Whenever a new minor version of Umbraco Forms is ready, eg. 10.x or 11.x, you will get the option to apply the upgrade to your project. When your project is eligible to receive the new version, you will see an "Upgrade available!" label on your left-most environment.

Version-specific changes

In this section, you can find information about version-specific changes that might affect the way Umbraco Forms works on your project.

Version 9+

In Umbraco Forms version 9.0.0+, it is only possible to store Form data in the database.

Version 8.5.0

Prior to Umbraco 8.5.0, all forms data was saved as .json files in the App_Data/UmbracoForms directory in the file system.

As of Umbraco 8.5.0, you have the option to persist all Forms data directly in the database. This behavior defaults to all new sites created on Umbraco Cloud since September 2020. If your Cloud project was created before, you will need to upgrade the Umbraco Forms version. Additionally, apply a setting to perform the migration of the Umbraco Forms data.

To switch to persisting all definitions for Umbraco Forms data in the Umbraco database, follow these steps:

  1. Make sure all environments are upgraded to at least Umbraco Forms version 8.5.2 and Deploy 3.5.0.

  2. Make sure your Forms are in sync between all your Cloud environments.

  3. Clone down your left-most environment.

  4. Restore content and Forms to the local clone.

  5. Open the configuration file App_Plugins\UmbracoForms\UmbracoForms.config from your local clone.

  6. Add the following key in the <settings> section and make sure the value is set to True:

    <setting key="StoreUmbracoFormsInDb" value="True" />
  7. Save the file.

  8. Spin up your local clone and verify that everything works as expected.

Now it is time to deploy the setting to your Cloud environments.

Follow the steps outlined below for each environment for the migration to run on each of them.

  1. Access KUDU.

  2. Navigate to site/wwwroot/App_Data.

  3. Delete the UmbracoForms directory.

  4. Push the updated setting to the environment.

  5. To run the migration, restart the environment from the Cloud portal.

  6. From the Umbraco Backoffice, Queue and transfer the Forms to the environment.

  7. Repeat steps 1-5 for each of your Cloud environments.

Did you create your project before June 2018?

Then your Umbraco Forms data might still be handled as metadata.

You will need to follow the steps below to persist Umbraco Forms data in the Umbraco database.

  1. Find and open Config\UmbracoDeploy.settings.config on your local machine.

  2. Update the transferFormsAsContent value to true:

    <?xml version="1.0" encoding="utf-8"?>
    <settings xmlns="urn:umbracodeploy-settings">
       <forms transferFormsAsContent="true" />
    </settings>
  3. Remove all existing data\revision\forms-form__*.uda files, so it's not possible to accidentally revert to this state (removing UDA files won't remove the actual form on deploy).

  4. Push the change back to the Cloud environment.

    • If you have more than one Cloud environment, make sure to deploy the change through to all of them.

  5. You are now able to queue your Forms for transfer between the Cloud environments, like content and media.

If you do not have the transferFormsAsContent setting in the UmbracoDeploy.settings.config file, you do not need to make any further changes.

Common issues with Umbraco Forms on Cloud

The Forms tree is missing

Sometimes you might experience that you lose the tree in the Forms section in the backoffice after a deployment. To get the tree back, all you need to do is restart the environment from the Umbraco Cloud Portal.

Umbraco Forms is part of the . Whenever a new patch is ready for release, we will automatically apply it to your Cloud project. There will be a notification in the Umbraco Cloud Portal at least 5 days before we roll out new versions.

To avoid having the auto-upgrades overwrite any of your custom settings, we strongly encourage that you use when you need custom configuration. Additionally, use when you need to customize your forms.

If you want to upgrade to Umbraco 9 and are using Forms, you should first migrate the Forms to the database using Forms 8. See the article.

Umbraco Forms
Transfer content, media and forms
Restoring content
auto-upgrades on Umbraco Cloud
config transforms
Themes
Umbraco Forms in the Database