Migrations to and from IBM FileNet, Content Manager, BAW or CMOD
Novadoc is a specialist in moving content to (and sometimes from) IBM products. The content can be analyzed, classified and provided with metadata.
For example, in the following situations:
There is a large amount of documents on different source systems that need to be moved to an IBM based DMS, including mandatory metadata.
A new ECM system is being introduced and the data in the old system must be transferred to the new system in a structured manner.
An old FileNet, CMOD, Content Manager or Case Manager version is upgraded to a new version, where migration is necessary. We take care of the upgrade and the data migration.
Another database is chosen. For example, Oracle is replaced by DB2 (included free with IBM BAW).
The on-premises environment moves to the cloud
Although migration is often a closing item in many projects, with most of the attention and time going to the implementation of a new system or version, migration projects are often challenging.
For example, when long-running processes (workflows) need to migrate, or when 'the store remains open during the migration'. What happens during a long-running migration process (lots of data = long lead time) with the new influx and mutations?
Novadoc has a migration platform to efficiently and with high quality perform a migration from and especially to an IBM content product (FileNet P8, CMOD, Content Manager).
In addition, we have over 25 years of experience with migrations, we know the challenges and know how to give such a project the greatest chance of success. For this we have a standard approach that is customized for each project.
Our advice: start well in advance, calculate the actual required migration time based on trial migrations, consider carefully in advance how the end result should be measured and tested and which KPIs should be achieved.
Please note that many exceptions can make the migration process quite complicated.
Improve data quality with AI
A challenge with migration is the old saying: 'garbage in is garbage out'. A document with little or wrong meta-data will still have low quality during migration.
With AI we can now do something about that. With NLP and LLMs the documents can be analyzed in terms of content to improve the quality of the metadata. Or to provide empty, but mandatory fields with meaningful values.
A migration can even be like this: 'garbage in, quality out'!
We are regularly asked to migrate documents to a FileNet P8 / IBM Content Services / BAW environment. We have developed a number of tools for this purpose to realize the migration in an effective and efficient manner. For you, this means a fast migration process, with the least possible risk of disruptions to the ongoing process and loss of data.
We can perform large migrations where information can also be automatically derived from the content (with Watsonx.AI) and passed on as meta-data to the document in the new environment. With this modern enrichment of the migration data
Our migration tools are suitable for many types of document migrations. These tools cover 4 phases:
Inventory and analysis
Read from the source system
Processing / enriching (possibly with AI)
Writing in the target system
Read and write adapters are available for Tridion, File Systems, various databases, FileNet Content Services, FileNet Image Services, and FileNet P8.
We develop customer-specific adapters easily and quickly within our migration framework. These are also available for OpenText Documentum, among others.
And if necessary, we also migrate data from FileNet / BAW to other systems.
