Documentation Knowledgebase

This area helps us show you how to use our features to grow your business.

WordPress to Blog Importer

Handle WordPress Import Problems

Understand inserted, skipped, and failed rows in a WordPress import, including prior imports, slug conflicts, needs-review rows, media limits, and comment or view warnings, and follow safe recovery steps that start with a fresh dry-run.

Updated

Goal

Understand skipped and failed rows and choose a safe next action.

Read the result first

On Import Result, review:

  • Inserted: destination posts created;
  • Skipped: rows rejected by the safety checks or already handled;
  • Failed: rows that could not finish;
  • featured-image counts;
  • inline-media counts;
  • imported and non-public comment counts;
  • view totals detected or skipped;
  • the row message and issue table.

Understand common statuses

Prior import skipped

The importer found tracking for the same source post, source-site identity, destination portal, and destination module. It points to a non-deleted destination post. The importer will not create a duplicate.

Slug conflict

The planned slug already exists on a non-deleted post in the destination portal. The importer does not overwrite the existing post or rename the new one automatically. Resolve the slug through the approved content migration plan, then run a fresh preview.

Needs review

The row has a condition that prevents automatic import, such as a protected source post or an author that cannot be resolved to an approved destination user. Correct the source or destination setup, then preview again.

Media skipped or failed

Only eligible local files are copied in the normal WordPress workflow. Supported types are PNG, JPG/JPEG, GIF, and WebP. Files must be nonempty and no larger than 5 MB. Remote-only images are not downloaded. A post may still be inserted without a missing image, so review the post after import.

Comment or view warning

Comments can be imported, but non-public comments remain unapproved or deleted. WordPress view totals are detected, not normally converted into historical daily views.

Safe recovery steps

  1. Keep the import result and record the affected source post IDs.
  2. Check the exact row message and recommended action.
  3. Correct the connection, author, table, path, slug, or source data problem.
  4. Confirm the destination backup and file backup are still available.
  5. Run a fresh dry-run. Do not rely on an old preview.
  6. Import a small test batch first.
  7. Review the destination before continuing.

Do not do these things

  • Do not delete import tracking records just to force a retry.
  • Do not assume uninstalling the importer rolls back imported posts or files.
  • Do not assume a failed request removed files created before the failure.
  • Do not repeat the same five-post request without increasing the Maximum Items window; candidates are limited before old imports are filtered out.
Topics: