Laserfiche WebLink
While Tyler's data conversions teomhas extensive experience with data mining, conversion and <br />migration, it your responsibility to provide Tyler with readable conversion data and' to review the <br />converteddatafpreccu/aeyamdcunopleteness.YourTy|erimp|ementadon1eannguidesyouthromgh <br />the process, starting with conversion analysis and mapping, followed by interactive data conversions <br />and valiclations, and ending with final testing and loading into your production environment. Within <br />three implementation stages, critical data conversion work packages outline the steps needed. <br />Tyler does not provide services fordataex<ractionfrormyowrle8mtysyskym.Yourprojeetteann <br />resources are responsible for extracting and providing the data from the legacy system tmowrin- <br />hmusaconversionteamintherequiredformais.VVedomo{par<mervv|tbthirdpudyproviderntooffer <br />thhsserviceandthus,camnmtidentifythenesourceo.VVecanrccommendturrenicUenLsvvhohave <br />utilized third party services for more research nmthe client side. <br />4.5.1 AsSESS AND DEHNE: DATA MAPPING AND DEQGN <br />At the beginning of the project, data from your legacy application is mapped to the Tyler system, You <br />will be expected to ensure that the data extracted is well defined and conforms to the same format <br />with each extract. The Assess and Define stage sets a path which, when followed precisely, leads to <br />success with subsequent conversion activities in the remaining project stages. Th�s critical step <br />includes, but is not limited to: <br />0 Comprehensive mapping and migration of legacy data <br />• Creation of a road rnap defin:ing conve,rsion approach, data extract strategy,conversion and <br />reconcNiatimnstra1egy <br />• Outline of migration mandates and best practices govern�ng the layout of the destination <br />storage environment <br />Such communication will incUude: <br />w Comprehensive review and evaluation of legacy system data with specific attention to <br />general data quality, viability and identification of overt "scrubbing" necessities <br />Tyler's conversion programmer examhnesyour data files and layouts, and uses the supporting <br />materials to interpret, crosswalk and generally re -arrange the data from the legacy system into the <br />new database. Working collaboratively, the tearns address conversion errors and report <br />discrepancies. This iterative data conversion and validation stage includes: <br />0 Data loaded, tested, reviewed, and validated <br />0 Stakeholder acceptance of data quality, viabilfty and operability <br />Much attention is given to data integrity during the testing phase by the conversion developers. The <br />conversion developer spends time testing to ensure the data conforms to the database definition and <br />standards. Your team and the Tyler implementation team work on testing the balances and output of <br />37 <br />City ql'�(xdh lfefuJ, IN <br />