Dependencies in a SaaS migration

Why switch to Basware Alusta? What are the implications of a migration? What are the dependencies in a migration process and what is the right approach? Questions Martijn Hoogendijk and Christian Willemsen answered during a webinar organized by ICreative.

It is a fact that support for Basware IP/PM will end in the foreseeable future. But that is not the main reason why users should switch from this version. 'The new Basware technology allows users to do their business operations remotely. There is also no more hassle with licensing,' Hoogendijk says. In fact, users of the SaaS solution pay per transaction rather than per user. Moreover, users are less dependent on their own IT department.

Switching to SaaS leads to an improved purchase-to-pay process, explains Christian Willemsen. The percentage of invoices processed automatically increases and the control of expenses increases. In addition, different stakeholders have different information needs. For example, the financial administration wants to know which entries can be automated, while a process controller may be more interested in whether there is enough cash in house to make the upcoming payment run. The new version meets everyone's needs.

To start a migration project, two questions are important: Who or what is the trigger and who is in charge? Is the project driven from Purchasing, IT or Finance? 'There is change management involved. Behavior and thinking will have to change throughout the organization,' Willemsen knows.

Finally, Hoogendijk explains what a possible trajectory might look like in time, reasoned in reverse from a final go-live date. Roughly speaking, three scenarios are conceivable: total relief, joint efforts and rapid delivery. As the user organization assumes more responsibilities, the total lead time can decrease.

Want to know more?