Tips for a Successful Epicor Implementation

01 Oct Tips for a Successful Epicor Implementation

You’ve gone through the hard work of selecting software, a platform, and an implementation provider.

You’re all done…right? Not really. Now the real work begins…here are some tips for a successful ERP


1. Management support. Identify an executive sponsor who meets regularly with the team. What are the team challenges? How can you help them? Executives don’t need to know every application detail, but they need to be aware of the issues that are causing delays to the project, and they need to help prioritize competing tasks.

2. Strong team leadership with knowledge of your business. This isn’t an IT project…this is the way you’ll manage your business. Appoint a strong champion and surround him or her with good people. This person will be responsible for collection and testing all end user requirements and learning the new system inside an out. While it’s difficult to free up your best resources, it’s the best way to assure the best results.

3. Have a plan. Set out a reasonable implementation timeline and scope. Is your team dedicated to this project? If so, implementation will be shorter. If the project is another task on the ‘to do’ list, competing with other priorities, expect that your implementation may take more time. Follow the Epicor Signature process – plan, education, testing, validate, deploy. Don’t underestimate the time and resources it will take to complete the project successfully.

4. Provide the time and resources for training. You’ll be learning a new way of operating. This is a significant time commitment for everyone. Learn the software, and apply it to your business processes. You may need to modify what you do today to get the most out of your software.

5. Obtain accurate data. Are you coming from multiple legacy systems? You may need to clean up your data and understand the importance of setup in your new system. Your ERP system is only as good as the data in it.

6. Test your business processes. Have a list of all common business activities the software needs to cover and know the results you expect to achieve. Test all the scenarios, across your business functions.

7. Think before you customize. Highly customized solutions require higher costs. The customizations need to be scoped and tested prior to implementation. Most business processes are basically the same. Can you find a solution – use an ‘out of the box’ or slightly modified report or dashboard to solve your needs? Control the changes to your project scope.

8. Validate. After testing your business processes, conduct a ‘User Acceptance Test’ of the procedures, platform, and hardware you plan to implement. Users should be able to demonstrate their system knowledge prior to system implementation.

9. Continuous Improvement. Once you go live, allow time for the system to ‘settle out,’ then tackle the important items that surface to continue your business process improvements.