Customers frequently reach out to us looking to transform their organizations by radically reconceptualizing how they utilize their ERP system. It is not uncommon that a poorly configured ERP system can become a significant impediment to business excellence, beleaguering business processes and muddying the information that would otherwise form the basis of decision-making.
As such, remediating an ERP system can be a fundamental step in transforming the related organization. That said, many customers come to us seeking to understand just how this process operates: how does a consultancy like The Estes Group work with a customer to improve their ERP system? Our answer is not especially surprising — a successful business transformation begins with a successful business process review (BPR).
A BPR is a comprehensive review of an organization and its ERP application, to understand the relationship between them and how the ERP system in question might be modified to the betterment of the organization. But the BPR itself occurs in stages, so let’s better understand the stages of a business process review.
Onsite Review
This is the first stage of a business transformation effort, and is an area-by-area assessment of the organization and the ERP-related elements that might be within the scope of the overall transformation effort. It consists of the following activities:
Clarify business priorities and goals that form the backbone of the assessment. For instance, an organization might be trying to understand whether to reconfigure or reimplement the current ERP system to better serve the needs of the organization, or even to understand whether the system in question is the right system for the organization.
Review ERP-related business processes by department — understanding each department’s perspective is critical for understanding the movement of data across the system. Identify and document issues, gaps, process problems, performance issues, data issues, or any related ERP challenges.
Review ERP data setup — data is fundamental to a successful implementation, and the core master files (items, customers, suppliers) need to be properly set up to support successful transactions.
Review ERP system configuration — the base configuration of the ERP system, which can manifest itself at the level of the company and site or even among various setup tables, can significantly alter how the system behaves. Understanding which decisions have been made is critical to understanding the behavior of the system itself.
This assessment is normally conducted onsite, as it tends to be most thorough when conducted in that manner. The consultant involved is documenting findings and making assessments at the time of the review. On the heels of the onsite review, the consultant normally performs any additional follow-up, be it in the form of data review, process follow-up questions, or remote meetings.
Document Findings
Coming out of the business process review, comprehensive documentation would occur as related to the areas covered, including the following:
Functional areas covered and the characteristics of each.
Gaps/issues identified within areas and between areas, and across the system as a whole.
Recommendations to address gaps/issues where applicable.
Determine Key Next Steps
Based on the business priorities, next steps would be identified and recommendations made. Should the organization clean up the existing environment and correct the existing data structures and business processes to better align with the organization’s intent, or should the organization reimplement a new environment to avoid the challenges of the current state? Or are there simply some tweaks to the existing system to be made, in the form of business logic or reporting?
Preliminary Review
At this point, the BPR would be reviewed with the customer. Considerations of the benefits and drawbacks of each approach would be defined and reviewed, and priorities and scope would be identified, which would be used to construct the project plan and budget. It is always helpful at this stage to clarify expectations, to make sure that goals are aligned and to avoid any downstream confusion when the final deliverables are reviewed.
Identify the Scope
Scope definition would serve to answer the following questions:
Which gaps or issues are most significant, and thus should be fundamental to subsequent planning efforts?
Which key areas would need to be addressed in order to achieve the goals identified above?
Which data files (master files and transactional files) are most in need of review?
Which business processes need to be adjusted?
How much prototyping is required to make the necessary decisions regarding data setup and process definitions?
How do we ensure that data entry is better managed in the future?
How do we ensure that preferred business processes are consistently performed in the future?
Develop the Project Plan
Based on the decisions made in the preliminary review, and the related project plan, determine the project budget that answers the question: what does the cost of the ensuing project look like? A budget may similarly have multiple versions based on the degree of customer involvement:
High customer/user involvement
Low customer/user involvement
Final Review
Once the plan and budget have been constructed, a final review will be conducted with the customer. Fine-tuning of the project plan and budget can occur to align with customer perspectives.
Proposal Development
As an output of the final review, a proposal for project execution will be constructed, using all of the information developed at this point. Assuming agreement on and signature of the proposal, the implementation project will commence.
As you can see, a systematic and staged approach to a business process review can set the stage for a systematic and staged approach to transforming your ERP system — to transform your business.
Your ERP Transformation Begins with a BPR
An ERP process review matters because it reveals how well your system is supporting — or hindering — your business. Over time, ERP setups drift away from best practices as organizations grow, users improvise, or data quality slips. This creates inefficiencies, workarounds, and reporting blind spots that quietly slow down the business. Your ERP journey doesn’t have to be complex. A review with EstesGroup’s expert consultants gives you clarity, direction, and confidence in every next step. Whether you’re reconfiguring, reimplementing, or simply fine-tuning your system, the right insights can transform challenges into opportunities.
By stepping back to evaluate processes, data structures, and configurations, an ERP process review uncovers where gaps exist and what changes will deliver the greatest impact. It turns vague frustrations into concrete improvement opportunities, aligns system performance with business goals, and provides a roadmap for smarter decision-making. In short, it ensures that your ERP isn’t just running, but running in a way that drives measurable business value.
Curious how a BPR could reshape your business? Let’s start the conversation.
Before any major ERP decision, clarity comes first. That’s why we offer a free first-step assessment with our industry experts. In this consultation, we’ll review your current ERP environment, discuss your business priorities, and identify where process gaps or system challenges may be holding you back. Think of it as a guided starting point — no obligation, just actionable insight to help you decide whether a full BPR or another path makes the most sense for your organization. And as your needs grow, EstesGroup’s expert ERP and IT teams can also support you with flexible cloud options and EstesCare Support Services to keep your systems secure, scalable, and supported long-term.
Fast, Personalized, Proven IT & ERP Expertise
No spam. No pressure. Just strategic insights and clear solutions.
Is your backup solution running on a Raspberry Pi?
We’ve all tinkered with DIY tech—but when it comes to business data, even a Raspberry Pi has its limits. Let’s explore business backup and disaster recovery plan options for Enterprise Resource Planning (ERP) workloads.
DIY Backups Can Be Fun—But Are They Enough?
Many businesses struggle to figure out how to properly back up their data. We all know that backup is important to prevent data being lost. Many things can happen such as ransomware attacks, natural disasters, data breaches, or even internal attacks on your backup system. With this in mind, it is of utmost importance to ensure your company is making proper backups. A well-built business backup and disaster recovery plan protects data, ensures uptime, and gives your team the confidence to handle the unexpected.
You never know when disaster might strike, whether it be something like flooding, an earthquake, or even something as simple as a hard drive failing in your NAS or an employee accidentally deleting a file. These things can greatly affect the productivity of your team, and cause your business to lose money, data, and time.
Common threats that make a business backup and disaster recovery plan essential:
Ransomware and cyberattacks targeting small businesses
Natural disasters like floods, tornadoes, and fires
Employee error, accidental deletions, or insider threats
Hardware failure, aging on-premise servers, or NAS crashes
Data breaches requiring fast compliance-driven restoration
Why Professional Backup and Disaster Recovery Solutions Matter
When it comes to data backup and disaster recovery, small businesses and enterprises alike need robust solutions that go beyond basic file storage. Professional backup and disaster recovery services, which are built into business application cloud hosting solutions, ensure business continuity by providing automated backups, version control, and rapid data recovery capabilities. Without a comprehensive backup strategy, companies risk losing critical business data, customer information, and years of operational history that can never be recovered.
Enterprise-Grade Data Protection Features
In light of this, as a business owner, you must ask yourself the important question, is your backup solution running on a Raspberry Pi? Is your team making trips to the bank on a weekly basis to put a LTO tape backup of your data into a safe deposit box that is intended for rare coins and jewelry? Or, even worse, is all of your data stored in a cabinet in the basement of your office, making all of your data stored on-site?
The True Chaos (and Cost) of Data Loss for Businesses
The old saying goes “don’t put all your eggs in one basket” and this absolutely applies to backups. If all your data is stored on one site, what will you do if your building gets swept away by a tornado or broken into in the night? Will you call Sherlock Holmes and try to find your Linear Tape-Open (LTO) backup tapes or hard disk drives?
LTO Tape vs. Modern Cloud Solutions
While simple solutions like a Raspberry Pi can be great for ensuring the coffee pot in the break room is never empty, your backups are the backbone of consistent service for customers. Your business deserves better than a solution designed for hobbyists, or even something like a NAS (Network Attached Backup), which only really ensures a secure backup if it is located off-site.
Thankfully, EstesGroup is here to help, with our dedicated team which will help you analyze your current business backup and disaster recovery solution, and help you improve your business continuity plan. Our on-premise and cloud-based solution suites make disaster recovery of your important data fast, secure and available 24/7/365.
Our team works hard to meet your advanced cybersecurity and compliance needs, and will help you ensure everything from your customer data to your email accounts are backed up to allow for recovery in case of a disaster.
Integrate, Automate, Report — And Prepare for Disaster
Modern backup solutions should include features like cloud storage integration, automated scheduling, encryption, and compliance reporting. Enterprise-grade backup systems provide redundancy across multiple geographic locations, ensuring your data remains accessible even during widespread outages or natural disasters.
Automated Business: Backup and Disaster Recovery Plan Scheduling and Monitoring
The best backup and disaster recovery services offer both on-premises and cloud-based options, giving businesses the flexibility to choose the right mix of speed, security, and cost-effectiveness for their specific needs.
What to look for in a business backup and disaster recovery solution:
Automated backups with customizable scheduling
Cloud-based redundancy across secure, geo-distributed locations
End-to-end encryption and ransomware protection
24/7/365 support with SLA-driven recovery
Compliance-ready reporting for audits and regulations
Scalability to grow with your business needs
Business owners often underestimate the true cost of data loss until it’s too late. Studies show that 60% of small businesses that lose their data shut down within six months of a disaster, and few IT departments leverage expert network and security assessments.
3-2-1 Backup Rule
Professional IT services and managed backup solutions can help prevent this scenario by implementing industry best practices for data protection, including the 3-2-1 backup rule: three copies of your data, stored on two different types of media, with one copy kept off-site.
Don’t let your business become another statistic – invest in professional backup services that scale with your growth and protect your most valuable digital assets.
So, what are you waiting for? Reach out to our team today at [email protected] or call us at (888) 300-2340 (if you prefer the old-fashioned telephone). Let us help you ensure your business is prepared for anything.
ERP Platforms That Require a Strong Backup and Recovery Plan
EstesGroup supports a wide range of ERP systems for manufacturers, distributors, and service-based businesses. Our team provides consulting, optimization, and secure cloud hosting for leading platforms, including:
Infor SX.e and Infor SyteLine (CloudSuite Industrial)
Whether you’re running a legacy ERP system or planning a cloud migration, EstesGroup can help you build a disaster recovery plan that aligns with your technology, operations, and compliance needs.
Wondering if your backup strategy is really enough? Whether you’re running Epicor, Prophet 21, Sage, SYSPRO, Infor, or another ERP system, your business depends on consistent uptime and data protection.
Below are some of the most common questions we hear about backup and disaster recovery (BDR) for ERP users—along with expert answers to help you protect your systems, your data, and your future.
What is a business backup and disaster recovery plan?
A business backup and disaster recovery plan is a set of strategies, tools, and processes that protect your company’s data and systems. It ensures you can recover quickly from threats like ransomware, hardware failure, or natural disasters—minimizing downtime and loss.
Is a DIY (like Raspberry Pi) backup good enough for business?
Not really. A Raspberry Pi can handle basic backups for personal use or lab environments, but it lacks the redundancy, encryption, automation, and compliance features needed for enterprise-grade disaster recovery. Think of your DIY business backup and disaster recovery plan as the Raspberry Pi of the current digital landscape.
What’s the difference between a NAS and cloud backup?
A NAS (Network Attached Storage) is a local device for storing files, while cloud backups replicate your data to secure, remote servers. Private and hybrid cloud solutions provide better scalability, offsite redundancy, and disaster resilience.
How does the 3-2-1 backup rule work?
The 3-2-1 rule means keeping three copies of your data, on two different types of storage, with one copy stored off-site. It’s a proven strategy for avoiding data loss during unexpected events.
How can EstesGroup help with disaster recovery?
EstesGroup offers fully managed backup and disaster recovery solutions tailored to small and mid-sized businesses. From secure cloud hosting to compliance reporting and rapid restore capabilities, our team helps you prepare for anything. Schedule a free IT assessment with a vCIO today.
Stay ahead of system failures, ransomware threats, and compliance risks with expert insights about enterprise-grade backup and disaster recovery plans and more.
Subscribe to our newsletter for practical tips on ERP performance, backup and disaster recovery planning, cloud hosting strategies, artificial intelligence (AI), and IT best practices—tailored for manufacturers, distributors, and business leaders who depend on reliable technology.
In the fast-paced world of business technology, staying ahead means embracing innovation and adaptability. As organizations strive to streamline operations and meet the demands of a dynamic market, the tools they use must evolve. Enter Epicor Kinetic, a transformative leap forward in enterprise resource planning (ERP) technology. With its cutting-edge user interface (UI) and enhanced capabilities, Kinetic sets a new standard for productivity, flexibility, and user experience. So what happens to the Epicor Classic UI now? What does the future look like for legacy versions?
Goodbye, Epicor Classic UI: Hello, Kinetic UI
What exactly makes the Kinetic UI so powerful in comparison to the Epicor Classic? And why is now the time to make the shift? Let’s explore the benefits, the transition timeline, and how your organization can navigate this evolution.
The Kinetic UI isn’t just an update—it’s a reimagining of how ERP systems should function in the modern age.
Built with user-centric design principles, it introduces features that empower businesses to operate with greater efficiency and agility.
Intuitive Interface: Say goodbye to clunky workflows. The Kinetic UI simplifies navigation, cutting down on the steps needed to complete everyday tasks.
Flexibility to Work Anywhere: Whether your team is in the office or remote, the browser-based design ensures ERP tools are always accessible.
Improved Performance: A faster, more responsive interface means less downtime and more productivity.
Customizable Tools: Integrated solutions like Application Studio make low-code customization a breeze, allowing businesses to tailor their ERP to meet unique needs.
These features aren’t just enhancements—they’re enablers, giving organizations the tools to compete and thrive in a fast-changing landscape.
The Sunset is Coming
Change is on the horizon, and planning ahead is critical. With the release of Epicor Kinetic 2026.1 in May 2026, the classic user interface (UI) associated with E10 and its predecessors will officially be retired. From that point forward, users will interact exclusively with the Kinetic web-based interface.
This shift marks a significant milestone for ERP software users. As the Epicor Classic UI is phased out, the Kinetic UI becomes the default, offering a future-ready solution with modernized design, enhanced performance, and more efficient workflows. Organizations adopting the Kinetic UI gain access to features that legacy systems cannot support while avoiding the risks of limited support for older versions.
The bottom line? Embracing the Kinetic UI and leaving the Epicor Classic UI in the dust isn’t just about keeping pace with technological advancements—it’s about positioning your business to succeed in a future defined by flexibility, speed, and innovation.
Web UI vs. Cloud: Understanding the Difference
A common misconception about Kinetic is the relationship between its Web UI and cloud deployment. It’s essential to understand the distinction:
Cloud Deployment focuses on the server and how the application is hosted—whether on-premise, in a private cloud, or in a public cloud managed by a vendor.
Web UI refers to how users interact with the application through a browser-based interface.
This means you can use the Kinetic web UI without moving to the cloud. Whether your ERP is on-premise or hosted in a private or public cloud, the Kinetic UI is accessible, providing flexibility for organizations to adapt at their own pace.
What Does “Kinetic” Really Mean?
“Kinetic” carries a multifaceted meaning within theEpicor ERP ecosystem. At its core, it’s a rebranding of Epicor’s Vantage/905/E10 ERP system. More specifically, it’s the name for the new web-based UI that will fully replace the Classic UI with Release 2026.1. When someone talks about “moving to Kinetic,” they might mean different things:
Upgrading to E11/Kinetic: This is essentially a shift from E10 to the next version.
Transitioning to the Web-Based UI: Moving from the Classic WinForms UI to the Angular JavaScript-based UI, which will become the exclusive interface starting in 2026.
Key Takeaway: Upgrading to E11/Kinetic doesn’t require an immediate adoption of the Kinetic web UI. Organizations can approach the transition in stages.
Upgrade vs. Uplift: A Practical Path Forward
For many Epicor customers, the transition to Kinetic isn’t an all-at-once process. Instead, they adopt a phased approach:
Upgrade First: Move to E11/Kinetic while retaining the Classic screens. This ensures your system is on a supported version without requiring immediate changes to the interface.
Uplift Later: Gradually transition to the Kinetic UI, tailoring workflows and training teams at a manageable pace.
This approach minimizes risk, allowing organizations to benefit from the latest version of Epicor without overwhelming their teams or operations.
Future-Proof Your ERP Today
The move to Kinetic is more than just an upgrade—it’s a strategic opportunity to position your business for long-term success. By embracing the Epicor Kinetic UI, you’re not just adopting a new tool—you’re unlocking a more efficient, flexible, and innovative way of working.
Are you ready to make the shift? Connect with us today to explore how moving from the Epicor Classic UI to the Kinetic UI can transform your ERP experience and help your business thrive in an ever-changing market.
Keeping your Prophet 21 ERP system up to date poses numerous challenges, especially when dealing with upgrades. The testing, retesting, troubleshooting, and remediation processes can be time-consuming and demanding. Transitioning to the P21 Web UI introduces even greater challenges, with larger changes, increased risks, and heightened frustrations for end users. Consequently, the adoption of the P21 Web UI has been progressing slowly, akin to molasses in January, as they say in Canada.
In November, EstesGroup sponsored the Southeast User Group chapter of the P21WWUG, presenting on P21 Infrastructure Best Practices and the elusive topic of Web UI Migrations. Our polls revealed that two-thirds of customers have yet to fully migrate from the P21 desktop application.
For customers still tethered to a desktop version seeking a way out, we recommend two approaches when planning a P21 Web UI migration: incremental or big bang.
An Incremental Approach
For those committed to the last branched version (2021.1) and hesitant to fully transition from the P21 desktop, an incremental approach is advisable. The customer creates an ecosystem as a live testing model, gradually shifting from the old to the new through the following steps:
Develop an adoption plan for “branched” usage, initially allocating specific hours for web UI use.
Configure a branched deployment in the live environment, allowing parallel use of desktop and web UI.
Instruct users to incrementally operate on the web UI during designated hours.
Address reported shortcomings incrementally through IT or ERP administrator intervention.
Create a remediation work plan for identified issues and initiate resolution.
Conduct remediation and testing cycles until all issues are resolved.
Increase web UI usage until reaching a predefined cutoff amount of time.
Attain user and management signoff, and officially transition all users to the web UI.
Stabilize the live cutover environment and provide ongoing support.
A Big Bang Approach
For customers seeking a more significant leap to a web-only version (2022+), the big bang approach is recommended. This involves an implementation-level cutover executed in one decisive move:
Deploy the Web UI to a middleware-only test environment.
Conduct user testing, addressing and communicating issues as they arise.
Create a remediation work plan and resolve identified issues.
Document remediations and compile into a cutover plan, expanding the testing pool.
Conduct a mock cutover (CRP), regression testing, and address any remaining issues.
Attain user and management sign-off for the “go live” decision.
Repeat the cutover to the new version in the live environment with Web UI.
Stabilize the live cutover environment and provide ongoing support.
The Weight (and Freight) of Risk in P21 Migrations
The choice between incremental and big bang approaches depends on your risk tolerance and desired rewards. If you seek to minimize risks, choose the incremental approach. For maximizing rewards, opt for the big bang. Each approach comes with its own set of risks, rewards, and characteristics. If you need assistance with your Web UI Migration, please reach out to us!
I once had an Epicor go-live brought to its knees by an administrative snafu – as cutover weekend neared, the Epicor admin refreshed the Epicor production environment with a copy of the Epicor Pilot database. Such a step is not uncommon in an Epicor cutover. But this had not been the first time that a production refresh had occurred, and there had been subsequent customization activities developed since the last Epicor database refresh. As such, there were several Epicor user-defined fields that were present in the Pilot database but new to Production. This small discrepancy created unexpected hardship to all involved.
Chaos to Resolution in Epicor
The net result for the Epicor core team that was cutting over to the new system over the weekend was a litany of cryptic Epicor error messages, abysmal system performance, and a near mutiny by the Epicor user community. After roping in a few Epicor administrative experts, we were able to discern the discrepancy, regenerate the data model, and move beyond this hurdle. But the memory of that small Epicor system administration rule-of-thumb gone wrong stuck with me, long after the project had wrapped up.
One reason for this latent memory is that it finds itself refreshed by new instances – just recently, I found an end user reaching out to me over some cryptic errors in a test environment, an Epicor environment that had just recently been refreshed from a seed database. My first question: “Did you regenerate the Epicor data model after refreshing the Epicor database?” Problem solved, albeit this time, without the pitchforks and torches.
Echoes of CRC Errors
Does this issue sound familiar? For those of us whose Epicor administrator duties go back to Epicor 905, Epicor Vantage, or some earlier Progress-based version, these issues might be likened to the familiar “CRC errors” that once plagued our Epicor custom solutions. In that case, a field had most often been added to the database, and that field caused an existing Progress-based compiled assembly to malfunction. The table structure at the database level did not match the table structure at the application level, and chaos ensued.
Sometimes, the resolution to an Epicor issue is simple. In this case, a simple Epicor admin policy would be to regenerate the data model when refreshing an Epicor environment. This ensures that you will not have any mismatch with your Epicor UD fields, and that the users can jump in without issue.
This is especially true in an environment where custom solutions are being developed, as is the case with many Epicor implementation projects, where changes are most often occurring. This can also be the case in Epicor projects that are heavy in the use of the Epicor Product Configurator module, or longtime Epicor customers who have undergone a significant amount of Epicor customization.
Post-Model Regen
Now that you’ve regenerated the data model, don’t forget the subsequent step of retrieving a copy of the Epicor database’s data model, so that the application server in question can store it locally, for use by the application itself. At a minimum, the Epicor admin should recycle the application pool for the application server instance in question – this is accomplished from the administration console. Now, I’ve had some administrators tell me that it is preferable to start and stop the ERP application pool, rather than simply recycle it. The difference between stopping and recycling an IIS application pool demands its own article, so I will stop at mentioning this controversy for the time being, without discussing its resolution.
Epicor Cutover Success
The art of efficient Epicor system administration often boils down to steering clear of preventable pitfalls. The instance described here serves as a prime illustration of a minor adjustment that can avert substantial issues. By ensuring the proper regeneration of the data model and taking the necessary steps to maintain database consistency, ERP administrators can fortify their systems against disruptions.
Do you need help with your Epicor cutover or are you looking for more admin tips?
If you find yourself seeking guidance in the realm of ERP administration, don’t hesitate to reach out. Our Epicor Kinetic consultants can assist you in navigating the intricacies of your ERP environment, ensuring smooth operations and enhanced productivity for your organization. EstesGroup brings your company functional, technical, and custom solutions for Kinetic ERP. Manufacturers will benefit from our full-suite of services and solutions, including on-premise expertise and 24/7/365 IT and ERP consultants. From third-party integrations to private cloud and hybrid cloud managed services, Estes provides everything your team needs to succeed before, during, and after go-live.