Here comes a new system! But who’s going to clear up the old one? And at a good price too.

This question has to be answered in the context of a project. It includes defining technical requirements based on processes in order to be able to come up with and implement solutions from it. Find out what’s important.

Implementing a new IT system poses the challenge to companies of what to do with the old system being replaced. There’s often not time or motivation to spare to take care of the previous system, although this is crucial to fulfil legal requirements and also to save costs.

In defining the technical requirements, a process-based approach has proved itself. The following questions should be answered here:

  • Which processes still have to be run using the old system?
  • What are the relevant cases that apply?
  • Who should retain access to the old system (read/write)?
  • Which interfaces (internal and external) must still be maintained, and which don’t have to be?
  • Are there any changes to requirements to data security and data protection?

From these technical requirements, various scenarios can be extrapolated as solutions. As a rule, a cost-benefit analysis is a good basis for decisions.

Contracts with service providers (e.g. support suppliers, IT infrastructure providers or even providers of the entire application) often represent an enormous potential for savings. This above all depends on the licence model and the servicing packet agreed (service level agreement).

To deal with old systems successfully, it is recommended setting up a project with an appropriate structure. To ensure that the project is successful experienced project management is crucial.