Kentico 12 to Xperience by Kentico Migration – Site-Specific Migration & Media File Handling

Selective Site Migration

When using the Kentico migration toolkit (https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool), how can we migrate only a specific site if the Kentico 12 instance contains multiple sites (both in local and production environments)?
Is there any configuration or supported approach to limit the migration scope to a single site instead of migrating data for all sites?

Media / Image File Migration Behavior

*

While migrating media files (images) from Kentico 12 to Xperience by Kentico using the CLI command in a local environment, we observed that only metadata is migrated and the physical media files are not copied from Kentico 12 to Xperience by Kentico.
Is this expected behavior of the migration toolkit, and what is the recommended approach to migrate or sync the physical media files across environments?

Related question: Migration from Kentico 12 to Xperience by Kentico – Media Library & Content Hub Workspace Handling

Environment

  • Xperience by Kentico version: [31.0.0]

  • .NET version: [8]

Tags:
Kentico DXP Media Library Xperience Administration

Answers

In your appsettings.json file within the Migration.Tool.CLI project, look for the Migration section. You can specify the SourceSiteGuid or SourceSiteName to target a single site

Command line: When running the tool, you generally use the --sites parameter. If the configuration is set to a specific site, the tool will focus on that site and its related dependencies (pages, media libraries, etc.).

As far as the physical files it could be a path issue: The tool expects the source media files to be in the standard ~/getmedia/ or ~/Media/ directory of your Kentico 12 project. Ensure the SourceFileSystemPath in your appsettings.json points to the root of your Kentico 12 CMS folder, not just the media subfolder.

Or check if MigrateOnlyMediaFileInfo

Is set to true in your config

Or if it's in azure and stored in a blob you will need to migrate those files separately

I would strongly recommend that you migrate those media files to the content hub and not to the media library.

To response this discussion, you have to login first.