About this block

Import Dry Run Preview sells the rehearsal instead of the leap, a split section where the left column explains that the importer can run against a scratch workspace first, and the right column shows the report that run produces, counts per data type, statuses that admit what needs review, and the estimated live run time. The report panel is the argument, a buyer who can see 3 need review next to 212 templates stops imagining worse numbers.

Copy points and report rows are two small arrays, and the flagged boolean flips a row badge from muted to primary. No client code.

When to use

Reach for this block on migration pages early, right after the hero, for the evaluator who wants proof the switch is testable before it is real. It also works on comparison pages as the answer to but what if the import breaks.

A natural flow around it on a Marketing Pro page:

Before

• Switch hero making the afternoon claim this block backs up

After

• Import coverage detailing what the run carries per source
• Migration timeline showing the live run hour by hour

What you can display

One strong use is the importer dry run with its report. Other rehearsal panels:

• Sandbox environments. A trial workspace report with seeded objects and limits.
• Audit previews. What a security or SEO scan found, before the paid fix.
• Billing simulations. A projected first invoice from real usage, before switching plans.

Tip: keep at least one flagged row in the report. A rehearsal that finds nothing reads like it was not really run.