Migrations
Migrations to and from IBM FileNet, Content Manager or CMOD
Novadoc is a specialist in moving content to and 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 content management system is being introduced and the data in the old system must land in the new system in a structured manner.
An old FileNet, CMOD, Content 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) and the content must be transferred.
The on-premises environment moves to the cloud
Although migration is often a last resort 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 developed its own tools 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 how to give such a project the greatest chance of success.
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.
With customised application management
Your business is constantly on the move, because stagnation is regression. Application management must be designed with this in mind. The lifespan of the IBM Platform is very long; an average version lasts 5 to 7 years. This means that the configuration must be managed flexibly, so that the application is always adapted to the requirements and wishes of the organisation, processes can be continuously improved and tasks are increasingly automated.