Over decades, companies have spent enormous amounts of money to build custom content applications often resulting in a huge and bloated application portfolio as well as multiple data silos and legacy ECM systems. As a result, nearly 70% of an average IT budget is spent on maintenance to keep legacy systems alive: definitely a huge problem.
This blogpost focuses on the first stage in a decommissioning or modernization project: extracting legacy content and integrating it into a standard migration or decommissioning approach.
migration-center offers a wide variety of connectors to standard ECM systems with more than 140 migration paths. Still, there are many more source systems out there, especially when custom applications were built on proprietary content storage or legacy ECM systems. So what are your options when facing the challenge of having to migrate data from these legacy systems?
No need for headaches! Often it is less complicated than you might think. migration-center can help you with the decommissioning, even if we do not have a specific connector. Usually every document management system is based on a database and that means you can use migration-center’s database connector to extract information, regardless of the user interface and whether there is an API provided or not.
All there is to it is to understand the database scheme. Sometimes vendor documentation is available, but even if not, a closer look into the database tables generally reveals the required information.