Migration Headaches? Blame it on metadata.
I would say many, if not most organizations are well aware that metadata associated with content is typically of poor quality. Even if acknowledged, you are rather in a pickle when it comes to migration. You don’t have the luxury of time to manually apply meaningful metadata to every piece of content. Common issues include a lack of metadata, subjective metadata, and plain old wrong metadata. Even taking the step to assess data quality before the migration, it is only a small sampling and leads to a false sense of security as most metadata issues only become apparent during import or validation.
Based on our own research, most organizations still rely on the business user to manually apply metadata. And so the problem is a never ending circle. Obviously we recommend our own tools, but there are several third party tools available that can assist in addressing the metadata problem. I know they are well worth the time to research and deploy a migration solution that addresses the heart of the problem – which is metadata.
I don’t know the state of your metadata. How do you handle during a migration?