Skip to main content

Umbraco Forms Moving to a Subscription Model

Explains the transition of Umbraco Forms from a one-time license file model to a subscription-based license key model, including pricing, migration details, and next steps.

Jonathan Pabst Klemensen avatar
Written by Jonathan Pabst Klemensen
Updated over 3 weeks ago

Overview:

Starting September 1, 2025, Umbraco Forms will move from using license files to using subscription keys. Specifically, version 16.3 serves as a pivotal transition point for adopting key-based licensing.

  • From Umbraco version 17 onward, only the subscription key model will be supported.

  • For Umbraco versions 13 and 16, both license file and subscription key models will work during a hybrid period starting September 1, 2025. Version 16.3 is the first to introduce key-based licensing within the hybrid model.

  • On Umbraco Cloud, no action is required. License validation happens automatically.

  • You can still test Forms locally without a subscription; a key is only required for live domains.

Benefits of the Change:

  • Unified and consistent licensing model across all Umbraco products.

  • Stronger foundation for long-term product development and faster updates.

  • Easier license management — no more handling license files.

  • Lower upfront cost and predictable annual payments.

  • Flexible for both long-term platforms and short-term campaign sites.

Pricing and Subscription Information:

Updated pricing and details for Forms subscriptions and add-ons are available at:

Each subscription covers one live domain (including all subdomains) and includes two development/test domains at no extra cost.

Migration Details:

Existing one-off license holders will receive subscription time equivalent to up to 32 months from the original purchase date.

  • Example: If your license is 10 months old, you’ll receive 22 months of subscription time (32 - 10 = 22).

  • After the migration period ends, annual billing will begin automatically.

  • Migration to the subscription model is required when upgrading to Umbraco version 17 or newer.

  • Contact Umbraco support to convert your existing license file to a subscription key to ensure compatibility with Umbraco 17+. If you want to do this now, type "talk to a person".

Next Steps (Effective September 1, 2025):

  • The Umbraco shop (shop.umbraco.com) will close for direct purchases and partner sales.

  • For new projects or migrations, request a subscription license at umbraco.com/licenses.

  • To migrate an existing license, visit umbraco.com/licenses/migrate-forms.

  • To modify an existing license (add/remove domains), use the ‘Modify an existing license’ option at umbraco.com/licenses.

FAQ Summary:

  • Will old one-off licenses stop working? No. They remain valid for Umbraco 13 and 16. However, Forms support for those versions ends when they reach end-of-life. For Umbraco 17 (or newer versions), you’ll need a subscription key.

  • Can I modify domains on old one-off licenses? Yes. Partners can manage this via umbraco.com/licenses, and direct customers via umbraco.com/products/add-ons/forms/.

  • Will Umbraco 17 only support subscriptions? Yes. Umbraco 17 or newer versions) will exclusively use the license key subscription model.- Are old license files compatible with Umbraco 17+? No, license files from earlier versions of Umbraco Forms are not directly compatible with Umbraco 17. They require conversion to the subscription key format.

  • Can I still buy a one-off license now? Yes, for ongoing projects. Request one at umbraco.com/licenses.

  • What if my license is older than 32 months? It will still work for versions below 17. When upgrading to Umbraco 17+, a new subscription license key will be required.

Version Info:

  • Hybrid model (file + key): Umbraco 13 and 16 (from September 1, 2025)

  • Subscription key only: Umbraco 17+

Notes:

  • No license changes are required for Umbraco Cloud users.

  • Localhost installations remain free for testing.

  • Subscriptions renew automatically after the migrated period ends.

Did this answer your question?