Box scenarios updates 1012

migration/mm-faqs-box.md

@@ -1,5 +1,5 @@
 ---
-ms.date: 03/18/2021
+ms.date: 10/14/2024
 title: "Migration Manager Box FAQs"
 ms.reviewer: 
 ms.author: heidip
@@ -23,18 +23,18 @@ description: Migration Manager Box FAQs
 # Frequently Asked Questions: Migration Manager Box
 
 **Question:**   **What gets transferred?**</br>
-Answer: Only owned folders and the root files for each user are copied. If a user isn't the owner of data they can access, we don't copy it. Content may be automatically reshared after it's migrated so that each user has access to their content exactly as before.
+Answer: Only files and folders owned by each user are copied. For example, if "Folder B" is located in User A's account but owned by User B and shared with User A, it isn't scanned or migrated under User A. Instead, it's scanned and migrated under User B.
 </br>
 
-**Question:**  What happens to Box Notes?</br>
-Answer: Box Notes will not be converted during migration to a .docx format.
+**Question:**  **What happens to Box Notes?**</br>
+Answer: Box Notes are converted during migration to a .docx format.
 
 **Question:**  **Is this available for GCC, GCCHigh, DoD tenants?**</br>
 Answer.  Currently Migration Manager Box isn't available for any of the Government clouds.
 </br>
 
 **Question:**   **Does Migration Manager Box sync files?**</br>
-Answer: There's a source-to-destination delta; when you run a transfer, we compare the destination directory to the source, and only transfer new or modified files over. We call this our incremental feature. We compare the timestamps of the files in both the source and destination and transfer the newest versions only. The incremental feature is always on.  Here are a few examples of how we deal with changes to files and folders.
+Answer: There's a source-to-destination delta; when you run a transfer, we compare the destination directory to the source, and only transfer new or modified files over. We call this our incremental feature. We compare the timestamps of the files in both the source and destination and transfer the newest versions only. The incremental feature is always on. Here are a few examples of how we deal with changes to files and folders.
 
 - **Content changes**: If a document is edited in your source or you've added a few new files, we copy them to your destination on the next incremental run, overwriting the previously existing file(s) in the destination.
 
@@ -44,23 +44,23 @@ Answer: There's a source-to-destination delta; when you run a transfer, we compa
 </br>
 
 **Question:**   **Does Migration Manager delete my files?**</br>
-Answer: No. We never delete your data from any source. We take your data from one place and copy it to another; akin to *copy and paste* rather than *cut and paste.* We also don't retain any of your cloud storage data for any reasons. 
+Answer: No. We never delete your data from any source. We take your data from one place and copy it to another; akin to *copy and paste* rather than *cut and paste*. We also don't retain any of your cloud storage data for any reasons.
 
 </br>
 
 **Question:**   **Can I rearrange content during a migration?**</br>
-Answer:  Not recommended. Any major changes in directory structure should happen before or after your migration. It's also not a good idea to use our app to rearrange content.  The risks that come with rearranging content during the migration are primarily in the form of data duplication; our incremental process sees all changes as new data. So, for example, if you change a folder name at the root, we detect that as a new folder, and all of the contents is retransferred, including all subfolders.  When sharing permissions are transferred, both owners and collaborators receive duplicate data if content has been rearranged or renamed.
+Answer: Not recommended. Any major changes in directory structure should happen before or after your migration. It's also not a good idea to use our app to rearrange content. The risks that come with rearranging content during the migration are primarily in the form of data duplication; our incremental process sees all changes as new data. So, for example, if you change a folder name at the root, we detect that as a new folder, and all of the contents is retransferred, including all subfolders.  When sharing permissions are transferred, both owners and collaborators receive duplicate data if content has been rearranged or renamed.
 </br>
 
 **Question:**   **What happens to external sharing links?**</br>
-Answer:  We don't recreate external sharing links. After migration, these have to be set in the destination manually.</br>
+Answer: We don't recreate external sharing links. After migration, these have to be set in the destination manually.</br>
 
 **Question:**   **What about external collaborators?**</br>
-Answer:  We don't share content with external collaborators. This policy is in place to protect your organization, and industry best practice is to never automatically share sensitive internal data with external users.</br>
+Answer: We don't share content with external collaborators. This policy is in place to protect your organization, and industry best practice is to never automatically share sensitive internal data with external users.</br>
 
 **Question:**   **Does Migration Manager preserve file versions?**</br>
-Answer:  No. During a migration, only the most recent version of a file is transferred.</br>
+Answer: No. During a migration, only the most recent version of a file is transferred.</br>
 
 **Question:**   **Does Migration Manager automatically notify users?**</br>
-Answer:  No.  We automatically suppress all emails to users so they aren't bombarded with excessive notifications about the data they now have access to.</br>
+Answer: No. We automatically suppress all emails to users so they aren't bombarded with excessive notifications about the data they now have access to.</br>
 

migration/new-migration-transition.md

@@ -40,7 +40,7 @@ Tenants with ongoing migration projects will experience transition UI elements:
 * **October 8th, 2024**: The Transition UI will be released, featuring a New Migration switching panel in the top-right corner of the project page. You can select  "Switch now" button to switch to the New Migration.
   + **Before Switching**: You may occasionally see pop-up prompts encouraging you to switch to New Migration. If you don't switch proactively, the transition will be mandatory starting **November 11th**. 
   + **During Switching**: The transition process may take a few moments but won't affect your ongoing migration tasks. 
-  + **After Switching**: New Migration will become the default service, and new migration tasks can only be initiated in New Migration. An entry point to Old Migration will remain available for reviewing or completing any unfinished migration tasks. Old Migration will be permanently closed on **December 16th**. Download any summary or detailed reports beforehand if you wish to retain the migration history from Old Migration.
+  + **After Switching**: New Migration will become the default service, and new migration tasks can only be initiated in New Migration. An entry point to Old Migration will remain available for reviewing or completing any unfinished migration tasks. Old Migration will be permanently closed on **December 11th**. Download any summary or detailed reports beforehand if you wish to retain the migration history from Old Migration.
 
 >[!NOTE]
 > If you encounter any transition issues, please feel free to contact us through the 'Give Feedback' widget at the bottom right of the page.