Results & troubleshooting

Track exceptions and export review evidence

Keep an actionable record of blocked, failed, skipped, and manually reviewed work.

Quick answer

Use the batch review/results for the immediate scope and Reports → Exceptions for operational follow-up. Export the relevant evidence rather than relying on a summary count alone.

Your next step

Review each unresolved issue and record its cause and intended follow-up before expanding the migration.

Save the review you approved

In a batch's access review, Export access review captures proposed source/destination items, recipients, access levels, readiness, and reasons. It is useful for peer review and the change record.

That pre-execution export is a plan, not evidence that the proposed changes were applied. Keep the execution and verification results alongside it.

Use exceptions as a work queue

  1. Open Reports and choose Exceptions.
  2. Filter to the relevant project or scope using the available controls.
  3. Inspect the reason and affected item/run for each issue.
  4. Use the supported follow-up controls to record the investigation or resolution.
  5. Return to the underlying batch to fix mappings, prepare again, or retry when needed.

Choose the right export

NeedEvidence to keep
What was proposedBatch access review export.
What happenedExecution and verification details for the exact run.
Where new sharing links pointLink recovery's Export link map output.
A broader project/batch evidence bundleReports → Audit packages, with the required privacy and retention choices.

Share evidence with the intended audience

Exports can contain paths, names, email addresses, and sharing details. Choose redacted audit output when the audience does not need personal identifiers, and keep unredacted exports with your migration records under your normal access controls.

Continue with the next relevant guide.

Need help with your project?

Send the exact error and your project, batch, or run reference so we can investigate.

Get support