Migrate from Traditional Digital Assets to New Digital Assets

If you created assets with a Universal Credits subscription to Oracle Content and Experience Cloud prior to August 2018, you need to migrate those assets to the new asset repository structure. The new asset repository structure includes support for publishing channels and localization.

Perform the following steps to migrate your digital assets:

If you run into any problems, see Troubleshooting.

Repository Administrator Creates a Repository for Migration

The repository administrator needs to create a repository to store the migrated assets and give your site administrator and collection owners access to the new repository. A repository administrator is a user with a Manager role within at least one repository.

Sign in to Oracle Content and Experience Cloud as a repository administrator.
Create a repository to store your migrated assets, and assign your site administrator the contributor resource role to the repository. See Creating and Sharing Asset Repositories in Creating Experiences with Oracle Content and Experience Cloud.

Collection owners will automatically be granted the manager resource role to the repository when they migrate their collections.
Let your site administrator know that he or she can configure the repository for migration.

WARNING:

After you configure a repository for migration, you won’t be able to delete it until all collections have been successfully migrated. You can leave the repository in place indefinitely and delete it later if needed.

Site Administrator Configures Repository for Migration

The site administrator needs to configure the repository for the migrated content.

Sign in to Oracle Content and Experience Cloud as the site administrator.
Open the Asset Migration tool by navigating to https://service_name-identity_domain_name.documents.dc.cloud.oracle.com/documents/assets/migration.

For example, if salesdocuments1 is your service name, mydomain is your identity name, and the data center (dc) is us2, you would access the migration tool by navigating to https://salesdocuments1-mydomain.documents.us2.cloud.oracle.com/documents/assets/migration.
On the Asset Migration page, click Setup.
In the Migration Setup dialog, select the repository you want to configure to store migrated content.
Let the collection owners know that they can start migrating their collections.

Collection Owners Migrate Their Collections

Each collection owner migrates their collections and the associated assets to the new repository so the assets are ready for use.

When you migrate digital assets, the published version is migrated. If it was never published, the latest version is migrated. Prior revisions aren’t migrated.

Before migrating a site collection, bring the site offline.

Sign in to Oracle Content and Experience Cloud.
Open the Asset Migration tool by navigating to https://service_name-identity_domain_name.documents.dc.cloud.oracle.com/documents/assets/migration.

For example, if salesdocuments1 is your service name, mydomain is your identity name, and the data center (dc) is us2, you would access the migration tool by navigating to https://salesdocuments1-mydomain.documents.us2.cloud.oracle.com/documents/assets/migration.
By default, you see all the collections you own. Filter the list of collections to those that are ready for migration. In the menu, select Ready.
Select the collection you want to migrate, and then click Migrate. You can migrate only one collection at a time.
Confirm that you want to migrate the collection.

If there's already a collection with that name, the newly migrated collection will be renamed to avoid conflict. For example, "Collection A" becomes "Collection A(1)". The collections will not be merged in the new repository.

The collection will show that migration is in progress. Oracle Content and Experience Cloud migrates the collection, its content types, its content items, and its digital assets to the new repository. If the collection is associated with a site, Oracle Content and Experience Cloud creates a new publishing channel, assigns it to the repository, associates it with the site, and targets all associated assets to the publishing channel.
When migration has completed successfully, you need to republish all the migrated assets and sites.

If there are collections that you no longer use or don’t want to migrate, you can “skip” them. Skipping a collection means that the assets won’t be migrated and won’t be able to be used going forward.

WARNING:

If you mark a collection as skipped, it will be lost forever the next time the cleanup service runs. There is no way to retrieve the collection after it’s been skipped. You can instead just leave a collection as “ready” for migration if you aren’t absolutely sure you want to get rid of the collection permanently.

To skip a collection:

Select one or more collections, and then click Skip Migration.
Confirm that you want to skip migration for the selected collections.

The collection will show that migration has been marked as skipped.

To view the status of your collections, you can look at the status messages displayed when viewing all your collections, or you can filter your collections by status:

Ready — the collections that are ready to be migrated and haven’t previously been attempted to migrate.
Skipped — the collections that have been marked skipped (that won’t be migrated and therefore won’t be able to be used going forward).
Complete — the collections that have been successfully migrated.
In Progress — the collections that are in the process of being migrated.
Error — the collections that had errors during migration.

For migrations that completed successfully or migrations that had errors, you can view detailed information about the migration. Select the collection, and then click Show Result.

The following information is displayed:

Collection Name
Collection ID (if you experience any problems and contact Oracle Support, you’ll be asked for this number)
Site Name (if the collection belongs to a site)
Migration Status
Start Time
End Time
Migrated Collection (if the collection was migrated with or without errors)
Error (if there is an error in migration)
Details (if there is an error in migration)
Failures (if the collection was migrated with errors)

Troubleshooting

If a collection migration fails (status shows “Error in Migration”):

You can try to migrate again.
You can skip the migration. Again, the collection will be permanently deleted, so choose this option only when you are positive the collection content will never be needed.
You can show the result, and, if necessary, contact Oracle Support. Copy the information in the Migration Result dialog, and save it to share with Oracle Support.