Anyone migrate from Dynamics 365 to Epicor? I’ve never done a migration and looking for some pointers and/or basic game plan.
Every ERP system has its own table structure. I don’t remember how Dynamics does theirs, but its different than Epicor. Take some time and refresh your memory about how that Dynamics table structure operates.
THEN take some time and learn how Epicor’s table structure operates. The “Field Help” functionality can be invaluable here, there is a Data Dictionary that describes each table and its fields, and the BAQ tool can be used to see how the major tables relate to each other.
Make a data map. List out how tables/fields in Dynamics will relate to tables/fields in Epicor.
If you can put the effort in at the beginning, the backside becomes a lot easier.
1 Like
Also, WRITE DOWN all your current Dynamics processes. There will be some things that Epicor does differently than Dynamics does, and you’ll need to modify (or perhaps even significantly change) the way you do certain things. There is also going to be different functionality that you can maybe take advantage of. Be bold when you’re starting off, try everything, don’t be afraid to say wow this is better OR wow this really sucks.
Do the easy stuff first. Get some wins under your belt, then start tackling the more challenging stuff.
If there was a magic bullet I’d be a billionaire by now…
2 Likes
I’ve worked with Epicor for a while, but I took a new position that is multi-site. One of those sites is on Dynamics 365 and they are wanting to migrate them over into Epicor. I am thinking we could use the DMT Migration for the data migration and work the rest out as we go. Does that sound correct?
1 Like
Although that will probably work in the technical sense, don’t skimp on the mapping and processes parts… the less you do beforehand the more your users will need to make up for it afterwards.
2 Likes
To second @Ernie’s point - map out how you want your processes to work, not just how they work in Dynamics. Likely some of your current processes were designed the way they are because of how Dynamics works. This is a great opportunity to drive out non-value-added steps and make changes to better fit how you want the business to run.
1 Like
Have the team moving from Dynamics go through Epicor Education… learn what they are moving TO better than what they are moving from.
My illustration is: When you buy a new car, you sit down in it, and you learn where everything is. It is different from your old car… the radio is in a different place, you turn on the air and heater differently, the cruise control is on a lever on the steering column instead of the steering wheel… You probably take out the manual to learn how things are done differently.
Moving to a different ERP system is very similar… but many people look at the differences and immediately try to modify the new system to look/work like the old one.
By fully learning the new system, and MANUALLY entering / transfering a few of the data records from the old to the new, you will learn what is important to move, and what is not.
Example: Dynamics may have 100 more fields in their customer table than Epicor has… but in reality many of the fields may be stored in other tables, and when you really examine it, the number of fields you REALLY need to move are a small subsite (10 address fields, shipping method, terms, credit limit, customer type, etc)… the balance of the fields may be system maintained, so do not need to be moved. THIS is why i say “manually enter the data the FIRST time to find out what is important and where it goes.”… then once you find that out, you can start your data migration with DMT.
3 Likes
Thanks for this @timshuwy honestly, I can’t recall the number of times I’ve heard the expression “But E10…”.
“In Vantage we…”
ahahah classic 
