Yardi Voyager Data Conversion: Data Mapping Consultant Tips

 http://www.lupinepartners.com/data-conversion - David Wolfe of Lupine Partners explains data mapping in reference to Yardi Voyager data conversions.

First of all, it’s important to realize your old software system and Yardi Voyager store data differently - they are different systems.  So, in order to electronically convert the data, the fields in the old system must be mapped to the fields in Yardi system.  Most users are going to need help doing this, because they are familiar with the schema of the old system, but not necessarily with Yardi’s.  If you are in charge of mapping the data, it is best to work backwards from Yardi’s schema to the source system’s schema.  This is due to Yardi being the ‘catcher’ of the data - the source system being the ‘pitcher.’  Since we are migrating to Yardi, then its schema and data rules are what will dictate during the mapping process.  Begin with the mandatory columns for a table in Yardi and work backwards to an equivalent column in the source database.  If a column is in Yardi but not in the source database, then this is considered a ‘gap’.  Gaps can be ignored, or the relevant data can be compiled outside of the source database and entered/imported into Yardi.