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).
(English version below)
Mit Sicherheit haben auch Sie bereits davon gehört, dass immer mehr Unternehmen Software einsetzen, um die interne Kommunikation, Zusammenarbeit in Projekten oder auch das Onboarding zu verbessern. Ausgangssituation ist oft ein älteres, unmodernes Intranet, welches von den folgenden Problemen betroffen sein könnte:
- Unübersichtliche Struktur (z. B. zu viele Gruppen, unsortierte Beiträge)
- Wenig Aktivität
- Schlechte Bedienbarkeit
- Unzufriedenstellende Funktionalität
Heutige Unternehmen wenden sich deshalb oftmals von diesen statischen Systemen ab und suchen nach Lösungen, welche besonders den Mitarbeiter in den Mittelpunkt stellen – und nicht die riesigen Datensammlungen, so wie man sie häufig in älteren Intranets findet.
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.