Epicor Kinetic Archives - Page 3 of 4

Introducing Epicor Automation Studio

by Rob McMillen | May 27, 2022 | Epicor, Epicor 10, Epicor Administration, Epicor Kinetic, ERP, ERP Implementation, Prophet 21

There’s always something new with Epicor Kinetic and P21. And here’s something new that is coming!

At the annual Epicor Insights conference, in Nashville, there was an announcement about “Epicor Automation Studio”. The word “Automation” caught my attention because it is a popular term right now. It can describe everything from complex machinery in the factory or warehouse to event-driven even software that runs on the desktop (like the inbox rules in Microsoft Outlook).

All these automations are designed to reduce the mindless tasks that we humans often do, so we can ideally spend more time on ~~Facebook~~ work and being more creative/human! For hundreds of years we’ve automated the physical world (washing machines). Now we see increased automation of our digital worlds to better fit our personal needs.

So, how does Epicor Automation Studio help?

Here’s what we heard.

It is a low-code/no-code toolset for P21 and Kinetic
It will support integrations between Epicor and other applications

This sounds interesting. We all know that there are significant needs for “integrating” various applications. I discuss this topic of “integration” with Epicor Kinetic and Prophet 21 clients weekly.

Often the need is to integrate EDI, e-Commerce, scanners, shipping packages, factory floor vending, or third-party applications so that they work seamlessly with Epicor and P21. So, anything that would simplify that effort would be great!

A quick “google” check helped me find an Epicor article about Epicor Automation Studio, here. It is just an introduction and discusses, in a video, how “Citizen Developers” will be able to use this new tool (I will discuss these Citizen Developers terminology in another article!).

This Epicor article adds more information about what Automation Studio does.

Helps bridge the business / IT gap
Connects Epicor / P21 to thousands of applications
Allows Epicor users to share and store automation “recipes”

What is Epicor Automation Studio?

At first glance it sounds like an Epicor version of Zapier. Zapier has been around for many years. It’s a subscription cloud service with pre-built connectors that allow a non-developer to link applications, so they share information. This involves picking two software products from a list on the screen, determining what actions you would like them to do and selecting it.

The beauty is that it focuses on “what” you want to do without requiring you to know “how” it is done.

Each Zapier process starts with a Trigger and is then followed by multiple steps to complete it. As a user you just click on options to define the one or more steps. It’s intuitive and flexible.

I’ve seen Zapier used to send texts every time you get an email in your Inbox from a key customer or open a help desk ticket if a message has certain words in it or send updates from your Contacts to Salesforce or load new information onto a website page.

However, Epicor Automation Studio will need to handle more complex situations that involve Orders, Customers, Parts, User ID’s, Jobs, Vendors, and Purchase Orders. And to do all of that, there will have to be underlying processes that likely use Application Programming Interfaces (API’s).

Today, it would take a good C# developer to integrate an application with Epicor using API logic. That skill involves knowledge about the plumbing between the two applications and also the time to fully test it.

And that’s why Epicor is moving this direction. They realize that automation is a growing trend. Particularly the trend to involve Epicor users in more of the work that has traditionally been an IT function.

We’ve already seen some of this where Epicor allows users to customize their menus, favorites and screens in Kinetic and P21. For example, in Kinetic, users can rearrange data columns when displaying information. Then they can save the format for future use. Every time they access this data, it appears in their preferred column sequence.

Another area, we see, is the use of Business Activity Queries (BAQ’s) in Epicor products. BAQ’s do require more technical knowledge than a screen customization but have opened the door to some end users creating custom dashboards and reports (SSRS). For those who are not developers they offer a simpler way (point and click) to display information and improve productivity.

What is interesting is how widespread this is. In almost every organization there is at least one non-IT person, that has decided to invest time learning how to create BAQ’s, Reports, Dashboards and even BPM’s. I’m always amazed and grateful for their skills because they are the real changemakers!

With Epicor Automation Studio, the trend continues where we see several business changes that are merging.

The first change is the widespread use of point and click interfaces (who doesn’t have a cell phone?).
The second change is the introduction of low-code/no-code tools to automate and accomplish more without having to know the details of the system.
The third change is the sharing of information (“recipes”) with others, so they don’t have to start from scratch.

While there will always be work for those who are highly technical you should expect to see more of the application customization shifting to tech-savvy end users who know what the business needs and have better tools to implement those changes. So get ready.

Who knows? Maybe someday you will start a new job and use a “studio” to design your digital workspace to your personal preferences. That would be interesting, right?

Ask the Author About Epicor

Rob McMillen is a Senior Project Manager and Principal Consultant with EstesGroup, the premiere cloud provider for manufacturers and distributors. He has worked in the manufacturing industry for over 30 years supporting multiple implementations of new ERP systems and leading projects. Because his mom was an English teacher, he grew up with a love of writing. Combined with his working experience, he has written articles for LinkedIn and User Groups, and has published numerous blog posts. He is also a co-author of a book on technology and working collaboratively. He currently lives in the DFW area.

Rob McMillen
Principal Consultant / Project Manager at EstesGroup

Ready for digital transformation? Talk to us using the chat to begin a conversation with our Epicor Enterprise Resource Planning (ERP) consultants!

Taming Your ERP System With Hybrid Cloud Infrastructure

by Brad Feakes | May 17, 2022 | Cloud, Epicor Kinetic, ERP Implementation, Hosting, Prophet 21

Cloud ERP: Confused as a mollusk and dumber than a brick wall?

In discussing integrated application ecosystems, metaphors are often helpful in understanding the challenges associated with cloud migrations and the implications associated with the options selected when migrating an integrated ERP platform. Sometimes conceptualized as a “hybrid cloud,” any time an ERP system integrates with application extensions, homegrown solutions, or third-party applications, we move beyond a simple cloud platform into a hybrid ecosystem. Read on to learn more about hybrid cloud infrastructure.

Cloud migrations can be complex, especially when a migration includes more than simply an ERP system. A stand-alone ERP system can be assessed at face value: depending on the needs of the business, the functionality of the various versions of the software, and the resources available, a company can come to a relatively clear deployment decision. But when we begin to discuss the company’s hybrid cloud architecture — the ERP application and its integrated extensions — the waters get inky-dark and murky in a hurry.

Enter the confused octopus. One helpful metaphor in understanding cloud migrations is to liken an application’s ecosystem to a confused octopus.

An ERP hybrid cloud is a body with many tentacles. And the tentacles don’t always get along with the head — or with each other, for that matter. While each tentacle is joined in some manner with the head, the lifecycle of each tentacle is independent of the parent ERP system. While an ERP system may move from an on-premise architecture to a Software-as-a-Service model (SaaS), a given extension may be designed to only interact at the database server level and may no longer be receiving updates. Simply put, the tentacles advance at their own pace — some may advance more rapidly or more slowly than the main ERP system.

As such, if we were to view a private cloud migration as the movement of an octopus though the ocean, you’d discover that some tentacles keep up with the head, while others may actually surpass the head, while others still stand in place, slowly stretching and extending their ever-thinning connection as the head moves further and further away. And in some cases, a tentacle may stretch so far as to snap off entirely. For instance, if the head of the mollusk slithers into SaaS and one of the tentacles still languishes in the deep trenches of SQL stored procedures, we might be in deep… water!

So why is it that the movement of the ERP animal’s head might estrange one of its third-party tentacles?

Perhaps another metaphor would help clarify our conundrum. Let’s talk about brick walls. The truth is, there’s a hidden brick wall hovering in the cloud, as it relates to access and control. When it comes to the level of access and control required to integrate with third-party extensions, the differences between Software-as-a-Service and private cloud architectures are monumental.

On the SaaS side of the wall, interactions are only allowed at the API-level of the parent application. Conversely, a private cloud platform can allow interactions at any level, whether the API, the business logic level, or even at the database, if necessary.

As such, understanding the necessary level of access and control to support hybrid cloud integrations is fundamental to a successful cloud migration. If you move your base ERP system onto a platform that the third-party applications cannot successfully interact with, you might discover that you’ve left several applications behind, no longer able to leverage them as part of your hybrid cloud ecosystem. I have seen cases where customers moved their ERP systems to a Software-as-a-Service deployments, only to realize that they had to essentially re-write their third-party integrations, and even some of their third-party applications entirely, to be able to interact with their new SaaS platform. They ran head first into the cloud’s hidden brick wall and spent six months of development and integration time and expense for their troubles.

While the explanations are metaphorical, the implications are as real as it gets. Are you considering a migration to the cloud? Carefully consider the implications. Take a thorough audit of the third-party extensions that comprise your hybrid ecosystem, and understand how they are constructed.

Hybrid Cloud Infrastructure Integrations

Then understand how they might also migrate in order to be able to interact with the parent ERP system in each deployment scenario, be it in a SaaS environment or as part of a private cloud. These considerations can help save a lot of grief and trauma during implementation, so make them before you bind yourself to a given path.

Mixed metaphors, even in hybrid cloud infrastructure, are rarely a good thing, so I doubt I’ll run into many mushy mollusks swimming though the ether and squishing themselves up against hidden walls in my future cloud adventures. Until then, I will have my eyes set on both the sky and the sea.

Watch a “Cloud Stories” Webinar on Hybrid Cloud Infrastructure for ERP Systems

Out-of-the-Box vs. Best-in-Breed Credit Card Processing

by Brad Feakes | May 12, 2022 | Epicor, Epicor 10, Epicor Kinetic, ERP, Prophet 21

The (ERP) Credits Are Rolling

ERP was once a battle between “comprehensive” and “best-of-breed” solutions. While the “comprehensive” solution providers claimed to offer a one-stop-shop of business functionality, providers working under a “best-of-breed” model constructed simpler overall ERP systems that were easier to integrate with third-party solutions.

The debate has morphed over time, as “best-of-breed” providers try to progressively dress themselves as comprehensive ERP solutions, while the old dinosaurs are working to make their systems more interoperable.

Credit Card Processing in Enterprise Resource Planning

For customers, this has served to muddy the waters. At a macro level, it seems safe to say that ERP has increasingly moved to a best-of-breed model, where customers are willing to manage an increasing number of third-party solutions, provided that they provide “best-in-class” functionality.

Credit card capabilities find their place among this morass of functionality, with third-party solutions competing with the integrations provided directly by vendors. Let’s look at some of the challenges that companies normally face when implementing the out-of-the-box solutions that ERP vendors provide.

Configuration Issues

We see customers frequently complain to us of the challenges in configuring their credit card modules. A customer purchases an integrated module from an ERP vendor’s feature card and expect that it should be as easy to implement as the rest of the application. Normally, we only hear from them after those hopes have been dashed.

It’s worth noting that these “modules” are modules in name only—in truth, they are loosely integrated third parties, sold as a comprehensive, out-of-the-box solution. Some ERP vendors even offer multiple versions of credit card integration, which further complicates the situation. As such, a consultant may become savvy in configuring one payment model in one licensed module, only to stumble at the next implementation.

Testing

Testing credit card solutions is always a daunting task—there is private information and money involved, after all. But a clumsy integration can exacerbate the problem. When vendors integrate with third-party solutions, but the third-party solutions themselves do not “own” the functionality and the integration, a situation where a diffusion of responsibility is likely to occur.

In such a situation, neither side of the functionally can adjudicate the outcome of testing, and provide guidance to the causes for errant outcomes. In an ERP system, the customer invariably wants a single throat to choke—a party who can assume responsibility for the functionality in question.

I’ve seen too many cases where vendor integrations leads to situations where the customer ends up paying a consultant to determine that there are bugs or unknown limitations to the integration that will hamper the use of the advertised functionality.

Functionality Limitations

It’s not uncommon that a company’s needs exceed the capabilities of the solutions that the vendor’s out-of-the-box integrations provide. Because of the specialized functionality and capabilities involved, it is often the case that the credit card capabilities provided by a vendor are a “minimal acceptable solution” variety—a solution that barely meets the base requirements, but offers very little “wiggle room” for customers whose requirements step over the vendor’s proverbial line. Such is often the problem with vendor-supplier solutions, and one of the reasons customers leverage best-of-breed solutions in their place.

“Comprehensive” Credit Card Processing or Best-in-Breed?

With all the challenges to credit card processing, we’ve found the best-of-breed solutions to be generally preferable to the comprehensive but underpowered solutions provided out-of-the box by the ERP vendor community. In that light, our work with Century Business Solutions and their EBizCharge payment platform has proven to help customers handle complex payment requirements, helping them extend their operations and shorten their order to cash cycles.

Interested in e-commerce, cloud, backup and disaster recovery, and other services and solutions that complement your ERP system? Watch our videos to learn more!

This Old IT: The Modify vs. Rebuild Software Quandary

by Joe Trent | Jan 24, 2022 | Business Consulting, Epicor, Epicor 10, Epicor Kinetic, ERP, ERP Consulting, Managed IT Services, Prophet 21, Software

When should you start from scratch?

When I was about ten years old, my family lived in an old frame house. I have a lot of fond memories from our time there, but it had some quirks.

New Construction ERP With Blueprints & Project Planning Consultants

Originally a two-bedroom house, a third bedroom had been added onto one side. Built in sort of a lean-to style, the roofline didn’t match, of course. And it was added against the dining room/kitchen side over what was formerly the back door, so you could look out the kitchen window into my parents’ bedroom. It was built on a concrete slab instead of the pier-and-beam construction of the old house, so you stepped down into it, and then there was another back door in the bedroom opening to the backyard. It was an interesting place.

I’m reminded of that house occasionally when I encounter an aging software package that we’re replacing with a modern Epicor ERP system.

When the old stuff was installed, the implementation team made modifications to tailor it to the company’s operation and crafted operating instructions to guide the team. Over the years, the company and its requirements evolved, so more changes and additions were tacked on, old features were abandoned but not removed, and documentation was bypassed in the name of expediency. “Spaghetti Mess” is the technical term for what you get after ten, twenty, or thirty years. That’s just the way of life.

Eventually, a company makes the painful choice to start afresh with current technology and fresh eyes, and we find ourselves on the brink of an adventure. As we all know, adventure is rarely experienced without peril, sacrifice, and hard work. But it also can bring us reward and satisfaction.

When IT comes to IT, our consultants will be there.

The EstesGroup will be excited to be your partners in this journey. Need help with technology solutions or cloud services? Is it time for help with your enterprise resource planning (ERP) system? We’ll be there before you know it!

Partner with EstesGroup for your entire ERP journey.

Are you researching Enterprise Resource Planning (ERP) and seeking help understanding what your ERP vendor has to offer? Software vendors aside, an initial ERP implementation or ERP upgrade should improve your user experience, streamline business functions, and create new management systems that optimize your core business processes. With real-time data, a single system (deployed in a private or hybrid cloud) can be the software program that gets your business beyond the burdens of the computer system itself – meaning that your ERP software gives you a clean solution across all business units and future software development projects. EstesGroup offers custom solutions for your unique business needs.

Watch Joe Trent On “Epicor Kinetic Business Activity Query: Fancy Tips & Nuanced Tricks”

Watch Joe Trent On “Modifying Standard Reports: SSRS Reporting”

6 Tips to Save Time & Money When Customizing Your Epicor Application

by Rob McMillen | Dec 6, 2021 | Epicor, Epicor 10, Epicor Kinetic, Prophet 21

Here at EstesGroup, we do a lot of customizations for Epicor ERP and P21 systems. These include adding new logic to processing, adding / changing reports, updating screens to add custom information and creating new dashboards to simplify business understanding. We love customizing both P21 and Epicor Kinetic / E10 because it drives customer efficiency and productivity. But the process of getting things done can be frustrating when delays set in. With that in mind, I want to give you six tips to streamline the customization process and save you time and money!

Does your Epicor application have you caught in a cycle of subtraction?

#1 – You should consider having an ad-hoc Statement of Work (SOW) setup with EstesGroup.

Doesn’t it always seem that the more urgent the request, the more roadblocks you encounter?

Often you want something quick, but you find that your current SOW has expired. Or maybe is doesn’t have enough hours for the customization. This delays your request and adds more work for you. That’s why we offer our “ad-hoc SOW” as an option.

If you have an ad-hoc SOW established with us, we can skip the step of creating a new SOW (sending emails, getting signatures, entering all of that into systems, etc.) and focus on getting the work done.

Action Step: Contact us and setup an ad-hoc SOW now. Then keep it active so that there is no delay if you have an urgent issue. We usually set them up for 12 months long and we will contact you for approval to renew. And we always get your email approval before starting any work so there are no surprises.

#2 – Have the actual user write up what is needed so that you get the most accurate version of the request.

Remember the telephone game? You whisper in another person’s ear, and they then do the same? What you find is that a request that goes through multiple people can gradually change. Then when the estimate comes back, it doesn’t match the real user’s needs and we’ve introduced more delay in the process.

Action Step: If you are the intermediary at your organization and are gathering the information, have the actual user describe what they want in their own words. Don’t try to interpret it for them or make assumptions you haven’t checked out.

#3 – Focus on describing what you want and how you would like it to work not the details of how the developer should make the code changes.

Often, we get customization requests where the customer focuses on describing the details of how the customization should technically be done rather than what the customization should accomplish.

That’s helpful but overlooks the fact that a developer may know a better way to accomplish the same thing. Plus, realize that developers are naturally prone to find solutions that will not require more work in the future. And there is also a good chance they may have done this same change for another customer.

Letting them figure out the best way ensures they will offer a solution that doesn’t affect your next upgrade and is also simpler to do.

Action Step: Focus on what you want and how you would like it to work. Describe what the screens must do, or how the report should look. Trust the developer to use their expertise to find the best way to do it.

#4 – Use a standard set of questions for each customization request. Don’t settle for a brief email that can be interpreted several different ways.

We often let requests come in with partial information and the result is a lot of unnecessary back and forth conversations to get the information needed. Your time is valuable, so use a template.

We know that when the user answers the right questions, they offer the best information. And a template is a great way to simplify the process. Of course, we know that in some cases an internal discussion is best to gather the answers. But you can still use the template, right?

Action Step: Use this downloadable form to capture the request information up-front.

#5 – Be clear about what you want and don’t rely on assumptions!

Developers will make assumptions. It’s human nature and that will affect how they estimate the time to make, test and deliver the customization. If you can define those assumptions beforehand, it will reduce delays and improve the quality of the estimate. Here’s a list of common assumptions made by the developer:

The customer doesn’t need to license any new modules to complete the solution.
This area of the application hasn’t been significantly modified before.
The customer has a good testing environment they can use.
The customer has good data to test with.
The end user will review and help test the solution.
I’m the only person currently customizing the environment.

Action Step: If these assumptions are incorrect, include the information in your request so they include them in their thinking. Don’t make them guess!

#6 – Don’t wait to verify the developer has good access to your test environment.

One of the biggest delays in delivering customizations is when the developer cannot get working access to your test environment. We’ve seen delays of several weeks around this problem and we know that is frustrating for you.

Plus, we are prone to assume that because access worked once before, that it still works. New versions of VPN software and minor configuration changes in your network will easily break the process used only several weeks ago.

Action Step: Provide connection information to the developer early in the process and have them test their access as they develop solutions. If you can validate their access yourself by emulating the developer, we highly recommend doing that so that you know your connection information works.

SUMMARY

Customizations are great but the process can be challenging. As you use these Six Tips to Save Time and Money When Customizing Your Epicor Application, you will simplify the process for your organization and save time in getting the solutions you need. Plus, you will feel less aggravation in the process!

Please feel free to share this information in your organization and let us know if you have any other suggestions as well!

Are you ready to begin a conversation about your Epicor application?

We have Epicor Kinetic / E11 / E10 & Epicor Prophet 21 experts on standby to answer your questions about every aspect of the application – from the software vendor through to the server!

Epicor Kinetic Upgrade: A Customer Perspective

by Rob McMillen | Nov 5, 2021 | Cloud, Epicor, Epicor Kinetic, ERP, ERP Implementation, Hosting

An Interview with an Epicor Kinetic User

I recently had the opportunity to sit down with an Epicor customer to discuss their recent upgrade to Epicor Kinetic 2021.1. For many Epicor customers, this is a decision they will be facing in the next 12 months since the Epicor lifecycle for 10.2.700 will create a decision point in September 2022.

During the discussion, we covered a lot of questions that are commonly asked. My hope is that what you learn here will be an input to your thought process about when and how to upgrade to Epicor Kinetic.

Conservation of Manufacturing Energy

Epicor History

This customer has been using Epicor for almost 8 years after they went live on version 10x. After the implementation they fell into the habit of not upgrading on a cadence. They regretted this because it made upgrades more challenging. Plus maintaining an Epicor upgrade cadence would have benefited them with better Epicor support, fixes, and new features. In their situation they were faced with upgrading to Epicor Kinetic from V10.2.200.

They currently have 35 users and expect to expand to 50 users in the next 12 months. They do light manufacturing and lean more to the distribution side of the spectrum. They also use Electronic Data Interchange (EDI) and a Business Intelligence (BI) solution that interfaces with Epicor.

Upgrade to Kinetic

The upgrade process took them about 90 days of effort. Knowing that future upgrades are released regularly, they invested front-end effort into documenting their business processes, end-user procedures and customizations. They also developed standard test plans that they can reuse in the future when they need to do upgrades.

They are expecting this investment to pay off as they move to 2021.2 later this Fall. During the upgrade preparation they took some time to clean up reports on the system, review their over 300 dashboards and look for ways to reduce the complexity and number of customizations that had accumulated over the years.

They then did very thorough testing in a Pilot Kinetics environment. The testing used formal test plans with each department supporting the effort. They ran all reports and validated cross-functional capabilities of the new system using a copy of their production 10.x data. As they found issues, they created solutions and documented them.

Reports

They found that many of their reports didn’t fully convert over to the new Kinetics format. So, they reached out to get external SSRS support for conversion of these reports. They were able to resolve any conversion issues with their dashboard reports using internal resources. This typically involved compiling them in the new environment and then saving them in the new Kinetic format.

Menus

They also set up two separate menu structures, one with a Kinetic look and one with the Classic look. This allowed users who were hesitant to use the new Kinetic menus some time to adjust. They estimate that they will transition all users away from the Classic view over a nine-month period.

Epicor Kinetic Upgrade Process

The actual upgrade was done on the 3rd weekend of the month to avoid month-end closing activities. They pre-arranged for necessary on-call support and proceeded with the upgrade. It finished and they applied any solutions they had discovered during testing. Then they tested the overall functionality using some pre-determined tests. No glaring issues were found so they were able to release the environment to users.

They found that the minor kinks that remained took them about 30-45 days to resolve. They were pleased that there were no issues with user permissions after the upgrade or with printing and labels.

Lessons Learned

Here are a few Epicor Kinetic upgrade suggestions from the customer perspective:

Make sure you have the necessary licenses for your Pilot environment,
Don’t forget the testing of integrations that access or share data with Epicor,
Make sure that department heads sign off on the test plans, so they understand any gaps/concerns, and
Consider using the developed Test Plans to next create new End User Documentation.

In the end, they felt like the Epicor Kinetic upgrade was more of a UI and programming change than a lot of new features for their users.

One More Thing

In retrospect they had one other recommendation that I found valuable.

Since the new Kinetics Users Interface (UI) allows all Forms to be displayed in any popular browser, there is an important decision to make. The decision is whether to allow Users to access Epicor from personal devices (tablets, home computers, phones). Most companies will have security concerns that will affect this decision. In their case, they decided to not allow users to use personal devices for accessing the Epicor application.

Overall, this customer was pleased with the upgraded UI. They found that the new UI is cleaner and more modern. Plus, the users like the ability to sort, and rearrange columns on the screen. In version 2021.1 some of the features they needed still required them to use the Classic interface, but the new release 2021.2 seems to have resolved these problems.

For now, the largest issue has been helping users make the transition to the new User Interface. Some users felt it was a steep learning curve for them and others didn’t. It confirmed for them that users rarely like change particularly in the screens they use each day. That’s why it is important to give them time to experiment and view the new interface well before any upgrade.

The I.T. department didn’t see any speed issues with processing under the new release. And they are looking forward to not having to install/upgrade clients on user laptops/desktops as they fully use the new Kinetics interface.

I hope this quick look at one client’s experience will provide some background for your decision-making and spur some questions that your organization needs to explore. If you have any other questions, feel free to reach out to us.

Ask the Author about your Kinetic ERP Project

Rob McMillen is a Senior Project Manager with EstesGroup. He has worked in the manufacturing industry for over 30 years supporting multiple implementations of new ERP systems and leading projects. Because his mom was an English teacher, he grew up with a love of writing. Combined with his working experience, he has written articles for LinkedIn and User Groups, and has published numerous blog posts. He is also a co-author of a book on technology and working collaboratively. He currently lives in the DFW area. Ask Rob a question now by clicking here to visit our “Ask An Expert” page.

Do you need help with keeping your ERP project kinetic?

For 18 years, EstesGroup has helped manufacturers and distributors implement, optimize, and support their ERP systems. With veteran consultants highly skilled in both the old Epicor ERP versions and in the latest version, our upgrade service is all-inclusive. Our Cloud ERP experts can help you understand everything from data migration to upgrade tools. We support companies on every version of Epicor, so whether you want to maintain your old system or upgrade to the latest release, you’ll find everything you need to make your application studio shine.

Are software upgrades or technology upgrades in your future? Our IT experts are here to help with your business. Are you wondering how to upgrade to Epicor Kinetic? Rather than focusing on your Epicor software, or other ERP system, focus on the work you love. Let our Epicor Kinetic experts do the busy work, the maintenance, and the specialized tasks while you focus on manufacturing. Put your data in a private cloud hosted environment for ultimate backup & disaster recovery and cybersecurity.