# Migration database report
The Report button generates an Excel summary of the migration database. Available on every connector tab that uses delta tracking (FileSystem, Box, iManageWeb).
Not used by every connector
iManage and OpenText use their own customized report instead of this shared one, so it can group by the target client/matter the same way their Import step resolves it. Their own documentation describes their report's sheets.
# How to run
- Select the migration database from the Database dropdown
- Click Report
- Confirm the prompt — the report runs against the selected database
- The report is saved to
Migrate\Report_{timestamp}.xlsxin the Epona.Migrate application directory
# Report contents
The Excel file contains four sheets:
| Sheet | Contents |
|---|---|
| Summary | Totals: unique sources migrated (with and without errors), unique documents migrated, total document versions, unique document errors, total version errors |
| MigrateSource Totals | Per migration source: document count, version count, version errors, and an Errors flag column for filtering. Auto-filter enabled |
| Unique Errors | Distinct error messages grouped with occurrence count, ordered by frequency |
| File Errors | All rows from _EDMSDocument where an error was recorded — full row dump including source key, target location, and error message |
# Identifying matters that need reprocessing
Use the report to find which source locations still have failed documents:
- Open the MigrateSource Totals sheet — filter the
Errorscolumn toTRUEto list every migration source (matter/folder) that has at least one failed version - Open the File Errors sheet for the full list of failed files — the
Sourcekey,TargetDocLib, andErrorcolumns identify exactly what failed and where - Use the Unique Errors sheet to triage: if the same error message appears hundreds of times it likely indicates a systematic problem (permissions, blocked file type, network) rather than individual file issues
Once the root cause is resolved, re-run the import. The delta tracking skip logic skips successfully migrated documents — only documents with errors (or new/modified files) are retried.
# Related
- FileSystem connector — imports documents from a filesystem
- Azure migration jobs and monitor — monitor window and retry workflow