Migration Epicor 10.0.700 to 10.2.700

Epicor ERP 10
2

I’ve done 10.1.600 and 10.2.100 to 10.2.700 and basically, Epicor Signature Methodology.

Get the guide from EpicWeb and read it carefully, twice.

The longer answer is roughly like this (but FOLLOW THE UPGRADE PROCEDURE from EpicWeb). This is an oversimplification but gives an overview of what you’re looking at.

I paid Epicor $25,000 USD to do this for me, and in fact they didn’t do very much at all, aside from 40 hours of Zoom calls with an excellent Epicor engineer. In reality, this was my full-time job for 5 months, and if I did it again I would ONLY buy the time with the engineer. No other value to speak of came from the arrangement. 40 hours should cost 6000-10000 at most.

Anyways, it’s about like this:

  1. have a dev server

  2. make sure your servers are adequate

  3. install 10.2.700 on your dev servers and get it up and running with none of your data or custom stuff (a few hours)

  4. use solutions to deploy all your custom objects into dev, and fix everything that breaks (anything from a couple of weeks to several months). Do a separate solution for each object type, starting with UD tables, then BAQs, then BPMs, then UI. Use all the conversion and verification tools built into Epicor, and bring specific questions to this forum (searching for answers first, of course)

  5. once you have a running system, repackage all your custom stuff from dev into new solutions

  6. refresh your dev database from your production environment and let all the automatic conversions run, and test your system

  7. do steps 4, 5 and 6 until you don’t have any more issues and/or you start throwing furniture, depending on your tolerance for frustration

  8. once you know you can confidently do 4, 5 and 6, do it one more time and then get your smartest users from each department together

  9. with your smartest users, create a spreadsheet of tests that covers every step from quote to cash plus engineering and purchasing. Include things like running MRP, issuing POs, cycle counting, executing jobs, etc. Everything.

  10. go through that list and test each step. For every item that has a surprise, enter an issue on an issues list.

  11. repeat steps 4,5,6 and 10 until the issues are gone

  12. on a night when users can be kicked out for a day, shut everything down and take a server snapshot (this assumes your on a VM - if not, someone on here can advise you on the equivalent)

  13. restart everything without allowing users in

  14. take a backup of your database

  15. install 700 on your prod server

  16. (really, REALLY follow the procedures from EpicWeb)

  17. take a copy of anything in your externals folder

  18. delete your production appserver in the admin console and IIS, and delete all the appserver folders

  19. restore your db

  20. create your production appserver

  21. do steps 4,5 and 6 on production

  22. before you do any transactions, take another db backup (“deploy” backup). Your assumption at this point is that everything is perfect

  23. do a quote to cash test

  24. if everything is good, restore your “deploy” backup and let your users back in

  25. if anything’s a surprise at this point, abort go-live and restore your server snapshot.

  26. go back and do 4,5,6 and 10 in dev until you’re ready to try again

2 Likes