Other Considerations before Embarking on a CloudSuite Implementation

Last week, we discussed the importance of identifying the scope and timeline roadmap for your organization by conducting a pre-planning exercise. The same careful attention should be applied to any customizations, as well as any big-ticket reporting or analytics needs that are mission critical. Hopefully, these will be out-of-the-box from CloudSuite, but you want to understand the implications if you're going to need to work through them during the project.

Something else that is absolutely necessary when preparing for a CloudSuite project is thinking through any data conversion needs your organization might have. All master type data needs to be present in CloudSuite on day one of go-live, but you have a few different options when it comes to transactional data. It's not a blanket statement of, "I want to bring over three years," or, "I want to bring over no data." For a given module, there are different pros and cons to bringing forward historical or open transactions. It's really worth the time to explore what those options are and consider what makes sense so that you have a good idea of that before really getting started on CloudSuite implementation or migration.

Once you figure out this information, you will be able to do a value analysis based on what the potential savings are. Examine the time that you're spending producing reports or how many resources are dedicated to system administration, and then get some pricing from Infor on what SaaS licensing are service estimates will look like. Not only will you save in hardware costs, but you will also save on the ensuing support costs related to the hardware, as well as the costs related to maintaining these point solutions.

It's not just the administration or the support costs, but also the upgrades, the integrations, and the professional services around them. Some of these things might require paying extended maintenance costs, which can be for hardware or software systems if you don't get off on time. Regardless, there's a lot of hard dollars out there that you should be able to save along the way by getting on a more consolidated platform.

That's the easy part of the calculation - I would argue that the greater impact is probably a little bit harder to quantify upfront. However, if you look at some of the leaders within our industries or organizations who made an earlier jump to modern systems, it's easy to see that some of those companies are already starting to see the benefits of migrating to the cloud.

If you want to know more about how to scope out what this effort might look like at your organization, we actually did an excellent presentation recently that was really well received. You can find it here: CloudSuite #105 – v11 Pre-Planning.

Learn More about RPI Consultants

Back to Blog

Related Articles

All About Data: What to Consider Ahead of a CloudSuite Migration

Every organization is different when it comes to their data and what needs to be brought over...

Ways to Support Your Team During a CloudSuite Implementation

Keith & I have spent a lot of time digging into the technical side of a CloudSuite implementation...

Understanding the Technical Backend of CloudSuite Implementations

Let's talk about the technical backend and types of CloudSuite implementations.