Top tips to prepare your institution for SaaS transition
Tidy the house
An IT team pre-transition task is to ensure your ERP solution is currently running as smoothly and burden-free as it can – by getting rid of any unwanted baggage before setting out on your journey. Have a look at your custom reports… any named ‘test_1’ or ‘Jim_test_3’ can probably be deleted. The rule is, if you don’t know what it is, find out, then delete it!
Also resolve any software errors while still running on premise – such as unwanted background jobs or database query fail warnings. If you can’t eliminate them in house, ask us to help you solve them. That way, you won’t be moving existing errors across to your new SaaS solution.
Some of our higher education customers, especially the longstanding ones, have developed custom reports to meet very specific needs. However, over the years we have created a number of new reports and workflows they may not be aware of – and we believe we’ve covered pretty much all bases now.
The SaaS version of our solution ships with all standard reports and workflows, which it is best practice to use. Yes, you can migrate customised reports across if you wish – but we recommend you first look to see whether you could instead use one of our standards. The advantage is that they run on a global code line, so patches and upgrades are automatic.
Make your authentication cloud friendly
Legacy authentication systems are typically on-premise focused, and there are now newer best practice ways. The industry standard is Security Assertion Markup Language (SAML) – a framework for authenticating and authorising users that can support multiple factors beyond username and password for additional layers of access security – such as tokens and fingerprints.
You must ensure your existing authentication is SAML-compliant well in advance because, if it isn’t, there will be a lead time involved in designing and deploying a new one.
Network planning and performance tuning
Another thing to be planned well prior to transition is your network configuration. Your ERP SaaS solution will be located at a highly secure public SaaS provider, which may require you to upgrade the internet links to your various locations. This can take some time to organise from carriers.
With regards to bandwidth requirements, we can advise based on the number of users at each of your campuses. Network latency must also be within acceptable limits, if users are to retain the same (or better) response rates than they do with your on-premise solution.
Ready to learn more?
To take advantage of the opportunities SaaS ERP can offer your institution, complete the form to speak to a SaaS transition expert.