Weave Code
Wp Import Laravel Package
statamic-rad-pack/wp-import
A Statamic addon from Rad Pack for importing WordPress content. Migrate posts, pages, media, categories, and tags through a guided importer, making it easier to move an existing WordPress site into Statamic without rebuilding content by hand.
Statamic WP Import can import simple content from your WP site.
Frequently asked questions about Wp Import
- How do I install statamic-rad-pack/wp-import?
- Install it with Composer using composer require statamic-rad-pack/wp-import. It is a conventional Laravel package: a service provider registers an import command and configuration, so once installed you run the guided importer from the console. Pin an explicit version such as 1.7.2 rather than a floating caret range so a mid-migration patch cannot change import behavior underneath an in-flight content transfer.
- What WordPress content can this addon import into Statamic?
- It imports simple content: posts, pages, custom post types, terms and taxonomies, and media. The importer maps WordPress entities onto Statamic's content model, so posts and pages become collection entries, WordPress taxonomies become Statamic taxonomies, and media lands in asset containers. It is aimed at moving an existing site across without rebuilding content by hand.
- Which Statamic, Laravel and PHP versions does this package support?
- The addon runs inside a Statamic application, so it inherits your host app's PHP and Laravel constraints rather than imposing its own. Check the declared support matrix in the package's composer.json against your pinned Statamic major, Laravel version and PHP runtime before committing. That is a five-minute check and the highest-value pre-adoption gate for this kind of addon.
- Is the WordPress import idempotent and safe to re-run?
- Re-run behavior is not clearly documented, so treat idempotency as something you must verify rather than assume. Run the importer twice against a staging copy of a representative export and watch how it handles existing terms with matching slugs, duplicate entries and repeated media. If a second run duplicates or flattens data, plan a single clean import plus rollback rather than iterative re-runs.
- What changed in version 1.7.2 of statamic-rad-pack/wp-import?
- Version 1.7.2 is a patch release containing a single commit, Update term/taxonomy import, merged from a first-time contributor. No breaking changes, deprecations or config signature changes were announced, and the change is scoped to how WordPress categories, tags and custom taxonomies map into Statamic taxonomies. The release note is not self-describing, so it does not say whether this is a bug fix, new edge-case handling, or altered default behavior for hierarchical terms.
- Does it import custom WordPress taxonomies and term meta?
- Core categories and tags are clearly in scope, but support for registered custom taxonomies and term meta is not documented in detail. Taxonomy import is the highest-fidelity-risk area of any WordPress to Statamic migration, since hierarchical versus flat terms, slug collisions and orphaned terms can go wrong quietly. Test with an export that includes a custom taxonomy and check parent relationships, term counts and slugs in the result.
- Should the importer stay installed in production after migration?
- No. This addon sits entirely at the migration boundary and is not a runtime dependency, so it delivers no ongoing product value once content is moved. Keep it scoped to a migration environment, verify the imported content, then remove the package. That keeps your production dependency surface small and avoids carrying an unmaintained build-time tool indefinitely.
- How do I verify a WordPress import was correct after upgrading the addon?
- Run a differential test: import the same representative WordPress export with the previous version and with the new one, then diff the resulting term and taxonomy structure. Compare term counts, hierarchy depth, slugs, parent relationships and associations to entries, plus asset and entry counts. If the outputs differ, confirm which output is correct before proceeding, and re-verify any migration you already completed.
- Does the importer migrate WordPress media into Statamic asset containers?
- Yes, media import into asset containers is part of the stated scope alongside posts, pages and taxonomies. Because it is a guided importer rather than a full sync tool, check how files are mapped to containers and whether existing assets are skipped or duplicated on a repeat run. Verify file counts and a sample of entry-to-asset references after the import completes.
- Is statamic-rad-pack/wp-import actively maintained?
- The project appears to be maintained by a small team at rad-pack with no visible LTS or formal support commitment. Version 1.7.2 is a patch-level release from a first-time contributor, which tells you little about release cadence or the open-issue backlog. Before relying on it, check the repository's recent activity, tested version matrix and issue history, and pin the exact version you validated.
Weaver
How can I help you explore Laravel packages today?