Template Migration

When a template's variable definitions change and a new version is created, assets linked to older versions are not updated automatically. Instead, Fleetera provides a migration workflow that lets you review proposed changes and upgrade assets on your schedule.

When migration is available

An upgrade notification appears on the asset detail page when:

• The asset was created from a template
• The template has a newer version than the one the asset is linked to

The notification shows the current version, the latest version, and how many versions behind the asset is.

Migration proposal

Before migrating, the platform generates a migration proposal that previews exactly what will change. The proposal shows:

Variables to add

New variable definitions that exist in the target version but not in the asset's current version. These will be created as new variable instances on the asset.

Variables to remove

Variable definitions that existed in the old version but were removed in the target version. The corresponding variable instances will be soft-deleted — the data is preserved in the database but the variables no longer appear on the asset.

Variables to modify

Variable definitions that changed between versions — for example, a change in data type, unit code, or name. The proposal shows the old and new values for each changed field.

Executing a migration

After reviewing the proposal, confirm to execute the migration. The platform:

1. Updates the asset's template version link to the target version
2. Creates new variable instances for added definitions
3. Soft-deletes variable instances for removed definitions
4. Updates variable instances for modified definitions

Migration scope

Migration operates on individual assets. If you have multiple assets linked to the same template (e.g., 20 pumps all created from the same template), each asset can be migrated independently. You can migrate all of them at once by selecting multiple assets, or migrate them gradually.

Migration reporting

After migration completes, a summary shows:

• Migrated count — number of assets successfully upgraded
• Failed count — number of assets that failed to upgrade (if any)
• Error details — specific errors for any failures

Partial migrations are reported — if some assets succeed and others fail, the successful ones remain on the new version and the failed ones stay on the old version.