Data Migration Sample Clauses
The Data Migration clause outlines the responsibilities and procedures for transferring data from one system or service to another, typically during the transition between service providers or platforms. It specifies the scope of data to be migrated, the format and timing of the transfer, and any technical or security requirements that must be met. This clause ensures that data is moved efficiently and securely, minimizing disruption to business operations and reducing the risk of data loss or unauthorized access during the migration process.
POPULAR SAMPLE Copied 149 times
Data Migration. Upon expiration or earlier termination of the contract, Contractor agrees that University may elect to have Contractor migrate any stored University data to University computer at no cost to University, or for Contractor to provide the data to University in another form which is acceptable to University at no cost to University.
Data Migration. First Due understands the importance of data migration to our customers and has extensive experience working to migrate historical records into the platform. First Due will use best efforts to migrate applicable data from Customer’s existing systems utilizing data migration best practices. This includes: • Data Migration Planning Session • Assistance/Guidance in extracting data from existing system/s • Mapping extracted data to First Due import workbooks • Importing of Data into First Due The Data Migration scope of this Statement of Work will be to import legacy data from Customer existing systems in order for the Purchased Products to be operational. This includes operational data and historic records. Note that there are times when certain data is not seen as valuable to migrate to First Due. First Due and Customer will agree during the planning phase on what data needs to be migrated and priorities around data migration.
Data Migration. Upon expiration or earlier termination of the contract, Contractor agrees that University may elect to have Contractor migrate any stored ASU data to ASU computer at no cost to ASU, or for Contractor to provide the data to University in another form which is acceptable to ASU at no cost to ASU.
Data Migration. 2.1 In many circumstances, We can help facilitate a bulk migration to the platform using local data import. This is priced on a time-and-materials basis from Our SFIA rate card.
2.2 We can also help facilitate a bulk migration to the platform using offline data ingest and extraction — please ask Us for details.
Data Migration. Upon request, we may provide reasonable assistance to you, and any third party nominated by you in relation to the migration of any data related to the [Software Product] and the costs and outlays relating to such assistance will be at your own cost and payable to us.
Data Migration. 4.1 NEXGEN will migrate legacy data provided by City using the data import template provided by NEXGEN, into NEXGEN AM. NEXGEN will migrate work history, asset inventory, warehouse inventory and resources. City’s existing asset inventory is currently maintained in multiple electronic database and spreadsheet sources.
4.2 NEXGEN will import maintenance plans prepared by and provided by City into NEXGEN AM.
Data Migration. The County intends to maintain all historical data in the current system. At the minimum, the County must have all current balances and sufficient historical data to full utilization of the new solution. The County will collaborate with the vendor to determine the appropriate scope for data conversion needs and alternatives.
Data Migration. 11.3.1 The Service Provider must perform the data conversion and migration Services described in the Data Migration Plan, Schedule 2 - Attachment B - Register ICT Service Requirements and Schedule 2 - Attachment C - Functional Requirements.
11.3.2 For data conversion and migration, the Data Migration Plan may include the following stages:
(a) assessment and definition of the:
(i) the Incumbent Service Provider's existing system;
(ii) Health Data migration goals;
(iii) required Deliverables; and
(iv) complexity of the project, End User experience and requirements;
(b) development of a data conversion and migration strategy that is appropriate for Health's needs and End Users covering all appropriate planning and timetabling issues associated with the data conversion and migration including:
(i) identification of the Services to be performed;
(ii) identification and procurement of any necessary products;
(iii) allocation of responsibilities within each Party’s organisation;
(iv) staging of the project;
(v) whether a data warehouse will be used as a staging mechanism in the migration of data;
(vi) development of a Milestones; and
(vii) implementation of the Services;
(c) preparation/pre-migration which may include recovering data, designing extraction and functional specifications, and developing contingency arrangements should the migration of the Health Data not be successful;
(d) procurement or design and development of relevant software and systems to effect the data conversion and migration;
(e) migration including installation of the migrated data including (as applicable) development of associated Documentation and training of users; and
(f) testing and Acceptance of the migrated data in accordance with clause 25.
11.3.3 Once the Service Provider receives the Health Data, thereafter the Service Provider is responsible for backing up any Health Data on which it has performed any Services.
11.3.4 Where the data migration and deployment Services are to be performed using Third Party Software, software tools, object libraries, other items or methodologies owned by the Service Provider or any other party, the Service Provider must use reasonable endeavours to provide Health with an overview of the Third Party Software, software tools, object libraries, other items or methodologies that are used by the Service Provider.
Data Migration. TCS scope of work includes uploading the historical data / setting up the master data from existing applications into TCS Platform:- • <Master data of all active employees as on Go-Live date • Transaction data for all employees e.g. leave balances, additional payments/deductions etc. for current financial year • Payroll register for the financial year as on the Go-Live date • Performance and compensation data for the financial year as on the Go-Live date> TCS would provide pre-defined file formats for data required for TCS Platform. Activities such as preparation of data extracts from the source systems, cleansing and conversion in to these formats would be carried out by Client. On the start of development phase Client shall provide data for <<OM and PM>> covering all business scenarios required for testing. The personal identifiable information in <<PM>> shall be masked before providing to TCS. Data for System Integration Testing ("SIT"), User Acceptance Testing ("UAT"), shall be provided as per the timelines defined in the plan in Annexure D. The final production data provided by Client shall be first time right and available within two (2) weeks of UAT start date, as given in Annexure D. TCS will be responsible to upload this data which has to be validated and signed off by Client in the production environment. TCS shall not be responsible for any liability resulting from failure to meet the timeline in case Client fails to perform its obligations of submitting good quality data as per the agreed schedule. Any such delay, whether in receipt of customer data or delayed due to corrections to the data, may also result in re-baselining of Go-Live schedule and evaluated and managed through Change Management procedure.
Data Migration. Where set out in the Technical Specifications, including in connection with Technical Specifications Section 31 (Technical and Software Support Services), the SI shall provide support and services in connection with migrating legacy Data and NFPS Data to the applicable target NFPS component or other location. The SI shall perform such services in accordance with Good Industry Practices.