A Successful Migration Is Not Adding a Revision Number to an Existing Document
There are quite few leading-edge migration software vendors who provide the management and features needed to successfully migrate to SharePoint, or one platform to another. The features may differ, but all experts agree with ‘garbage in – garbage out’ and as painstaking as cleaning up your content may be, it is a necessity, not an option. A successful migration cannot be viewed as simply adding a revision number to migrated documents.
Some solutions provide rudimentary metadata review and edit capabilities but still lack the ability to automate the process through the identification of semantic metadata (i.e. the concepts) found within the content. The bottom line is migration is not a simple process and determining the correct status of each and every piece of content is highly prone to error when performed solely by human efforts. Not only must the migration process address high value content, content that can be deleted before migration, but also the bulk of documents that fall somewhere in the middle. Those that fall within the middle are the most difficult to determine as there is no automated method to determine value.
The business imperatives driving these issues are:
- Rapid change has occurred in the legal landscape where organizations are being held accountable for protection of information either through laws, regulations, as well as civil and criminal penalties
- High costs associated with migration and the inability to solve ‘garbage in – garbage out’ syndrome
- Lack of the ability to provide security profiling based on the content of documents, not necessarily migrating the existing security designation
- Lack of time and resources
conceptTaxonomyWorkflow along with conceptClassifier or conceptClassifier for SharePoint is used to assist in the migration process and works with other migration applications. The easy-to-use taxonomy management tools enable your organization to quickly build, import, or customize existing taxonomies before the migration process. This achieves the consistent migration of content across the organization based on the conceptual meaning of the document’s content. Using conceptTaxonomyWorkflow automatic routing based on the text content of each document can be performed.
For more information about this topic, please read our ‘conceptTaxonomyWorkflow’ solution brief for migration.