What this module does
The Wix to Blog Importer copies published Wix blog posts into an existing runsonUpendo Blog module. It reads the posts through the Wix API, converts the content for the destination blog, downloads supported images when requested, and reports the result for each post.
This is a migration tool, not a two-way connection. It does not keep Wix and runsonUpendo synchronized after the import.
Who should use it
The importer requires Edit permission on the importer module.
- Superusers: Can choose a destination portal and a blog module in that portal.
- Site administrators: Can run imports in the current portal when they have Edit permission.
- Upendo clients and staff: Can use the importer when the site owner has approved the source, destination, and import settings.
- General content editors: Should review the imported posts but should not run a production import unless the site owner grants permission.
- Website visitors: Never see this tool. They see only destination posts that staff publish.
Before you begin
- Back up the destination database and portal files.
- Confirm that the destination runsonUpendo Blog module exists in the target portal.
- Ask the Wix site owner or Wix administrator for an API key.
- Confirm that the API key can read blog posts and rich content.
- Decide whether posts should be imported as published or as drafts.
- Decide whether images, comments, and search/social metadata should be copied.
- Test the import with a small number of posts first.
The import workflow
1. Choose the destination
Superusers can select the Destination Portal. Other users are limited to the current portal.
Choose the Destination Blog Module. The selected module must belong to the selected portal.
2. Enter Wix access details
Enter the Wix API Key. The key is used for the import request and is not saved by the module. Enter the optional Wix Site ID when your Wix API key or site setup requires it. Using the site ID is recommended when you have one.
3. Set the import size and content defaults
Set Maximum Posts. The default is 100 and the maximum is 500. Posts are requested from oldest to newest by first published date, which helps preserve the original publishing order.
Enter a Publisher Name and Default Author Name when the destination needs a clear author label. These values help identify imported content when Wix author details are incomplete.
4. Choose import options
- Download Wix images locally: Copies supported Wix images into the destination file system and changes eligible content links to local files.
- Publish imported posts: Creates posts as published when selected. Clear it for a review-first migration so staff can check drafts.
- Enable comments: Enables comments when Wix does not provide a post-specific commenting value.
- Add Open Graph tags: Adds supported social-sharing information to the imported page data.
- Add Twitter Card tags: Adds supported Twitter/X card information.
- Add BlogPosting JSON-LD: Adds structured data for search engines.
The importer does not write title tags, meta descriptions, meta keywords, canonical tags, og:url, or twitter:url into page-header data. Review and configure those items separately in the destination site.
5. Run the import
Select Import Blog Posts. The importer reads the selected Wix posts and processes them one at a time. Do not refresh or close the page while the import is running.
What is copied
- Post title, excerpt or summary, rich content, and plain text content.
- Original publish and update dates when Wix provides them.
- Categories and tags.
- Featured status when Wix provides it.
- Comments setting.
- A destination slug based on the Wix slug or title.
- Selected SEO and social values as allowed by the import options.
- A local hero image and inline images when image download is enabled and the files can be reached.
Slugs and repeated imports
If the planned slug already exists in the destination blog module, the importer adds a time-based suffix instead of replacing the existing post. It does not update an older imported post automatically. Repeated imports can therefore create another post with a different slug. Review the result and keep a migration record before running the same source again.
Import results
The results screen shows:
- total posts found;
- imported posts;
- skipped posts;
- errors;
- a row for each Wix post with its title, destination slug, message, and destination record ID.
An imported post can still have a warning, especially when an image could not be downloaded. Read every warning before publishing.
Safety and recovery
- Keep the Wix API key private, even though this module does not save it.
- Do not publish imported posts until the content owner reviews them.
- A partial import can leave earlier posts in the destination when a later post fails.
- Image downloads and database writes may not fail in the same way. Check both content and files after an error.
- There is no one-click undo for the whole import. Use the backup and the destination blog's normal delete or unpublish process.
- Check links, embeds, shortcodes, formatting, categories, tags, authors, images, and search metadata before publication.
What visitors will experience
Visitors do not see the import process. They see the imported posts only after staff make them public. If posts are imported as drafts, visitors see nothing until publication. If posts are imported as published, visitors may see them immediately, so use that option only after approval.