M365 tenant to another tenant migration issue

Please note that our forum is a public platform, and we will modify your images to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

Dear Md. Nasir Uddin
Thank you for reaching out to the Q&A Forum. 

Based on my research, regarding completed import jobs:

• If you delete these completed jobs: There will be no impact on the imported data. Once the status is Completed, the data is already in the target mailbox. 
• If you keep them: It simply retains the job history for auditing or troubleshooting purposes. If this is not required for compliance, you may safely delete them. 

Note: Microsoft automatically deletes PST files from Azure Storage after 30 days, regardless of whether the job is deleted in the portal. (Reference: After I upload my PST files to the Azure Storage area, how long are they kept in Azure before they're deleted?)

There is a possibility of duplication as noted in the official documentation How does the PST import process handle duplicate email items? Since I do not have a testing environment and configurations or permissions may vary, based on theoretical best practices, I suggest the following approach:

• Review and Repair: First, identify the failed PST files in the job report and check the "Status Detail" column. If the error indicates "Corrupted Items" or the file is too large, run SCANPST.EXE locally to repair the PST. 
• Create New Mapping: Create a new mapping CSV that includes only those failed (and repaired) PSTs. Remove any rows for files that were successfully imported. 
• Re-Import: Create a new import job and upload this updated CSV. 

This approach might ensure that only the missing data is imported without duplicating successful items. 

Regarding VM shutdown during analysis, there is no impact if the PST files have already been uploaded because the analysis/import process runs on Microsoft’s backend. However, if the VM is still uploading files when it shuts down, the upload will fail. You may also review this section for additional insight: Import job is stuck or running slowly. Please clarify your current job status: 

• If Import in progress, it’s best to keep the VM running until the upload completes. 
• If Analysis in progress, you can safely turn off the VM. 

For further details, you may refer to these resources: 

• Purview PST import very slow, seeminly stuck on analysis
• Import Jobs to office 365 mailbox Stuck at Analysis in Progress.-

I hope this information is helpful. If you have any additional questions, please do not hesitate to reach out. 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.