Go to main content Go to main menu

Preparing For Asset Migration

Before you begin your migration, there are a few things to consider

Clean Asset Source

The last thing we want is to move a bunch of unused assets to our new system. Whether you're migrating from another DAM or local CMS assets, 

  • Delete all unused or unneeded assets.
  • Check if there are any assets that have expired due to agreements and should be removed.

Clean Source Optimizely CMS

  • Delete / Empty and archived content. These content items could contain unneeded asset references.
  • Delete any page or block content items that are not needed.
  • Identify eny incoinsistancies with asset sources. For example, are some of your assets in a DAM system and others are local CMS assets.
  • Identify if there are only certian CMS content nodes you would like to migrate assets from, otherwise the assets from the entire site will be migrated.

Investigation

  • What version of Optimizely CMS are you using?
  • What version of Image Vault's integration is installed? (if relivant)
  • Do you have the CMS integrations installed for your target DAM? (if relivant)
  • Do you have the Proxima DAM Migration Tool installed in your CMS?
  • Have you recieved a valid license key from Epinova?

CMS Code Implementation

  • How do you use images in code? Identify all properties that could contain assets that you wish to migrate. Note: This could include XHTML properties if you use images in TinyMCE.
  • Identify any shared or inherited properties that could reference assets. For example, teaser or open graph images.
  • Remember where these asset properties are referenced, these will be needed for the migration code implimentation.