This is payroll data only. I realized there is not necessarily a one-to-one mapping. Some data is split out from one table in VP 10 into multiple tables in Pro. Data that was not normalized is sometimes normalized in Pro. However, I would have thought they would have created a document to determine the changes prior to coding the conversion routines (how else to you validate the conversion routines). They claim there is no such document, so it was never created, no longer exists, they don't want to look for it, or they don't want to supply it.

>The "mapping" between VP and Pro uses business rules, not one for one mapping, since Pro has much richer functionality and structures its data differently.
>For example Pro is lot based and VP is not, etc, etc, so the VP data must be restructured to follow Pro's business rules.
>Depending on what tables you want to "map", it can be hairy at best and excuciating at worst.