Equivant - Laserfiche WebLink

Home Browse Search

equlvant Data Conversion Data Migration enables the Customer to retain the electronic case histories that have been assembled over time in the legacy system. Data will be converted from DAMiaN. This legacy data is processed and mapped to fit within the JWorks data structures . Data Conversion Overview The conversion process will require a Customer review of legacy data and will provide the opportunity for the Customer to perform data analysis and clean-up, plus mapping of legacy codes to the JWorks codes prior to moving data into JWorks. Identity Consolidation The consolidation, or deduplication, of identity records from the legacy data source is not included in the scope of work. equivant can provide an estimated cost for identity consolidation technical services if the Customer desires to have equivant perform this service. Conversion Strategy This Statement of Work includes a high-level overview of the strategy that equivant utilizes for data conversion of legacy data into the JWorks database. equivant will expand on this as well as update specific plans for the conversion effort. Part of the planning effort will be to make final decisions as to what legacy data will be converted through an automated data conversion effort. equivant will facilitate a data conversion planning session(s) with staff and provide a Data Conversion Strategy Plan deliverable for review and approval. The equivant conversion methodology includes seven distinct steps: • Data Mapping Business Rules • Script Development • Data Checking • Test Data load • Mock Implementation Run • Final Conversion Run • Stabilization The activities of each of these conversion steps are described briefly below . Data Mapping Business Rules Support During the data mapping and business rule process, equivant and the Customer will analyze the legacy system data model and determine which data needs to be migrated to JWorks and where it will be viewed within the application. The Customer is required to place the data from the legacy system, which is to be migrated to JWorks, into the equivant conversion data model. Detailed worksheets will be provided outlining the format (ASCII text files having fixed length data attributes) of these files. Some extraction files may be excluded, depending on the specifications of the existing legacy system. In addition, during the extraction process, data exceptions will be discovered, allowing the Customer to identify potential data constraints and cleanse legacy data. The baseline code set-up must be completed prior to the initial mock conversion, including the Conversion Mapping Utility, which allows the Customer to map its legacy codes to the corresponding JWorks codes. It is assumed that equivant will provide the on-line mapping utility and that the Customer will use this utility to complete the actual code value mapping. Once all rules and mappings are established, a formal acceptance document is generated outlining the decisions equivant Pagelll r.r ...... ' .• ~Yf ~~:I,<-.., ......... J". ,~ l!1.'4 ,,,,,,,,,,,,1