Episode 1: Traditional DMS and ECM systems vs. Microsoft 365
The market for traditional Enterprise Content Management (ECM) or document management systems (DMS) exists for more than 30 years and is dominated by few internationally positioned enterprises like OpenText, Hyland or Box. In addition, there are many medium-sized providers – primarily from the DACH region – such as ELO, DocuWare, d.velop, EASY or SER. Due to this long history, the many tens of thousands of customers of these providers have functionally very mature, but also extraordinarily complex systems in use – and this mostly on their own IT infrastructures with application servers, databases and storage systems.
Driven by the Corona crisis, the increasing pressure of digitalisation and the continuing shortage of IT specialists, it is becoming more and more difficult for these customers to keep such DMS or ECM infrastructures running. Not to speak of setting up and establishing new process solutions on top of them.
The solution is quickly found: We go to the cloud! But what does that mean?
Old wine in new skins
The offer often looks like this: The DMS or ECM system is hosted and operated in a data center, alternatively in Microsoft Azure or Amazon Web Services (AWS), by a service provider or directly by the provider. Since almost all traditional DMS or ECM providers have to manage the balancing act between a large number of historically existing on-premises installations and the “new” cloud/SaaS hosting, the cloud architectures – if they exist at all – are usually not comparable with those of pure cloud/SaaS providers.
At best, the service provider takes care of the provision and configuration of the booked applications, necessary updates and regular adjustments to the infrastructure as a full-service provider. This also includes the provision of storage space for GoBD-compliant, audit-proof management and backup of customer documents and their metadata. As I said, at best. The problem here is, among other things, that the service provider in this constellation becomes a comprehensive data processor for the customer.
Large effort and limited update capability
But what does that mean exactly? In concrete terms, it means that the service provider needs a lot of staff and effort to be able to look after the large number of customer systems. Updates – especially in cases where system components also have to be installed on the customer’s workstations – can often not be fully automated due to the customer-specific (i.e. individual) adaptations. This in turn means that new functions and releases are not available in a timely manner.
In addition, the customer is no longer “master” of his own data and documents, because he can only access them via the respective DMS or ECM system of the service provider. If the contract with the service provider is now terminated, the data and documents must be returned by the service provider – often, unfortunately, at a cost to the customer. This type of DMS or ECM system deployment is very expensive and inefficient. But what is the alternative to this?