From a development perspective, I wish I'd known that there is "new code" and "classic code" with entirely different development methodologies. Most of the important stuff is still in classic code mode.

Credit Card processing could be better. If you authorize a CC on a sales order you can only have 1 un-invoiced delivery at a time. At least with PAYA.

A gold solution partner today might be a "who is that, never heard of them" tomorrow... xD

Overall Sage itself is great though. Very flexible once you learn it's tricky ways.

I think the best feature of Sage EM is its flexibility (the ability to develop specific to change the standard process). This offer a large range of possibilities. But this is as well a risk: specific develop has down sides (immediate cost of service, extra workshop to design the specific, extra testing, more complex support and maintenance).

So I would advise to identify from the start of your project what is the 10 critical outcomes of the project and focus specific on these only. For the rest, try to adopt the standard solution (work around, some work done outside fo the system, etc.) at first. After getting used to the products, you will be better fitted to identify the "real" pain point and work on these topics in a second phase.

I hope it makes sense. I wish you a nice journey to Sage EM.

We just went live last month (5/2019).  A few lessons learned would be:

- test...test...test - we thought we did a lot of testing but it wasn't even close to enough.

-Try to back fill positions or in the very least extend your timeline to allow people to work on Sage and their other work

-Make notes - We had so many times that a consultant would make and change and a month or two later no one on the core team could remember why we made the change.

-Hold your team accountable.  I was the PM on our team and it was my first time.  Everyone kept saying they had done a ERP implementation before so i didn't press anyone when it came to issues or deadlines.  Just because they have done something like this before doesn't mean they know what they are doing.

-Lastly- have a clear path of where you are going.  So many times we skipped a core meeting because people were busy and we then couldn't remember what we were supposed to be doing.

I hope this helps and is what you are looking for.  I wish you the best of luck!

We are 18 months into our Sage EM project and we haven't gone live yet! Make sure whoever is doing the configuration understands both Sage EM/X3 and your business thoroughly. 

I second this!  We started with an accounting constant that just didn't fit with us and we had to get a different one.  It was a bit rough and awkward but the new consultant was/is amazing.  This should also not be understated for your PM.  Make sure they are blocking times with consultants after dry runs / pilots.  We had an issue where the consultants were booked directly following our runs and so they couldn't answer or get to any of our questions for a week or more.