Files

T

Rajendra Kadamandmelpike 6e4b913a00 Add scripts and configuration profiles steps to downgrade guide (#50038 )

<!-- Add the related story/sub-task/bug number, like Resolves #123, or
remove if NA -->
**Related issue:** NA

## Description

Improves the [downgrade
guide](https://fleetdm.com/guides/downgrade-fleet) instead of changing
product behavior, per product design's direction.

The guide told users to move fleet-level **reports** and **policies** to
the global level before downgrading, but omitted **scripts** and
**configuration profiles**. Both are scoped per fleet and become
inaccessible once fleets are deleted during the downgrade, so users lose
them with no warning.

Adds two sections — "Move all fleet-level scripts to Unassigned" and
"Move all fleet-level configuration profiles to Unassigned" — placed
before the fleet-deletion step so users move them while the fleets still
exist. Unlike reports/policies (which move to the global level), scripts
and configuration profiles have no global bucket — they live under a
fleet or **Unassigned** — so the steps direct users to re-add them under
**Unassigned**, which remains available on Fleet Free.

> **Draft — pending wording pass.** The steps use "Unassigned" to match
the label in the Controls dropdown. Flagging for @Mel for a wording
review before this goes out.

## Testing

- [ ] N/A — documentation only.

# Checklist for submitter

- [x] Documentation change only; no code, tests, or migrations.

---------

Co-authored-by: melpike <79950145+melpike@users.noreply.github.com>

2026-07-28 21:05:26 +05:30

4.3 KiB

Raw Permalink Blame History

Downgrade from Fleet Premium

Follow these steps to downgrade your Fleet instance from Fleet Premium.

If you'd like to renew your Fleet Premium license key, please contact us.

Back up your users and update all fleet-level users to global users

Run the fleetctl get user_roles > user_roles.yml command. Save the user_roles.yml file so that you can restore user roles if you decide to upgrade later.
Head to the Settings > Users page in the Fleet UI.
For each user that has any fleet listed under the Fleets column, select Actions > Edit, then select Global user, and then Save. Delete any users that shouldn't have global access.

Move all fleet-level reports to the global level

Head to the Reports page in the Fleet UI and select a fleet from the fleets dropdown at the top of the page.
For each report that belongs to a fleet, select the report and select Edit report and copy the Name, Description, Query. Then expand the "advanced options" and take note of the values in the Platforms, Minimum osquery version, and Logging dropdowns.
On the Reports page select All fleets in the top dropdown, select Add report, paste each item in the appropriate field, select the correct values from the advanced options dropdowns, and select Save.
Optional: Delete each report that belongs to a fleet because they will no longer be accessible in the Fleet UI following the downgrade process.

Move all fleet-level policies to the global level

Head to the Policies page in the Fleet UI.
For each policy that belongs to a fleet, copy the Name, Description, Resolve, and Query. Then, select All fleets in the top dropdown, select Add a policy, select Create your own policy, paste each item in the appropriate field, and select Save.
Delete each policy that belongs to a fleet because they will no longer run on any hosts following the downgrade process.

Move all fleet-level scripts to "Unassigned"

Scripts are configured per fleet and won't be accessible after your fleets are deleted. Move them to "Unassigned" so they remain available following the downgrade.

Head to the Controls > Scripts page in the Fleet UI and select a fleet from the dropdown at the top of the page.
For each script that belongs to a fleet, select the download icon to save a copy.
Select Unassigned in the top dropdown, then select Add script and upload each script you saved.
Optional: Delete each script that belongs to a fleet because they will no longer be accessible in the Fleet UI following the downgrade process.

Move all fleet-level configuration profiles and assets to "Unassigned"

Configuration profiles and assets are configured per fleet and won't be applied after your fleets are deleted. Move them to "Unassigned" so they continue to apply to your hosts following the downgrade.

Head to the Controls > OS settings > Configuration profiles page in the Fleet UI. Select either Profiles or Assets in the menu, and select a fleet from the dropdown at the top of the page.
For each configuration profile or assset that belongs to a fleet, select the download icon to save a copy.
Select Unassigned in the top dropdown, then upload each configuration profile and/or asset you saved.
Optional: Delete each configuration profile and asset that belongs to a fleet because they will no longer be applied following the downgrade process.

Back up your fleets

Run the fleetctl get fleets > fleets.yml command. Save the fleets.yml file so you can restore your fleets if you upgrade again later.
Head to the Settings > Fleets page in the Fleet UI.
Delete all fleets. This will move all hosts to the global level.

Remove your Fleet Premium license key

Remove your license key from your Fleet configuration.
Restart your Fleet server.

4.3 KiB Raw Permalink Blame History