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 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. 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. 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 transactions as on 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. 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. 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. 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. 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. 6.5.1 The parties shall each use their best endeavours to ensure that Data Migration is able to take place by *** in respect of the NatWest Businesses and by *** in respect of the RBS Businesses or such other dates as may be agreed by the parties acting reasonably.
6.5.2 The Business Sellers and the Purchaser shall take all such steps as may be necessary to ensure that Data Migration is able to take place by the Long Stop Date in respect of the NatWest Businesses and by the RBS Businesses.
6.5.3 The Business Sellers and Purchaser shall each use their best endeavours to ensure that the Mid-Corporate and Complex SME Data Migration is able to take place as soon as reasonably practicable following the NatWest Closing in respect of the NatWest Businesses and as soon as reasonably practicable following the RBS Closing in respect of the RBS Businesses.
6.5.4 Each of the Business Sellers and the Purchaser shall provide to each other such information as the other party may reasonably require to enable it to satisfy its obligations in Clause 6.5.1, 6.5.2 and 6.5.3, including the Business Sellers’ provision of:
(i) in each case, all data definition files relating to the Business Data;
(ii) in each case, all rules relating to the Business Data;
(iii) in each case, a break down of the Business Data by Customer, Product and channel; and
(iv) in the case of Clause 6.5.3, information relating to:
(a) the retail internet channel XML shell;
(b) the process by which Customers are identified, routed and granted access to their account details and services;
(c) the Customer experience with respect to each channel relating to the SME Business and Mid-Corp Business; and *** Material has been omitted pursuant to a request for confidential treatment and has been filed separately.
(d) which processes relating to the SME Business and Mid-Corp Business are automated and which are undertaken manually.
6.5.5 Without prejudice to the provisions of Clause 6.5.2 and 6.5.3, the Business Sellers shall provide the Business Data to the Purchaser:
(i) in relation to the Retail Business and SME Business (other than in respect of Complex SME Customers) at the relevant Closing; and
(ii) in relation to the SME Business (in respect of the Complex SME Customers) and Mid-Corporate Business at the Mid-Corporate and Complex SME Data Migration Date, in each case, in such format as the parties (acting reasonably) agree.
Data Migration. (a) The Supplier is responsible for all data migration activities associated with XL Data (as detailed in the Data Migration Plan) as part of the Integration Services, and must undertake data migration so as to ensure that no XL Data is lost or corrupted.
(b) Without limiting clause 24.1(a) above the Supplier must:
(i) retain back-up copies of all XL Data being migrated;
(ii) ensure that in the event of any data migration failure or problem, XL is able to utilise the XL Data within the XL Systems to store and process the XL Data so that XL’s business operations are not affected.
(c) In the event of any breach by the Supplier of this clause 24.1 which adversely impacts on XL’s business operations in any way, and without limiting any of XL’s other rights and remedies, the Supplier must, at no additional cost to XL, immediately work with XL to identify any possible workarounds to the cause of the adverse impact, and provide resources (where necessary) to implement workarounds approved by XL in writing.
