Import your AMS assets

This guide is specifically for migrating from Azure Media Services (AMS). If you have content in Azure Blob Storage or Amazon S3 that was not originally from AMS, see Reference existing cloud storage content instead.

MK.IO references your existing AMS asset containers directly — no re-encoding or file movement needed. Your files stay exactly where they are in Azure Storage.

Azure Media Services has been retired. MK.IO is a drop-in replacement — your existing AMS streaming locators, content key policies, and asset containers can all be migrated.

Import your assets

Three approaches are available depending on your scale and tooling preference.

Whatever the approach, your assets remain in their Azure storage after migration — MK.IO does not copy or move them.

Using the MK.IO web interface

1. From the MK.IO dashboard view, go to Storage from the left-hand side menu.
2. Select the Add Azure storage option then fill in the required information:

Parameter	Description
Storage Account	From the drop down, select the connected Storage Account linked to your MK.IO account, where the hosted assets lives in your Azure Storage Account.
Storage container	Enter the name of the specific container where the hosted assets lives in your Azure Storage Account. In AMS, each asset is stored in a specific container. You can confirm the storage container name by navigating to the Assets view in AMS, locating your ‘output’ asset name you need to migrate and copying the name of the ‘Storage Link’ field. This will typically start with an asset-XXX naming convention and point to the container where the associated files are stored.
Sub-container (optional)	Enter the name of the sub-container if any.
Asset name	The unique identifier you want to use in MK.IO for that asset.
Description	Provide an optional description for that asset.
Upon asset deletion	Choose whether you want to preserve the container upon asset deletion.

When you click Add, the files will be uploaded and a new asset will be saved in your list. MK.IO will connect, ingest, and make the content available to be configured for streaming.

Using Azure Media Services Migration tool from MediaKind

All the steps are detailed in Bulk asset migration from AMS storage.

Using Azure Media Services Explorer tool

You can retrieve the AMS Explorer tool in this public GitHub repository: https://github.com/Azure/Azure-Media-Services-Explorer

This version of the Azure Media Services Explorer supports creating assets in MK.IO from existing AMS assets.