Goal
Insert reviewed WordPress posts into an Upendo Blog Manager module without importing unsafe or conflicting rows.
Before you start
- Complete and review a fresh dry-run.
- Confirm the destination backup exists.
- Confirm you have Edit permission on the destination Blog Manager module, unless you are a superuser.
- Make sure the content owner has approved the publication choice.
Import a small batch
- On Dry-Run Review, confirm the Safe to import count.
- Set Next Safe Posts Limit to a number from 1 through 5.
- Select Import Next Safe Posts.
- Read the confirmation message. The server will run the safety checks again.
- Confirm the action.
- Wait for Import Result.
The server imports only rows still marked WouldInsert. It does not import prior imports, slug conflicts, pages, protected posts, needs-review rows, or rows without a valid destination author.
Import all safe rows in the current window
- Review every safe row and the warnings.
- Select Import All Safe New Posts.
- Read the confirmation message carefully.
- Confirm the action.
- Wait for Import Result.
This removes the five-post request limit, but it is still limited to the current candidate window. It is not an unlimited full-database import.
Choose draft or published status
For a review-first migration, clear Publish imported posts later before the dry-run. Imported posts will be Drafts. If the option is selected, the current implementation inserts posts with Published status. Review this setting carefully before confirming.
After the import
Review the counts for inserted, skipped, and failed rows. Check featured images, inline media, comments, authors, and destination links. Open the destination Blog Manager and review the posts. Run another dry-run before the next batch.