[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-detail-166490-en":3,"doc-seo-166490-105":30,"detail-sidebar-cat-1-en-105":91},{"code":4,"msg":5,"data":6},0,"success",{"doc_id":7,"user_id":8,"nickname":9,"user_avatar":10,"doc_module":11,"category_id":12,"category_name":13,"doc_title":14,"doc_description":15,"doc_content":16,"file_id":17,"file_url":18,"file_type":19,"file_size":20,"view_count":4,"is_deleted":4,"is_public":11,"is_downloadable":11,"audit_status":11,"page_count":21,"language":22,"language_code":23,"site_id":24,"html_lang":23,"table_of_contents":25,"faqs":26,"seo_title":27,"seo_description":15,"update_tm":28,"read_time":29},166490,549768064778,"Felix Montgomery","https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8",1,18,"Letters","Document History and Distribution","Document History and Distribution specifies governance for a source-to-target system migration, defining how document assets, versions, metadata, permissions, and related documents are transferred. It outlines a structured processing plan driven by source document number ranges, describes delta runs to capture newly created or modified content, and sets expectations for cutover timing to avoid conflicting updates. The document also covers revision tracking, confidentiality obligations, mappings, and supporting scripts.","Migration Document\nSource System to Target System\nSeptember 1, 20xx\nVersion x.x\n\u000f\n\u0003Contents\n\u0013 TOC \\o \"1-3\" \\h \\z \\u \u0014\u0013 HYPERLINK \\l \"_Toc481734097\" \u0014Document History and Distribution\t\u0013 PAGEREF _Toc481734097 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734098\" \u0014Revision History\t\u0013 PAGEREF _Toc481734098 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734099\" \u0014Statement of Confidentiality\t\u0013 PAGEREF _Toc481734099 \\h \u00144\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734100\" \u0014Overview\t\u0013 PAGEREF _Toc481734100 \\h \u00145\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734101\" \u0014Migration Processing Plan\t\u0013 PAGEREF _Toc481734101 \\h \u00145\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734102\" \u0014Delta Runs\t\u0013 PAGEREF _Toc481734102 \\h \u00145\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734103\" \u0014Changes to Processing Order and Delta Run Frequency\t\u0013 PAGEREF _Toc481734103 \\h \u00146\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734104\" \u0014Sample Runs\t\u0013 PAGEREF _Toc481734104 \\h \u00146\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734105\" \u0014Meta-data Mapping\t\u0013 PAGEREF _Toc481734105 \\h \u00146\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734106\" \u0014Folders and Path Mapping\t\u0013 PAGEREF _Toc481734106 \\h \u00148\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734107\" \u0014Permissions Mapping\t\u0013 PAGEREF _Toc481734107 \\h \u00149\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734108\" \u0014File Types\t\u0013 PAGEREF _Toc481734108 \\h \u001410\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734109\" \u0014Version mapping\t\u0013 PAGEREF _Toc481734109 \\h \u001411\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734110\" \u0014Zero Byte Versions\t\u0013 PAGEREF _Toc481734110 \\h \u001411\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734111\" \u0014Related Documents\t\u0013 PAGEREF _Toc481734111 \\h \u001411\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734112\" \u0014Miscellaneous Details and Assumptions\t\u0013 PAGEREF _Toc481734112 \\h \u001411\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734113\" \u0014Required Scripts\t\u0013 PAGEREF _Toc481734113 \\h \u001412\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734114\" \u0014Group Translation\t\u0013 PAGEREF _Toc481734114 \\h \u001412\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734115\" \u0014Date and Time Merge\t\u0013 PAGEREF _Toc481734115 \\h \u001412\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734116\" \u0014Target System Category ID Translation\t\u0013 PAGEREF _Toc481734116 \\h \u001412\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734117\" \u0014Blank Client/Matter Assign Hardcoded Value\t\u0013 PAGEREF _Toc481734117 \\h \u001413\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734118\" \u0014Client and Matter Translation\t\u0013 PAGEREF _Toc481734118 \\h \u001414\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734119\" \u0014SUBCAT_ID and SUBSUBCAT_ID Translation\t\u0013 PAGEREF _Toc481734119 \\h \u001414\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734120\" \u0014Merge Version Attributes\t\u0013 PAGEREF _Toc481734120 \\h \u001415\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734121\" \u0014Product Enhancements\t\u0013 PAGEREF _Toc481734121 \\h \u001415\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734122\" \u0014Message and Parent Message ID Mapping\t\u0013 PAGEREF _Toc481734122 \\h \u001416\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734123\" \u0014Migration Results Report\t\u0013 PAGEREF _Toc481734123 \\h \u001416\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc481734124\" \u0014Acceptance\t\u0013 PAGEREF _Toc481734124 \\h \u001418\u0015\u0015\n\u0015\u0004\n\u000f\nDocument History and Distribution\nRevision History\n\u000fStatement of Confidentiality\n© 2017 SeeUnity, Inc. All rights reserved.  SeeUnity and the corporate logo are trademarks or registered trademarks of SeeUnity, Inc. in the United States and throughout the world. All other company and product names are used for identification purposes only and may be trademarks of their respective owners.\nThe material contained in this document is proprietary to SeeUnity. No rights in said material are hereby transferred to Client (“Client”, or “Customer”).  This material may not be disclosed, duplicated or otherwise revealed, in whole or in part, without prior written consent.\n\u000f\nOverview\nThe Source System to Target System migration project at Client will be conducted as outlined in this Migration Document.  From a high level the following information will be migrated from the Client (CLIENT) Source System database to the Target System library:\nDocuments\nVersions\nMeta-data\nSource System path structures will be migrated to meta-data objects.\nPermissions\nRelated Documents\nEach type of data that will be migrated is outlined in detail below.\nMigration Processing Plan\nThe order of content to be migrated will be based on document number ranges. The largest Source System document numbers will be brought over first. The following document number ranges will be targeted and processed in roughly","cbCaikhnykncdB32","https://ap.wps.com/l/cbCaikhnykncdB32","docx",824716,17,"English","en",105,"# Document History and Distribution\n## Revision History\n## Statement of Confidentiality\n## Overview\n## Migration Processing Plan\n## Delta Runs\n## Changes to Processing Order and Delta Run Frequency\n## Sample Runs\n## Meta-data Mapping\n## Folders and Path Mapping\n## Permissions Mapping\n## File Types\n## Version mapping\n## Zero Byte Versions\n## Related Documents\n## Miscellaneous Details and Assumptions\n## Required Scripts\n## Group Translation\n## Date and Time Merge\n## Target System Category ID Translation\n## Blank Client/Matter Assign Hardcoded Value\n## Client and Matter Translation\n## SUBCAT_ID and SUBSUBCAT_ID Translation\n## Merge Version Attributes\n## Product Enhancements\n## Message and Parent Message ID Mapping\n## Migration Results Report\n## Acceptance","[{\"question\":\"What content types are migrated from the source system to the target system?\",\"answer\":\"The migration transfers Documents, Versions, Meta-data, Permissions, and Related Documents. It also migrates source system path structures into metadata objects.\"},{\"question\":\"How does the document processing order get determined?\",\"answer\":\"Processing order is based on document number ranges, bringing over the largest source system document numbers first. The ranges may be changed to improve performance as the migration progresses.\"},{\"question\":\"Why are delta runs executed during and after migration?\",\"answer\":\"Delta runs copy newly created and modified content that appears after the initial range-based migration. Final delta runs are scheduled around cutover so that target content remains consistent until updates complete.\"}]","Document History and Distribution | DOCX",1788193971,6,{"code":4,"msg":31,"data":32},"ok",{"site_id":24,"language":23,"slug":33,"title":14,"keywords":34,"description":15,"schema_data":35,"social_meta":86,"head_meta":88,"extra_data":90,"updated_unix":28},"document-history-and-distribution","",{"@graph":36,"@context":85},[37,54,68],{"@type":38,"itemListElement":39},"BreadcrumbList",[40,44,48,51],{"item":41,"name":42,"@type":43,"position":11},"https://docshare.wps.com","Home","ListItem",{"item":45,"name":46,"@type":43,"position":47},"https://docshare.wps.com/template/","Template",2,{"item":49,"name":13,"@type":43,"position":50},"https://docshare.wps.com/template/letters/",3,{"item":52,"name":14,"@type":43,"position":53},"https://docshare.wps.com/template/document-history-and-distribution/166490/",4,{"url":52,"name":14,"@type":55,"author":56,"headline":14,"publisher":58,"fileFormat":61,"inLanguage":23,"description":15,"dateModified":62,"datePublished":62,"encodingFormat":61,"isAccessibleForFree":63,"interactionStatistic":64},"DigitalDocument",{"name":9,"@type":57},"Person",{"url":41,"name":59,"@type":60},"DocShare","Organization","application/vnd.openxmlformats-officedocument.wordprocessingml.document","2026-08-31",true,{"@type":65,"interactionType":66,"userInteractionCount":4},"InteractionCounter",{"@type":67},"ViewAction",{"@type":69,"mainEntity":70},"FAQPage",[71,77,81],{"name":72,"@type":73,"acceptedAnswer":74},"What content types are migrated from the source system to the target system?","Question",{"text":75,"@type":76},"The migration transfers Documents, Versions, Meta-data, Permissions, and Related Documents. It also migrates source system path structures into metadata objects.","Answer",{"name":78,"@type":73,"acceptedAnswer":79},"How does the document processing order get determined?",{"text":80,"@type":76},"Processing order is based on document number ranges, bringing over the largest source system document numbers first. The ranges may be changed to improve performance as the migration progresses.",{"name":82,"@type":73,"acceptedAnswer":83},"Why are delta runs executed during and after migration?",{"text":84,"@type":76},"Delta runs copy newly created and modified content that appears after the initial range-based migration. Final delta runs are scheduled around cutover so that target content remains consistent until updates complete.","https://schema.org",{"og:url":52,"og:type":87,"og:title":14,"og:site_name":59,"og:description":15},"article",{"robots":89,"canonical":52},"index,follow",{"doc_id":7,"site_id":24},{"code":4,"msg":5,"data":92},[93,98,103,108,113,118,122,125,130],{"id":94,"doc_module":11,"doc_module_name":46,"category_name":95,"show_sort_weight":96,"slug":97},11,"Presentations",90,"presentations",{"id":99,"doc_module":11,"doc_module_name":46,"category_name":100,"show_sort_weight":101,"slug":102},12,"Resumes",80,"resumes",{"id":104,"doc_module":11,"doc_module_name":46,"category_name":105,"show_sort_weight":106,"slug":107},14,"Invoices",70,"invoices",{"id":109,"doc_module":11,"doc_module_name":46,"category_name":110,"show_sort_weight":111,"slug":112},15,"Posters",60,"posters",{"id":114,"doc_module":11,"doc_module_name":46,"category_name":115,"show_sort_weight":116,"slug":117},16,"Social Media",50,"social-media",{"id":21,"doc_module":11,"doc_module_name":46,"category_name":119,"show_sort_weight":120,"slug":121},"Forms",40,"forms",{"id":12,"doc_module":11,"doc_module_name":46,"category_name":13,"show_sort_weight":123,"slug":124},30,"letters",{"id":126,"doc_module":11,"doc_module_name":46,"category_name":127,"show_sort_weight":128,"slug":129},21,"Paper Templates",5,"papers-templates",{"id":131,"doc_module":11,"doc_module_name":46,"category_name":132,"show_sort_weight":4,"slug":133},158,"General","general-158"]