Your Cloud ERP implementation questions answered
Do people still rely on ‘if it ain’t broke, don’t fix it’ attitudes to cloud implementations because they don’t really understand the benefits? Or is it something else?
This was essentially the question fuelling our recent webinar, ‘Key strategies for overcoming common challenges,’ which you can watch on-demand right now. In the webinar, we revealed research, undertaken in partnership with Computing Research, highlighting how cloud-based ERPs' benefits far outweighed the perceived risks and challenges.
However, even armed with this, some people still had questions about the implications of this. Here are the 3 big questions that came out of the webinar and what they mean for you.
We want to move our ERP to the cloud, but Unit4's solution takes away our access to the database and removing AG16s - Why do this? It removes all the benefits of migrating?
Having a direct database is, in principle, a no-go in cloud delivery. The biggest reason for this is a change in responsibility. In SaaS, your vendor (Unit4 in this example) is responsible for performance and security. Direct database access, for instance, using AG16, can jeopardize that severely due to unvalidated database input.
Next to that, Unit4 adheres to SOC 1 and SOC 2 compliance standardization. Being able to change data in a non-traceable way is not acceptable from a compliance perspective. Customers should ask themselves about the level of risk they face when employees can change data like bank account numbers and amounts without any validation or authorization.
In a Unit4 SaaS, AG16s and/or ACTs can be allowed, but only after having these reviewed by the vendor. We acknowledge this challenge, and to make migration easier, we have introduced a standardized, easy transition path to Unit4 SaaS.
What hidden costs - like new software and service purchases - does a cloud migration demand?
Unit4 has a transparent approach to cloud migrations. We work closely with our customers to identify precisely what internal teams will spend on the required changes (processes, integrations, customizations). This means upfront, all costs regarding your migration are clearly set out in a standardized statement of work, and the service itself is clearly described in a service description.
If updates occur automatically in the cloud, what guarantee is there that an unrequested update won't clash with other elements in your infrastructure (which is why updates on-premise are typically scheduled)?
First of all, it's our responsibility to ensure your infrastructure and software always work seamlessly together and ensure our users never experience issues like this. Secondly, with hundreds of customers in the cloud, our updates must roll out smoothly without impacting them. And if a deficiency is ever found, we make resolving it our highest priority, so that customers are affected as little as possible.
To do that, we always announce upcoming releases before they are deployed so customers can prepare to test, train, and/or adapt to new features.