Who can request a custom migration or deduplication of their workspace?
👨👩👧👦 Supported on Enterprise Air plan
✏️ Anyone with admin access to the workspace in partnership with an Air Migration Specialist or Dedicated Customer Success Manager
When you partner with Air on an Enterprise custom migration or workspace deduplication project, you will receive detailed CSV reports summarizing the status of your files, metadata, and merge actions. These reports help you verify successful transfers, reconcile skipped files, and review planned deduplication steps before execution.
Whether you are migrating content from Google Drive, consolidating duplicate files from Adobe Creative Cloud, or running a large-scale workspace cleanup, these reports provide a transparent, audit-ready record of every asset's journey into Air.
Reading your import reports
During custom migrations and importer runs, the Air Enterprise Services team provides import reports to summarize the outcome of your data transfer. These reports contain several key columns to help you audit the migration:
Imported files: A list of all assets that successfully transferred into your Air workspace.
Skipped or failed files: Assets that could not be imported, complete with specific failure reasons.
Source metadata: If you are migrating content from Google Drive or other source systems, your custom migration can preserve metadata from Drive and Adobe suite. The report will show which tags migrate over and how Drive-specific metadata has been mapped to Air custom fields. For more on how metadata appears in the UI, see our guide on the Asset Info tab and metadata.
Failure reasons: Clear explanations for any files that failed to import. For example, zero-byte source files are explicitly reported with a
zero-sized-filefailure reason, ensuring you have a complete accounting of your source directory.
Understanding version-stack imports
If your source system contains versioned assets, Air can import these directly into version stacks to keep your workspace organized. Our custom migration reports help you reconcile versioned files at a high level, showing you which specific file versions successfully stacked and which ones failed. To learn more about how version stacks keep your creative iterations in one place, see our guide on managing version stacks.
Workspace deduplication vs. standard duplicate detection
It is important to distinguish Enterprise workspace deduplication projects from Air's standard, in-app duplicate detection. Standard duplicate detection operates strictly at the board level during manual uploads, checking for the same name and prompting you to stack the duplicate as a new version or upload it separately.
In contrast, Enterprise workspace deduplication projects are designed to resolve massive duplication errors across your entire workspace. This service helps you detect duplication across multiple boards and sub-boards, merge the boards, and consolidate duplicate items systematically.
Reviewing your deduplication plan output
Before executing a workspace-wide deduplication, the Air team provides a deduplication planning output as a CSV file. This allows your team to preview planned merge actions in the exact same format as the final execution results. You can review which assets are flagged as duplicates, which asset will be kept as the primary, and which assets will be merged or archived.
Resolving single-select custom-field conflicts
When duplicate assets are merged, they may have conflicting metadata. If duplicate assets disagree on a single-select custom field, Air resolves this conflict using a deterministic value during the merge process. To ensure you do not lose important context, Air surfaces any dropped values in a customFieldOverrides column in your report. This allows your team to review the discarded values and manually re-apply them in Air if necessary.
What to do with report findings
Once you receive your migration or deduplication report, we recommend taking the following steps to ensure a successful transition:
Review failure reasons: Scan the failure reason column in your import report to identify any systemic issues with your source files (such as corrupted files or
zero-sized-fileerrors).Identify source-file issues: Resolve any issues on your source storage system (e.g., re-exporting zero-byte files or fixing file permissions) before attempting a re-import.
Contact your Air team: Reach out to your Air Enterprise Success Manager or migration specialist to coordinate remediation, re-run specific imports, or adjust metadata mappings.
Now that you know how to read your migration and deduplication reports, you can explore more about how custom migrations work in our Explore Custom Migrations guide.