Skip to main content
Background Image

Transitioning your ERP to Cloud

Korcomptenz - Total Transformation Blog - Transitioning your ERP to Cloud

Posted on July 22, 2019

Have you looked at Total Cost of Ownership (TCO) of transitioning your ERP to Cloud?

Is your company evaluating whether to transition your ERP solution to the cloud or stay on-premises? To determine whether this transition is right for your company, you’ll need to understand the economic impacts of your current ERP solution and what your ERP might look like in the cloud.

Total Cost of Ownership (TCO) is a financial estimate to determine your economic value of investment against your total direct and indirect costs over your system lifecycle. The TCO estimate considers the six cost areas every company needs to understand when visualizing their company’s transition to the cloud.

Take a look at the graphic below – on the surface, cloud and on-premises solutions look identical! Let’s dive into a comparative cost analysis between the cloud and on-premises to understand the right solution for your organization.

Transitioning your ERP to Cloud
Transitioning your ERP to Cloud - Software

Software

This is the cost of your software application including the cost of all supporting products and services, such as ISV solutions, add-on applications, customizations and other integrations to ensure your ERP system is fully inter-operable with existing systems. One big difference from a licensing standpoint is that the cloud is a SaaS that you pay-as-you-go monthly or annually and expense the cost, which is classified as Operating Expense (OpEx). In the case of on-premises applications, you pay a high upfront cost classified as a Capital Expense (CapEx) which is usually depreciated or amortized over several years.

So, just comparing your software costs on the surface is not enough. While looking at your Total Cost of Ownership estimate, you must include costs associated with implementation, operations, replacement and upgrades at the end of the system lifecycle.

Implementation, customizations and training

Implementation, customizations and training

This is the cost of your software application including the cost of all supporting products and services, such as ISV solutions, add-on applications, customizations and other integrations to ensure your ERP system is fully inter-operable with existing systems. One big difference from a licensing standpoint is that the cloud is a SaaS that you pay-as-you-go monthly or annually and expense the cost, which is classified as Operating Expense (OpEx). In the case of on-premises applications, you pay a high upfront cost classified as a Capital Expense (CapEx) which is usually depreciated or amortized over several years.

So, just comparing your software costs on the surface is not enough. While looking at your Total Cost of Ownership estimate, you must include costs associated with implementation, operations, replacement and upgrades at the end of the system lifecycle.

ERP to Cloud - Implementation, customizations and training
Transitioning your ERP to Cloud - Hardware

Hardware

In an on-premises scenario, you will incur a high upfront cost to purchase your infrastructure, such as servers, networking hardware, operating systems, databases, and data storage, and then periodic additional operating costs (such as electricity costs) to effectively run, manage, and secure your ERP solution on-premises. You will also need to buy more hardware and build redundancies in case of failures. On the other hand, the cloud allows you to flexibly manage your hardware costs without having to own, maintain, and pay for servers regardless of utilization percentage.

Transitioning your ERP to Cloud - IT personnel

IT personnel

One of the biggest single line cost items is often your IT personnel budget. Maintaining IT personnel is expensive, and in an on-premises scenario, you’ll need to factor in their labor costs plus maintenance of your real estate, servers, databases and other technology. In a cloud scenario, some of these costs will apply towards service, but that cost is typically a tiny fraction of maintaining your own in-house IT personnel, resulting in redeploying your free resources and immediately improving your bottom line.

Transitioning your ERP to Cloud - Maintenance

Maintenance

Now that you know your hardware and IT staff costs, you’ll need to include the maintenance costs of your on-premises ERP, which include the loading of fixes, patches, updates, and upgrades. Additionally, factor in the cost of IT personnel labor to test updates as they are released. In the cloud, updates, fixes, and patches are released on a continuous upgrade cycle, allowing for immediate deployment.

Transitioning your ERP to Cloud - Upgrades

Upgrades

In the cloud, upgrades run automatically in the background and require minimum oversight from your IT personnel, so there is no additional software or upgrade costs. However, in an on-premises scenario, you’ll need to account for additional IT personnel labor costs to test and deploy your upgrades.

Transitioning your ERP to Cloud - Get started

Get started

Curious to know what other costs are currently not visible to you on the surface? Contact us today to help you perform your comparative TCO analysis. Get the knowledge you need to make a fully informed financial decision about the direction of your organization.

Read more about how migrating to Azure is as easy as 1-2-3.

Read more about hosting on Azure.

Ready to contact Microsoft if you don’t have a Microsoft Partner? Talk to us here.

share This

comments

Leave a reply

Your email address will not be published. Required fields are marked *

Restricted HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type='1 A I'> <li> <dl> <dt> <dd> <h2 id='jump-*'> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.