Inspect the affected item
- Confirm the selected inventory and mapping run belong to the intended source and destination.
- Compare the source item path and the candidate destination path, including the library and parent folders.
- Open the intended destination item directly to confirm it exists and is the migrated copy.
- Read the mapping method, status, and review reason. An uncertain candidate should not be treated as an approved match.
Common reasons for a mismatch
| Reason | Next action |
|---|---|
| The file was not migrated | Complete or correct the content migration, then inventory and prepare again. |
| The destination library or folder structure differs | Check the selected container and paths. Rebuild the mapping after correcting the scope or migrated structure. |
| Several files have the same name | Use the full path and the review detail; a matching filename alone is not conclusive. |
| A recent move or rename is absent from the inventory | Refresh the affected inventory and rebuild the plan. |
| The item is outside the scan scope or limits | Review the scan configuration and completion detail before relying on its coverage. |
Recheck the final access plan
After correcting the mismatch, prepare the affected batch again. Confirm the new plan points to the correct destination and still names the intended recipients and roles.
A mapping fix and an identity fix solve different problems. A file can be matched correctly while its recipient still needs a decision, or the recipient can be matched while the file is missing.