Documentation Knowledgebase

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

WordPress to Blog Importer

WordPress to Blog Importer

The WordPress to Blog Importer moves posts from a restored WordPress database into an Upendo Blog Manager module through Setup, Inventory Summary, Dry-Run Review, and Import Result steps. It is insert-only and has no whole-import undo.

Updated

What this module does

The WordPress to Blog Importer moves selected content from a restored WordPress database into an existing Upendo Blog Manager module. It helps staff review the source, find possible problems, test the import, and then import a controlled set of safe posts.

This is an insert-only migration tool. It does not update existing blog posts, synchronize two sites, restore a database, or provide a full undo action.

Who should use it

The importer requires Edit permission on the importer module. Importing also requires Edit permission on the selected destination Blog Manager module, unless the person is a superuser.

  • Superusers: Can choose a destination portal and work with a Blog Manager module in that portal.

  • Site administrators and approved staff: Work in the current portal. They need Edit permission on both modules for an import.

  • Content editors: Use the importer only when the site owner has granted the needed Edit permissions. A content editor should not run a production import without a reviewed backup and migration plan.

  • Regular site visitors: Do not use this module. They only see the posts that staff later publish in the destination blog.

Before you begin

  1. Back up the destination database and portal files together.

  2. Restore the WordPress database separately. This module does not upload or restore a backup.

  3. Install and configure Upendo Blog Manager, and create a destination Blog Manager module.

  4. Give the website server a connection that can read the restored source database. Read-only source credentials are preferred.

  5. If you want local WordPress images copied, make the server-side wp-content/uploads folder readable by the website application identity.

  6. Make sure the destination can create website files.

  7. Restrict the importer page to trusted staff. The connection string is saved encrypted in a portal setting when a workflow action runs.

Main workflow

The screen has four steps: Setup, Inventory Summary, Dry-Run Review, and Import Result.

1. Set up the source and destination

Choose the destination Blog Manager module. Superusers can first choose the destination portal.

Enter the connection string for the restored WordPress database. The selectable source type is MySQL / MariaDB. The SQL Server source choices are shown as disabled in the current interface and are not the normal operator workflow.

Complete the source fields:

FieldWhat to enterSource Table PrefixThe exact prefix on the WordPress tables, such as wp_. Do not assume the default is correct.Source Site URLThe public source site root, such as https://source.example.com. Keep it the same on later runs.Source Blog PathOptional path used to build source links, such as blog.Uploads Root PathThe full path on the server to the WordPress uploads folder. Use the uploads root, not a year or month folder.Destination Blog Base URLOptional public article root used for preview links, such as https://destination.example.com/blog.Maximum ItemsThe source read limit. It defaults to 250 and cannot exceed 1,000.Default Author User IDAn existing approved destination user used when the source author cannot be matched.

Select whether to include posts and pages in the preview. The import workflow imports WordPress posts, not pages. Select Publish imported posts later only when the migration has been approved for immediate publication. Despite its label, the current code inserts those posts with Published status; when it is not selected, posts are inserted as Draft.

2. Build the inventory

Select Build Inventory. This checks the source and destination and shows counts, warnings, required tables, and possible problems. Inventory counts are not the same as the number of posts that can be imported.

Fix errors before moving on. A warning may still allow a safe row, but an error can block the import.

3. Run and review the dry-run

Select Preview Dry-Run. Dry-run does not write Blog Manager content or create website files. It does save a nonblank connection string in encrypted form before the service runs. A blank field does not clear the saved connection string.

Review the totals and each item. The preview can show:

  • source title, slug, status, author, and source link;

  • planned destination slug and destination link;

  • category and tag mapping;

  • featured-image and inline-media status;

  • comments and detected source view totals;

  • warnings and errors.

Only rows marked WouldInsert are eligible for the controlled import. Rows may be skipped because they were imported before, because a slug already exists, or because they need review.

4. Import a controlled set

Select Import Next Safe Posts to import a small batch. The limit is 1 to 5 posts per request. The server runs the safety checks again before writing.

Use Import All Safe New Posts only after reviewing the preview. It imports all currently safe rows in the candidate window, without the five-post limit. It does not import conflicts, prior imports, pages, protected posts, needs-review rows, or rows without a valid destination author.

What is transferred

  • Post title, summary, HTML content, planned slug, publication date, author, and derived SEO fields.

  • Categories and tags. Missing terms may be created. This is not a category-hierarchy migration.

  • Existing destination authors are matched by source login, email, or display name. The module does not create user accounts.

  • Local featured and inline images in supported formats: PNG, JPG/JPEG, GIF, and WebP. Files must be nonempty and no larger than 5 MB.

  • Comments, including available names, email addresses, dates, and parent relationships. Comment text is limited to 2,000 characters.

Remote-only media is not downloaded. Source view totals are detected, but the normal WordPress workflow does not convert them into historical daily views.

Important limits and recovery

  • Existing posts are not updated or overwritten.

  • A slug conflict is not renamed automatically.

  • A failed image copy does not always stop a post from being inserted.

  • A request is not one large all-or-nothing transaction. Earlier successful rows remain if a later row fails.

  • File copies happen outside the database transaction. A failed run can leave an unused file.

  • There is no whole-import undo button. Use the backups and your site recovery plan.

  • Repeating a five-post import does not automatically move through the whole database. Candidates are read within the Maximum Items window. Increase that value, preview again, and continue in reviewed batches.

  • Shortcodes and embedded content are not converted for you. Review the rendered result before publishing.

After import

Use the result step to review inserted, skipped, and failed rows. Check media, authors, comments, and destination links. Open the destination Blog Manager and review drafts before publishing. Refresh the destination site because direct import writes may not immediately clear every blog cache.