The report

When a migration finishes, the Report step opens by itself. It is also saved as an HTML file you can keep, share or attach to a support ticket.

In the app

• A badge: n succeeded · n failed.
• Summary — source and target versions, when it started and finished, total size, how many plugins were skipped and how many warnings there were.
• open report in browser, with the path of the saved HTML file beside it.
• A section for each kind of action that ran (merge_tree, copy_tree, patch_prefs, merge_layout, symlink_dir and so on), and one for everything skipped, each with its note.
• Failures, if any action failed, with the reason.
• Warnings carried over from the Preview.
• something look wrong? — restore snapshot and factory reset.
• changed your mind? — revert migration.
• continue to cleanup, for the optional Cleanup step.

The undo buttons are explained in Safety & undo.

The HTML file

The file is written into the new version’s settings folder, named migration-report-<date and time>.html. It is self-contained — no internet needed to open it — and has these sections:

Section	What it lists
Summary	Started, finished, elapsed time, total size, files planned, actions succeeded and failed, plugins skipped, warnings.
Copied	Everything copied, merged, repointed or layout-merged, by item, with source, destination, size and file count.
Symlinked	The command-line and Team Render links made, and what each points at.
Plugins skipped	Each plugin left behind, its classification (cpp_only, mixed…) and why. This is your reinstall list.
External plugin folders	Each folder found in plugins.json, where it was cloned to, and how many plugins were carried and filtered out.
Config rewrites	The new plugins.json, and what was repointed.
Warnings	Every warning, and every failed action with its reason.

Paths in the HTML report are shortened to their last few folders; the in-app report shows them in full.

Finding it again

Open the new version’s settings folder — in Cinema 4D, Preferences ▸ Open Preferences Folder… — and look for migration-report-…html. Every migration writes its own report, so earlier ones are kept.

When you contact support, attach the report: it records exactly what happened.