A clean dry run, then thousands of draw.io failures
What you are seeing
The dry run reported clean, but the real migration produced thousands of draw.io failures.
#Why it happens
Verification does not exercise the real conversion for draw.io. It substitutes a stand-in drawing rather than downloading the actual file, so the content check that decides success or failure in a real run never executes during a dry run. This is not theoretical, one production run followed three clean dry runs and produced over eighteen thousand failures.
#What to do
Treat a dry run as proof that macros are found and pages can be rewritten, not as proof that diagrams will convert. Pilot on a small, representative space with a real migration before committing to a site-wide run, and keep the vendor app installed until you have checked the result.
#Related
Found it? Good. Next.
