Understanding Asset Migration
During your activation of Aprimo, or even after you are “up and running,” customers frequently inquire about migrating assets from existing content stores (other DAMs, SharePoint, Box, etc.) into Aprimo. While you can always migrate your content using native uploading capabilities, in complex migrations that might involve tens of thousands of assets or advanced metadata requirements, you can request that Aprimo support and assist with your
asset migration. This document outlines the process when Aprimo supports you in bulk asset migration.
Consolidate Assets for Migration
This Asset Migration process was developed to help you minimize up-front costs and ensure migration quality. The process starts when the Aprimo Activation Team provides guidance and instruction on best practices to organize your content and metadata and consolidate that content into a central location. During this phase, you will need to prioritize content for migration as well as identify and eliminate duplicate assets across your business. Finally, after you have consolidated your content, Aprimo can provide a copy utility that moves your content into an Aprimo Azure Cloud File Store.
Test Migration
Once the content and metadata are uploaded into the provided Azure Cloud File Store, Aprimo uses our migration tools to meet your specific migration
requirement. Aprimo then performs a test migration of roughly 100 unique and varied assets and their associated metadata to expose any issues that might impact the complete migration. This test also allows you to see what their assets and metadata look like in Aprimo to ensure the appropriateness of the data mapping and the new content organizational structure introduced by the DAM.
Full & On-Going Migration
Once the test migration is completed with your sign-off, Aprimo begins the migration efforts. The process might take a few days to weeks, depending on the volume of content and metadata being migrated. It’s important to know that the Aprimo is operational and usable during migration. During the migration, errors might arise based on unique asset types or metadata structures not encountered during the testing phase. However, the chance of these errors occurring is significantly reduced when testing with Aprimo, and we immediately work with you to identify any required remediation.
Client Responsibilities
• Inventory existing content (assets, files, and systems/locations) and their available metadata
• Copy all identified assets and metadata to be migrated from the source systems into a single location (this copy process is important to ensure you have a backup of the content in the existing store(s) for current use requirements and short-term redundancy during the migration process) This includes any work that needs to be done with third-party vendors
• Perform any transformation or clean-up of the consolidated metadata file (CSV) Ensure accurate unique identifier on each asset (the unique identifier might be a file name or name + file path (which might be helpful to drive metadata structure as well)
• Ensure there is one metadata record per asset file (the metadata might be just the basic file naming or might be more robust)
• Work with Aprimo to ensure the quality of the consolidated content and metadata
• Leverage the provided Microsoft Azure Copy tool to move the content from the consolidated local storage into the provided Aprimo Azure File Store
Aprimo Expertise
• Provide guidance, instruction, and best practices on consolidating & organizing source assets and moving them into the provided Azure File Store
• Provide guidance on the format and structure of metadata file
• Optimize various migration tools based on specific and unique customer requirements
• Perform test migration of content and metadata (enhancing the migration as required until successful)
• Perform full asset migration
• Troubleshooting issues with asset and metadata migration