silverstripe-framework/docs/en/02_Developer_Guides/14_Files/05_File_Migration.md

title: File migration summary: Manage migration of legacy files to the new database structure

File migration

This section describes how to upgrade existing filesystems from earlier versions of SilverStripe.

Running migration

Since the structure of File objects has changed between 3.x and 4.x, a new task MigrateFileTask has been added to assist in migration of legacy files.

You can run this task on the command line:

$ ./vendor/bin/sake dev/tasks/MigrateFileTask

This task will perform a number of subtasks:

• move-files: Migrates existing File objects by adding required metadata to the database (incl. versioning). By default, it will not move files on the filesystem (starting with 4.4.0). Publishes to the live stage to ensure that previously visible assets remain visible to the public site. If additional security or visibility rules should be applied to File, then make sure to correctly extend canView via extensions.
• move-thumbnails: Move existing thumbnails, rather than have them generated on the fly. This task is optional, but helps to avoid growing your asset folder (no duplicate thumbnails)
• generate-cms-thumbnails: The new CMS UI needs different thumbnail sizes, which can be pregenerated. This can be a CPU and memory intensive task for large asset stores. See Migrating substantial number of files
• fix-secureassets: Migrates files secured through the silverstripe/secureassets module. Ensures that previous .htaccess folder protections don't interfere with 4.x-style asset protections.
• fix-folder-permissions: Fixes folder permissions which might have been broken by previously using the silverstripe/secureassets

One or more subtasks can be run individually through the only argument. Example: only=move-files,move-thumbnails

You can also run this task without CLI access through the queuedjobs module.

Migration of existing thumbnails

Thumbnails generated through SilverStripe's image manipulation layer can be created by authors resizing images in the rich text editor, through template or PHP code, or by SilverStripe's built-in CMS logic. They are now called "variants", and are placed in a different folder structure. In order to avoid re-generating those thumbnails, and cluttering up your asset store with orphaned files, the task will move them to the new location by default.

Discarded files during migration

Note that any File object which is not in the File.allowed_extensions config will be deleted from the database during migration. Any invalid file on the filesystem will not be deleted, but will no longer be attached to a dataobject anymore, and should be cleaned up manually.

To disable this, set the following config:

SilverStripe\Assets\Dev\Tasks\FileMigrationHelper:
  delete_invalid_files: false

Pre-existing file security solutions for 3.x (such as secure assets module) are likely incompatible with core file security. You should check the module README for potential upgrade paths.

Keeping archived assets

By default, "archived" assets (deleted from draft and live stage) retain their historical database entries with the file metadata, but the actual file contents are removed from the filesystem in order to avoid bloat. If you need to retain file contents (e.g. for auditing purposes), you can opt-in to this behaviour:

SilverStripe\Assets\Flysystem\FlysystemAssetStore:
  keep_archived_assets: true

Migrating substantial number of files

The time it takes to run the file migration will depend on the number of files and their size. The generation of thumbnails will depend on the number and dimension of your images. In general, the migration task can be restarted if it times out, and will continue where it left off.

If you are migrating a substantial number of files, you should run file migration task either as a queued job or on the command line. If the migration task fails or times out, you can start it again and it will pick up where it left off.

If your environement supports the Imagick PHP library, you may want to use that library instead of GD. Imagick is considerably faster when resizing images. You can switch back to GD after running the file migration task.

Changing the image manipulation driver to Imagick

If your project hosts big images (e.g. 4K images), this can also affect the amount of memory used to generate the thumbnails. The file migration task assumes that it will have at least 512MB of memory available.

By default the file migration task will not generate thumbnails for files greater than 9MB to avoid exhausting the available memory. To increase this limit, add the following code to your YML configuration:

SilverStripe\Core\Injector\Injector:
  SilverStripe\AssetAdmin\Helper\ImageThumbnailHelper:
    constructor:
      0: '100MB'

You can also set this to 0 to disable the limit.

System Requirements

The approach to running your file migration depends on your system and how many files you are migrating.

Use the following estimates to decide how you will run your file migration:

Number of files	Method	Expected Execution Time	Approximate Memory Usage
< 150	Web Request	30 seconds	6 MB
< 500	Queued Job	120 seconds	8 MB
< 10000	Command Line	10000 seconds	950 MB
10000+	Command Line or contact support	n/a	n/a

Your exact experience will vary based on your host server, the size of your files and other conditions. If your site is hosted on a managed environement (e.g.: Common Web Platform or SilverStripe Platform), you may not have access to the command line to manually run the migration task. Contact your hosting provider's helpdesk if that's your case.

Customise the File Migration Task (Advanced)

In some context, you may want to disable some other process when the file migration is running. For example, if you have a module that indexes files when they get modified, you'll probably want to wait until the file migration is done to reindex.

The MigrateFileTask exposes 4 extension point that can be use to detect the progress of the migration.

• preFileMigration that gets fired at the start of the task
• postFileMigration that gets fired at the end of the task
• preFileMigrationSubtask that gets fired at the start of each subtasks
• postFileMigrationSubtask that gets fired at the end of each subtasks.

preFileMigrationSubtask and postFileMigrationSubtask will provide a single string parameter matching the name of the subtask (e.g.: move-files)

Example migrate file task extension

<?php

use Psr\Log\LoggerInterface;
use SilverStripe\Core\Extension;

class MigrateFileTaskExtension extends Extension
{

    private static $dependencies = [
        'logger' => '%$' . LoggerInterface::class . '.quiet',
    ];

    /** @var LoggerInterface */
    private $logger;

    /**
     * @param LoggerInterface $logger
     */
    public function setLogger(LoggerInterface $logger)
    {
        $this->logger = $logger;
    }

    public function preFileMigration()
    {
        $this->logger->info('Run some extension code BEFORE the Migrate File Task');
    }

    public function postFileMigration()
    {
        $this->logger->info('Run some extension code AFTER the Migrate File Task');
    }

    public function preFileMigrationSubtask($subtaskName)
    {
        $this->logger->info(sprintf('Run some extension code BEFORE the %s subtask', $subtaskName));
    }

    public function postFileMigrationSubtask($subtaskName)
    {
        $this->logger->info(sprintf('Run some extension code AFTER the %s subtask', $subtaskName));
    }

}

Add the following snippet to your YML config to enable the extension.

SilverStripe\Dev\Tasks\MigrateFileTask:
  extensions:
    - MigrateFileTaskExtension