We are in the process of importing and migrating our data from a different system and I have a question regarding the order of operations for importing data.
What is the difference and/or purpose of the management vs migration menus? It seems like the migration menus guide you towards importing your data in a logical order and makes sense, but some things are missing that are only found in the management menu. Like ‘Part Plant’. So is there overlap between the two? or do you just use the management sections for things not included in the migration sections? Do people use the migration sections?
The migration uploads are for just that, imports in a logical order because some tables are prerequisites of others. Some tables or types may not be included because they are included in other uploads or required prior to the migration. I would assume you would complete you company configuration, part plant, companies, etc prior to any DMT’s.
We migrated from V8 to E10 via DMT. We did this so we could “cleanup” our V8 system (which had info in it since Vista 4 from 1997).
When we did that we used the “Migration” menus, which for the most part were ordered as you’d import them. I feel the Migration menus are geared towards an initial setup, and mostly hit your “base” tables (Customer, Part, GL structure, GL Accts, etc…), and not so much for things like Quotes, Orders, Invoices, etc…
Be warned that there can be circular references that would require several passes for the same table.
For example, If you are going to have multiple ShipTo’s for customers, and want to set a specific one as the default, you’d have to DMT into the following:
Customer - To create the Customer records
ShipTo’s - To create the Ship To records
Customer - To update the default ShipTo of the customer record.
You couldn’t set the default shipto in step 1, because ShipTo recs don’t exist yet. And you couldn’t make the ShipTo’s first, because they require an existing Customer record.
If I could only stress one thing about setting up E10 from scratch, and DMT’ing in the inital data… Be extra careful when it comes to the UOM system. Once part transactions are tied to a part, changing the UOM is very difficult - and more often, is impossible. Even just setting the cost of a part with zero QOH. That forever locks that part into the system (can’ be deleted), and its UOM might not be easily changed.