[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-250416-105":53,"doc-detail-250416-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","migration-process-overview-and-data-migration-plan","Migration - Process Overview and Data Migration Plan","","A formal guidance document defining end-to-end data migration responsibilities when moving “source data” from company control to a sponsor’s premises. It explains key handoff timing, handling of interim and final transfers, required formats and transformations, validated query-script execution, and data reconciliation between systems. The plan outlines audit-trail options, transfer media and frequency, validation evidence documentation, sponsor coordination around Last Patient Last Visit closure, and notification and documentation of migration activities.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":46,"@type":70,"position":76},"https://docshare.wps.com/template/paper-templates/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/migration-process-overview-and-data-migration-plan/250416/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/migration-process-overview-and-data-migration-plan/250416.png","ImageObject",442,249,{"name":88,"@type":89},"Chumphorn","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-14","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",9,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What is the central objective of the migration process described in this document?","Question",{"text":109,"@type":110},"To deliver data to a sponsor and migrate “source data” responsibilities from the company to the sponsor’s premises, including correct timing for when the source location changes.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What must be decided during the requirements phase regarding data migration?",{"text":114,"@type":110},"Agreement is needed on the needed data format and transformations, appropriate query script validations, and the content of interim data transfers including audit-trail and completeness (complete vs incremental).",{"name":116,"@type":107,"acceptedAnswer":117},"How does the document handle timing around Last Patient Last Visit (LPLV)?",{"text":118,"@type":110},"The sponsor is notified that the database will close within a specified number of hours at LPLV, then data entry is closed at LPLV plus the stated hours, after which a final output data file is compiled.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},250416,1790268898,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":45,"category_name":46,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":76,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":9},2336475401981,"https://ap-avatar.wpscdn.com/avatar/22000c94efd8d5204d?x-image-process=image/resize,m_fixed,w_180,h_180&k=1786935347598174694","Migration Rev. a 24 Apr 2003  \n1. Overview  \n1.1. Process overview  \nThe migration process describes the actions taken to deliver data to a sponsor and to migrate from one computing environment to another. A key point in this process is the declaration of when the“source data” location changes. This is a formal handoff of regulatory “source data” responsibilities and should occur once in the process. Another issue to manage is copies of data that must be delivered to multiple locations.  \nData migration should be discussed during the requirements phase of a project in order for all parties to agree on;  \na. Needed format along with any data transformations.  \nb. Appropriate query script validations.  \nc. Content of any interim data transfers.  \n1. With or without audit trails.  \n2. Complete or incremental.  \nd. Medium of data transfer.  \ne. Method of data reconciliation between systems.  \nThis process can also be used to internally migrate data from an existing legacy system to a new environment.  \nIt does not cover the succeeding decommissioning process, which ensures that the system is inventoried, de-energized, and all elements dispositioned.  \nThe Migration process covers:  \nß Requirement analysis and definition of migration.  \nß Development of migration tools.  \nß Conversion of software product and or data.  \nß Migration Execution.  \nß Migration Verification.  \nß Notification of migration activities.  \nß Appropriate documenting of the migration process  \n2. Data Migration Prerequisites  \n2.1. Sponsor has agreed to type and frequency of interim data transfers.  \n2.2. Sponsor has agreed to close data entry on xx days after Last Patient Last Visit.  \n2.3. Sponsor has agreed to transmit final data transfer on xx days after Last Patient Last Visit.  \nNote: Notify Sponsor that Company can only transmit data that has been entered into the system. At some point in time after LPLV data entry must close to allow for final data  \ntransfer.  \n3. Data Migration Plan (DMP)  \nThe data migration plan (DMP) documents all activities needed to successfully transfer data to a sponsor in a validated manner and “officially” moving the source data location from Company controled to sponsor premises. The following is the outline that should be documented using the DMP template.  \nMigration Rev. a 24 Apr 2003  \n3.1. Purpose of the Migration  \n3.1.1. A general purpose of the plan is discussed here outlining sponsor agreements.  \n3.2. Interim data transfers  \n3.2.1. Discuss what type of interim data transfers will occur. This includes complete or incremental, with or without audit trails.  \n3.2.2. Discuss the medium by which to transfer data. This can be CD, SSL, or persistent  \nconnection. Floppies are not to be used as they can be modified in transit unless encrypted.  \n3.2.3. Discuss the frequency of data transfer along with appropriate confirmations that transfer has occurred.  \n3.3. Final data transfers  \n3.3.1. Discuss what is to be included in a final data transfer. Discuss that one may not be required as the accumulation of interim transfers would suffice.  \n3.3.2. Discuss what data reconciliations are necessary to ensure the sponsor has the final dataset.  \n3.3.3. Discuss inclusion of full audit trial information.  \n3.3.4. Discuss the medium of data transfer.  \n3.3.5. State that the source data ownership is transferred to the sponsor during this stage.  \n3.3.6. Discuss how copies of source data will be available at investigator locations available for inspection by regulatory authorities in both paper and electronic format.  \n3.4. Data transfer validations  \n3.4.1. All interim and final data transfers need to be queried, transformed, and transmitted in a validated manner. This means that a set of requirements, designs, and code need to be documented and tested to ensure that the correct data is being transmitted with correct formatting.  \n3.4.2. Validation evidence can either be included in the DMP or as separate references.  \n4. Migration","cbCaibOIBUQVS9Ti","https://ap.wps.com/l/cbCaibOIBUQVS9Ti","pdf",24517,"English","# Overview\n## Process overview\n## Data Migration Prerequisites\n# Data Migration Plan (DMP)\n## Purpose of the Migration\n## Interim data transfers\n## Final data transfers\n## Data transfer validations\n# Migration Process\n## Periodic Basis\n## Near Last Patient Last Visit (LPLV)\n# Data Migration Flow\n## Data migration activities\n# Internal System Migration Process","[{\"question\":\"What is the central objective of the migration process described in this document?\",\"answer\":\"To deliver data to a sponsor and migrate “source data” responsibilities from the company to the sponsor’s premises, including correct timing for when the source location changes.\"},{\"question\":\"What must be decided during the requirements phase regarding data migration?\",\"answer\":\"Agreement is needed on the needed data format and transformations, appropriate query script validations, and the content of interim data transfers including audit-trail and completeness (complete vs incremental).\"},{\"question\":\"How does the document handle timing around Last Patient Last Visit (LPLV)?\",\"answer\":\"The sponsor is notified that the database will close within a specified number of hours at LPLV, then data entry is closed at LPLV plus the stated hours, after which a final output data file is compiled.\"}]","Migration - Process Overview and Data Migration Plan | PDF",1789254869]