---
title: "Migration"
manual: "Admiral Cloud Connector"
version: "5.0"
source: "Migration/Index.rst"
modified: "2026-09-15T08:41:54+00:00"
---

# Migration

This page lists required migration steps when upgrading to a new major version
of the extension.

## Version 5.0.0

Version 5.0.0 removes the dedicated *"Update metadata of AdmiralCloud files"*
Scheduler task. Updating metadata is now done via the console command
`admiral-cloud:update-metadata`.

### Converting the Scheduler task

1.  Open the backend module *Administration > Scheduler*.
1.  Note down the action type currently configured on your existing
    *"Update metadata of AdmiralCloud files"* task (either *"Update all"* or
    *"Update last changed"*), then delete the task. It can no longer run after
    the upgrade.
1.  Add a new Scheduler task and choose task type *"admiral-cloud:update-metadata"*
    (grouped under *"admiral-cloud"* in the task type selector).
1.  In the *"Command Configuration"* field, set the `actionType`
    argument depending on the action type noted in step 2:

    | Previous action type | `actionType` argument |
    | --- | --- |
    | Update last changed | `lastChanged` (default, can also be left empty) |
    | Update all | `all` |
1.  Configure the same frequency/start date as the old task and save.

> [!TIP]
> The command can also be run directly on the command line, e.g. for testing
> or when scheduling via system cron instead of TYPO3's Scheduler:
>
> ```bash
> vendor/bin/typo3 admiral-cloud:update-metadata lastChanged
> ```