Skip to main content
MediaBeacon University

Data Migration and Data Mapping Notes

MB Build / Version: X.X vXXXXX

Author: JTW

Issue Description


Resolution Description


General notes about migration and mapping

  1. Data Migration of assets / files
    1. Verify the file types being migrated to MB
    2. Determine method of data transfer
      1. Physical hard disk in mail
      2. Some sort of FTP or SFTP transfer
  2. Metadata Migration
    1. Details of migrating the metadata
      1. How is the metadata attached to the files in the customer’s existing environment?
      2. How will this metadata be transferred to MB?
        1. Attached to the file in xmp?
        2. A sidecar file that needs to be linked up to the data file?
    2. Type of migration
      1. Standard migration using MB out of the box Import tool
        1. Is it possible to meet the customer’s migration needs using the Import functionality?  This is the quickest and easiest option
        2. This requires specifically formatted metadata so that it can be imported into MB.
        3. The field mapping needs to be fully understood and fields need to exist in MB prior to import
        4. If importing metadata values after assets are already in MB, need to identify some sort of Key field to match up the new metadata being imported
      2. Custom migration script
        1. To be used when the migration/mapping is not possible with the out of box Import functionality
        2. Need to write a detailed functional specification to communicate the custom scripting requirements for the Engineering team to implement.  Then file a BT2 to request the custom script development and consider the timeline of the development and engineering schedule.
    3. Mapping
      1. Field Mapping
        1. This is typically included in a migration of metadata.
        2. The field mapping identifies the fields that exist in the customer’s existing environment and maps the field to the field to be present in the new MediaBeacon environment
        3. Field mapping is separate from Value mapping which defines transformations to be applied to the metadata values
      2. Value Mapping
        1. This is used when the customer’s existing metadata values need to be changed or transformed during the migration process
        2. Value mapping can include special rules on how to transform the data when migrated to MB
        3. Value mapping can also reference dictionaries of terms in the existing environment and the new MB environment
          1. Ex: When value “A” is found in the existing metadata, change the value to “B”
  • Was this article helpful?