Your ECM can be described as ‘legacy’ if it interferes with your business objectives, and stands in the way of that clean and agile content environment you need.
There are many situations where this is the case: the ECM might be out of support, be built around outdated technology, or no longer fit in your content architecture. This does not always mean your ECM is old. Content specialists migrate data both from and to ECM platforms such as Documentum; in one scenario the ECM is legacy, in another it is the new system that frees up content to support a lean and agile business strategy. Every organization is different. We do see that Digital Transformation is speeding up legacy ECM migrations.
In the era of Big Data, content is a resource almost as invaluable to an organization as its human capital. For this reason alone, leaving content in an outdated and inefficient ECM is no longer an option.
Although ‘legacy’ does not necessarily mean old, in most migration projects you will be dealing with legacy technology, legacy databases and legacy support (that is to say, all the support you have is in document form, if you can find the documents). This is one of the challenges you face, when doing a legacy migration.
The performance of your old system could be a concern, because it runs a large amount of content on an old environment.
Restructuring your legacy system (which might be based on folder thinking) to map the new environment requires building complex mappings.
The provider of your old system could be unwilling (or unable) to shed light on how your legacy system has been set up
Often times, systems are managed by people who have left the company. When nobody knows how the old system is configured, you could be fighting a losing battle.
These old implementations tend to be very well thought through and mapping this to new systems can be tricky.
The most legacy content migrations Xillio has performed are to Office 365, which could be due to the improved record management functionalities of SharePoint Online. Recently, we start to see more and more legacy migrations from systems, such as LiveLink, Documentum, OpenText and FileNet.
The top 6 requested legacy content migrations is as follows: