{"id":463,"date":"2020-03-08T15:34:36","date_gmt":"2020-03-08T13:34:36","guid":{"rendered":"http:\/\/dam-evangelist.blog\/?p=463"},"modified":"2022-10-14T16:48:00","modified_gmt":"2022-10-14T14:48:00","slug":"is-it-time-to-get-rid-of-your-legacy-system-5-signs-that-speak-for-this","status":"publish","type":"post","link":"https:\/\/dam-evangelist.blog\/en\/2020\/03\/08\/is-it-time-to-get-rid-of-your-legacy-system-5-signs-that-speak-for-this\/","title":{"rendered":"Is it time to get rid of your legacy system? 5 signs that speak for this!"},"content":{"rendered":"

\"Legacy
\nLegacy systems – Almost every company still has them and many companies shy away from the effort of finally replacing them.  By “legacy systems” I mean here software solutions that are getting on in years, that have been in the company for a long time and that have experienced a certain standstill.
\nBut when is it really time to start replacing these systems?<\/p>\n

Five clear signs that speak in favour of replacing such systems:<\/h4>\n
    \n
  1. \n The software manufacturer no longer exists, or has stopped developing the product\n<\/li>\n

    This reason is probably the most obvious: If the developer of a software solution no longer exists, or has stopped developing the product, then the solution is dead. A dead solution should be replaced as soon as possible, as continuing to work with such solutions only makes the transfer to a new solution, which will come at some point, more complicated and costly.<\/p>\n

  2. \nYou pay the annual software maintenance fee and receive nothing in return\n<\/li>\n

    Software maintenance fees are a good and necessary tool that gives software producers the possibility of planning security. It becomes problematic when you as a customer no longer receive anything in return for this annual maintenance fee. Software maintenance usually also includes updates for the software, but if these are no longer delivered regularly and the focus is only on keeping the existing software “running”, then caution is advised!<\/p>\n

  3. \nThird party software evolves, but not your software solution\n<\/li>\n

    Most manufacturers of software solutions offer add-on products for third party software at some point. In the case of DAM systems, for example, these are very often plug-ins for the Adobe products such as Indesign, etc. In the case of Indesign, new versions are added to the Creative Cloud at regular intervals. Software manufacturers must adapt their products to these versions accordingly. If this does not happen, or if it takes an extremely long time, this should be considered critical. The same applies, for example, to adapting web solutions to the current browser versions.<\/p>\n

  4. \nThere is no concrete roadmap for the product\n<\/li>\n

    In our agile times, it is often very difficult to create longer-term roadmaps for customers. Nevertheless, the software producer should have a vision and a direction for his product. In my opinion, as a user of software, you have the right to know what to expect from the product. A manufacturer who cannot do this either has no goal and no vision, or he does not want to share this with his users.<\/p>\n

  5. \nPromises are not kept<\/li>\n

    This is also an absolute reason for me to think about exchanging a software. In countless webinars or newsletters, you are promised great new solutions, functions, partnerships or the like. In reality, only these promises are not kept. Reliability is one of the most important qualities you should not compromise on!\n<\/ol>\n

    Software replacement is indeed not a foregone conclusion and also involves some effort. But there is a point at which one should act according to the principle “better an end with horror than horror without an end”. Dragging along more or less dead software as ballast can make the transfer to a new system, which is inevitable at some point, much longer and more complicated, so it is usually better to act than to remain passive.<\/p>\n

    Any questions?<\/p>\n

    Please contact us, we will be happy to help you:
    \n

    \n