This is the fourth post of my series “Insights into the development of migration-center 4”. In the last post I showed you how to configure and run a scanner in order to read all the desired files and their metadata from the source system. In today’s post I will show you how to organize your scan runs into so called migration sets. All further processing in the migration-center, i.e. transformation, validation and import will be based on a migration set. So the definition of a migration set is an important step in the whole migration workflow.
When you press the Organize icon in the main navigation bar, the client shows you the list of existing migration sets. You can use the icons in the command bar above the list to create, edit, copy or delete a migration set.
IBM Notes has been around for so many years – yet still many companies use it. Some are heavily relying on it as it supports many different processes – it can be used as an email tool for communication, as a database with or without any kind of documents and even as a feature rich application for (critical) business processes and workflows.
Notes is flexible and supports all kinds of different and custom scenarios.
However, there are several reasons to replace it with other platforms, especially when it comes down to document management. I do not want to talk about them in detail because you might know those already and therefore are reading this right now.
I want to talk about the solution to move to other platforms and I want to clear up doubts about the possibility to lose any information during the migration.
The typical migration scenario with migration-center is to read – or scan, as we call it – documents and their metadata from the source system (1), do necessary transformations on those documents in order to fit the target system (2), and finally write – or import – them into the target system (3).
Migration is an ongoing IT topic and there are many good reasons for that: Switching platforms or architecture e.g. when changing an operating system or database, virtualization and moving to the cloud are some reasons to be considered. In addition, the integration or merger of systems and applications can make content migration a relevant topic, as cost efficiency is a big deal in these cases.
Are you currently facing a migration project? Especially any Documentum migration task? Have your colleagues given you any serious advice to handle Documentum object IDs very carefully? A common example for that: Published links in intranet or e-mails referencing important documents through object IDs. Have you been asked to keep these documents’ object IDs and all their links working?
In this blog post I want to share some thoughts, experiences and solutions on migration regarding Documentum object ID concerns with you.
Every document management system’s core is a database.
I do not know if that is true for 100% of all the systems out there but it is definitely true for all DMS I have worked with. Beside, as a content migration consultant, I can tell that nearly every company has data (somewhere) inside a database.
Very often, I face the case that we have to migrate a legacy ECM system (based on a database) for which our product migration-center does not have an out-of-the-box-connector (see our target platforms). Such an OOTB connector is often the best solution for feature rich ECM systems because native connectors are typically able to support the features of an ECM system as best as possible. This applies in particular to features like relations, version, virtual documents, comments, renditions, annotations etc.
The development of migration-center 4 is moving forward. In today’s post I would like to show you two of the new basic configuration screens that we have designed in migration-center 4.
(English version below)
Dies ist der erste Beitrag einer kleinen Artikelserie, die einen Einblick in die Entwicklung der nächsten Hauptversion unseres migration-centers (MC) geben soll. Ab sofort werden wir an dieser Stelle neue Funktionen, Funktionalitäten und Verbesserungen vorstellen, auf die Sie sich freuen können. Im ersten Teil der Serie geht es hier um die neue Benutzeroberfläche.
When introducing new systems or adding new areas to a new system usually data migrations are needed to integrate the data from the old system or other areas into the new system. During such data migrations often a migration tool is used to get the data from the source into the target system. This migration tool transforms the data to be compliant with the new system and imports the data into the system.
In such a scenario generally these questions come up: How to validate the data migration? Do we need to validate the tool itself? Do we need to validate all details of all rules and functionalities that are available in the tool and could be used in theory?
As both EMC Business Partner and OpenText Technology Partner we are excited about this development. Our product migration-center enables EMC Documentum and OpenText customers to choose the best of both worlds and migrate their content to either platform without risk!
OpenText announced that it has entered into a definitive agreement to acquire Dell EMC’s Enterprise Content Division (ECD), including Documentum [http://goo.gl/tRA5LL].
What does this mean for OpenText and EMC Documentum?
Primarily, customers will have an even stronger partner to accelerate their digital transformation in order to remain competitive and to stay in business. “We are at the beginning of the Digital revolution where extreme connectivity, automation, and computing are converging,” said OpenText CEO and CTO Mark J. Barrenechea. “This acquisition further strengthens OpenText as a leader in Enterprise Information Management, enabling customers to capture their Digital future and transform into information-based business.”
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, functionally 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.