WordPress Importer
WordPress Importer reads WXR exports so Capell can preview WordPress posts, pages, authors, taxonomy, and attachment references.
What WordPress Importer helps you do
This private package is outside the Released and Beta channels, so no public install path is available.
Workflow screenshots
6 capturesWordPress Importer reads WXR exports so Capell can preview WordPress posts, pages, authors, taxonomy, and attachment references.
Import previews make migration decisions easier before content is committed.
It pairs with Migration Assistant so WordPress content follows the same validate-and-report path as other sources.
Use it when WordPress content needs a safer route into Capell.
Review the documentation and screenshots on this page before enabling it on a production Capell site.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces WordPress Importer adds when enabled.
- Wordpress
- Wxr
- Migration Assistant
- Imports
Install after you have checked the fit.
Confirm version compatibility, support, data access, migrations, retained data, and removal steps first. Then install the Composer package from the account that owns access.
-
01
Require the package
composer require capell-app/wordpress-importer -
02
Register the extension
php artisan capell:extension:enable wordpress-importer -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in WordPress Importer
Switch the evaluation lens to see how different roles should assess this package before installing it.
One broken post did not sink the import — what to verify
Add one corrupt post to an otherwise valid WordPress export. The import should name and skip that item, continue with the rest, and create redirects for changed permalinks.
Read more Show less
Evidence to request: Re-running the same export is safe because posts are tracked by their WordPress identity, not their title, so nothing duplicates. And every old permalink maps to its new URL automatically, so existing inbound links and rankings continue resolving on launch day.
Alternative fit: Budget for an editorial pass once it is live, because the import gets teams most of the way, not all of it. Staying on WordPress can be the better call when the site is stable.
Release and download evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
0 releasesNo package release history is published yet. Check the source and documentation before installing.
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy hosts paid marketplace checkout and issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the licence, receipt, support history, and future install access. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.
No approved reviews yet. Reviews from eligible customers appear here after moderation.
