Goal
Find safe posts, conflicts, warnings, and media problems before any destination blog content is written.
Before you start
Build the inventory and correct blocking errors. A dry-run is read-only for Blog Manager content and website files, but it saves a nonblank source connection string in encrypted form.
Steps
- From Inventory Summary, select Continue To Dry-Run or Preview Dry-Run.
- Review the totals: Total Found, Candidates, Would Insert, Prior Imports, Slug Conflicts, Warnings, and Errors.
- Confirm that the screen says destination blog data will not be written and website files will not be created.
- Review Safe to import. These rows are planned as
WouldInsert.
- Review Prior imports skipped. These rows already have import tracking for the same source identity and destination scope.
- Review Slug conflicts. The importer does not overwrite or rename these posts automatically.
- Review Needs review. Protected posts and unresolved authors are examples of rows that are not safe to import.
- Use the item preview pages to inspect each title, slug, source link, destination link, author, categories, tags, images, comments, and warnings.
- Open View source or Preview destination only when the links are trusted.
- Read the issue table and fix errors before importing.
Review decisions
- Import only rows marked WouldInsert.
- Resolve author problems before importing.
- Change a destination slug only through the source or destination content plan; do not assume a repeated run will solve a conflict.
- Confirm that local images are available on the website server.
- Review shortcodes, embeds, and internal links because the importer warns about them but does not convert them.
What success means
You have a reviewed count of safe rows, understand the skipped rows, and have no blocking errors. Continue to a controlled import only after the content owner approves the result.