Before moving from on-premises to SaaS, it is critical that you have a clear picture of your key business and system processes. We’re not talking about the IT side of how your ERP solution runs; this is about how your business uses it every day, month, quarter or year.
To facilitate, it is essential to engage a senior executive as your project sponsor. They will help link you up with other key users across the business early on in the process. There are two main areas your multi-disciplinary team must be totally across before migrating to SaaS:
Understand your interface inventory.
This refers to all the ways in which your system interacts with others. It includes Application Programmable Interfaces (APIs) as well as sources and destinations of data, supply chain communications protocols and many other possibly hidden links that users rely on. The longer your ERP solution has been installed, the less likely all these interfaces are to be fully understood. Some may only be used annually. You will need to refactor these interfaces for SaaS, so it is essential you investigate and document them.
Define your top ten end-to-end processes.
This must be done by business stakeholders rather than IT. These top ten will be the most critical – payroll, accounts receivable and the like – and they must be clearly documented so you can prepare test scripts to simulate them for testing when your data arrives on the cloud but before you go live. Yes, we do offer high-level generic test scripts for common processes, but not everyone does things the same way.