Goal
Prepare the importer with the correct source database, destination blog, file paths, and safety settings.
Who can do this
You need Edit permission on the importer module. A superuser may choose another portal. Other staff members can use only the current portal.
Before you start
- Restore the WordPress database where the website server can reach it.
- Create or confirm an Upendo Blog Manager module in the destination portal.
- Back up the destination database and portal files.
- If images are needed, confirm the website server can read the source
wp-content/uploads folder.
Steps
- Open the WordPress To Blog Importer page.
- If you are a superuser, choose the Destination Portal.
- Choose the Destination Blog Module.
- Enter the WordPress Backup Connection String. Use a private connection string. Do not put it in screenshots or documentation.
- Set Source Database Type to MySQL / MariaDB. The SQL Server choices are disabled in the current screen.
- Enter the exact Source Table Prefix, such as
wp_.
- Enter the public Source Site URL.
- Enter the optional Source Blog Path if the source uses one, such as
blog.
- Enter the full server-side Uploads Root Path. Select the uploads folder itself, not
2018\02 or another child folder.
- Enter the optional Destination Blog Base URL for review links.
- Set Maximum Items. Use a smaller value for a first test. The default is 250 and the maximum is 1,000.
- Enter an existing approved Default Author User ID, if needed.
- Leave Include posts selected for a normal migration. Pages are preview-only and are not imported.
- Leave Publish imported posts later clear for a review-first migration. When selected, the importer creates Published posts.
- Select Build Inventory.
Check your result
The Inventory Summary should show source counts and destination readiness. If it reports missing tables, a bad connection, or an invalid uploads path, correct the setup before running a dry-run.
Safety notes
Each workflow action saves a nonblank connection string in encrypted form in the destination portal setting. Clearing the field does not clear the saved setting. Limit access to the importer page and use read-only source credentials when possible.