Why migration-center 4.0?
The new major version 4 of our proven migration product is currently being developed and will be released in 2017. Version 4 comes with a new and modern user interface, great new user experience and a lot of new functionality that will make your migration team even more productive. The motivation to develop a new major version of migration-center have been the architectural and technical constraints of version 3 that inhibited major improvements in the areas of usability, customization, performance, functionallity and custom jobs support (pre & post processing).
New technologies used
The modernized migration-center job server’s architecture will allow multi-threading in all adapters, easier adapter deployment, and the integration of any kind of custom adapters or jobs – so you can expect faster migrations and support for new use cases. The job server and the client will use state-of-the-art REST web services for communication instead of proprietary protocols, making it even easier to implement custom adapters/jobs.
Another major change in migration-center 4 is the client application. We have developed the new migration-center client from scratch based on.NET technology. This leads to a state-of-the-art user interface with a much better user experience. And it allows us to keep the client up-to-date with new developments in user interface design.
Innovations and improvements
Over the last years our customers supplied us with a lot of valuable feedback and we have tried to integrate as many of those feature requests as possible in migration-center 4 in order to further streamline the overall migration process. The most important innovations and improvements to mention are multiple-value mapping lists, new transformation functions, custom processes, scheduler enhancements, and advanced folder creation.
Multiple-value mapping lists
The flexible transformation engine is a main building block of migration-center. The new multiple-value mapping lists feature will allow storing several values under one key, reducing the effort to enrich existing metadata. A single mapping list can contain, for example, four values for each key:
The call to the function mapValue(“fme”, 2) would then result in „ECM“.
New transformation functions
Often it is required to enrich the documents’ metadata with data stored in external database tables. With the getDataFromSQLTable function we will address exactly this use case. For example, a call to getDataFromSQLTable(“SAPTable”, 123, “Name”) on the database table below would result in “Maik”.
migration-center has a built-in support for six common migration steps (see figure below). But with the new custom job feature, it will gain flexibility on an unprecedented scale. migration-center users will be able to enrich metadata and even content during the migration process by using custom jobs in any stage of the migration process. For example, one can use a custom job for watermarking, PDF transformation, data retrieval from third-party system, deletion of objects in source system after successful import in target system and many others. Build individual customer processes (jobs) without affecting the core of the product by using the out-of-the-box customer process framework.
Also the new scheduler will be much more flexible than before and allow to start any job at any time and also to setup individual process chains for batch processing.
Advanced folder creation
It is a common request in migration projects to migrate source documents into a new folder structure in the target system. The new advanced folder creation feature will give you all the flexibility you need to create a new folder structure with folder metadata in the target system that is based on any metadata from the source system.
The first release of migration-center 4 will start with the three mostly used adapters but we will add all the other adapters and hopefully many more in the following releases. Please see the figure below for our current release planning.