Wp Import Laravel Package

Product Decisions This Supports

• Replatforming from WordPress to Statamic: this package is the migration path for content, posts, and now terms/taxonomies. It directly informs the "can we move off WordPress?" decision without building a bespoke importer.
• Build vs. buy for migration tooling: v1.7.2 continues to improve the shipped term/taxonomy importer rather than requiring custom ETL scripts — a strong argument for buying/adopting over building.
• Taxonomy-fidelity as a launch gate: the fix in this release targets term/taxonomy import accuracy, which affects category/tag pages, navigation, and SEO structure post-launch. Product should treat taxonomy integrity as an acceptance criterion in migration QA.
• Roadmap sequencing: because the importer is actively maintained (now with an additional contributor), iterative, phased migrations (content first, taxonomies next, redirects last) become viable rather than a single big-bang cutover.
• Use cases: blog/news archives, documentation sites, marketing content hubs, and multi-author editorial sites moving to a Laravel-based CMS.

When to Consider This Package

Consider adoption when:

• Your source system is WordPress and your target is Statamic (this is purpose-built, not a generic importer).
• You need to migrate posts, pages, and taxonomy terms with reasonable fidelity and want a maintained, community-backed tool rather than one-off scripts.
• Your team is comfortable operating a Laravel/Statamic stack and can run CLI-driven imports in a staging environment.
• You value incremental patch releases (v1.7.2 is a low-risk bug-fix/improvement release with no breaking changes) over large, infrequent upgrades.

Look elsewhere when:

• Your source CMS is not WordPress — this offers little value.
• You require enterprise-grade, fully deterministic migrations with formal SLAs; a community package (even an actively maintained one) may not satisfy procurement or compliance review.
• Your content model is heavily custom (custom post types with complex relational data, page builders, or ACF-heavy structures) — expect supplementary custom development regardless of this package.
• You need bidirectional sync; this is an importer, not an integration layer.

How to Pitch It (Stakeholders)

To executives: We can migrate off WordPress onto our Laravel-based CMS using a maintained, open-source importer instead of funding a bespoke migration project. The latest release (v1.7.2) is a small, low-risk patch that improves how categories and tags are carried over — exactly the kind of detail that protects SEO and site navigation after launch. No breaking changes; no action required beyond scheduling the upgrade.

To engineering: v1.7.2 updates term/taxonomy import and adds a new contributor, signalling healthy maintenance. It's a patch bump — safe to adopt in the normal upgrade cycle, ideally validated against a staging import of a representative content set, with taxonomy mapping and term hierarchy checked explicitly. Continue treating custom post types and field-mapping edge cases as out-of-scope work to be planned separately.

Recommendation: Adopt for WordPress→Statamic migrations; upgrade to v1.7.2 as a routine patch; hold taxonomy QA as a go/no-go gate for any migration milestone.