WP All Export Pro is the outbound half of the WP All Import ecosystem — the tool that gets data out of WordPress properly. Product catalogs export to XML and CSV for marketplace feeds and price comparison engines; orders export for accounting; users export for CRM imports; any post type exports with every field — custom fields, taxonomies, ACF values, images — through a drag-and-drop column builder that mirrors its sibling import plugin’s philosophy. Related reading: our import companion overview covers the adjacent workflow.
The Pro edition is where the data plumbing turns professional: scheduled exports of new or changed records, real-time exports triggered by events, WP-CLI automation, and a Function Editor for transforming values in-flight. Together with WP All Import Pro, it closes the loop — data out to wherever it needs to go, processed or enriched, and back in. For WooCommerce stores feeding marketplaces, accountants needing monthly order files, or agencies migrating content between systems, this is the export layer that does not need a developer on standby.
Competitive Features
Drag-and-drop column builder. Every field — native, custom, ACF, taxonomy, image URLs — drags into the export file with live previews of actual data rows.
Scheduled and real-time exports. Exports run on cron schedules (new/changed records only) or trigger in real time on events like Gravity Forms submissions.
WooCommerce-aware exports. Orders, products, refunds, and customers export with e-commerce structure — line items, taxes, metadata — not flattened posts.
Function Editor. PHP transformations run on exported values in-flight — currency conversion, concatenation, conditional formatting — without pre-processing the site.
Export bundles. Entire export configurations save as portable bundles, importable on other sites — the agency reusable-pipeline pattern.
Filter-driven exports. WP_Query-based filters select exactly which records export — by date, status, taxonomy, or any field logic.
Key Features
- CSV and XML output — with custom delimiters, BOM options, and element structures for downstream systems.
- ACF integration — repeater fields and complex ACF data export correctly.
- User export add-on support — including WooCommerce guest customers (added in 1.9.11).
- Empty-column removal — setting to strip empty CSV columns for clean files (1.9.2+).
- Internal order meta — filter-controlled inclusion of HPOS internal meta.
- WPCodeBox integration — Function Editor code sends directly to WPCodeBox (1.9.7).
- Corrupt-data resilience — improved handling of unexpected data during exports (1.9.12).
Comparison with Competitors
WP All Export Pro vs WP All Import Pro
Same developer, same interface philosophy, opposite data directions — designed as a pair.
| WP All Export Pro | WP All Import Pro | |
|---|---|---|
| Direction | WordPress → files | Files → WordPress |
| Typical job | Marketplace feeds, accounting exports | Supplier feeds, migrations in |
| Scheduling | Scheduled new/changed exports | Scheduled re-imports |
| Interface | Drag-and-drop columns | Drag-and-drop template |
| Best for | Getting data out | Getting data in |
Stores running supplier-driven catalogs realistically need both — the import side feeds the store, the export side feeds everything downstream.
WP All Export Pro vs Webtoffee Import Export for WooCommerce
Webtoffee’s plugin covers WooCommerce import/export in one package; the WP All Export route pairs a dedicated export engine with the import sibling.
| WP All Export Pro | Webtoffee Import/Export | |
|---|---|---|
| Scope | Dedicated export engine (all post types) | WooCommerce-focused suite |
| Filters | WP_Query-grade selection | Category/status level |
| Transformations | Function Editor in-flight | Basic mapping |
| ACF/custom types | Full support | Limited |
| Best for | Complex data pipelines | Simple Woo backups |
Complex pipelines favor the dedicated engine; simple Woo CSVs may suffice with the Webtoffee suite.
Recommended Stack: exported data feeds reporting and automation — pairing the export layer with a business management suite like WP-ERP Pro keeps CRM and HR data in the same self-hosted ecosystem the exports draw from.
Official Changelog
Version 1.9.15
Release Date: December 13, 2025
- Fixed: IE deprecation notice in WordPress 6.9
Version 1.9.14
Release Date: August 30, 2026 (distribution archives; vendor changelog lists as UI updates release)
- Improvement: UI updates
Version 1.9.13
Release Date: July 20, 2026
- Fixed: scheduling modal showing wrong license status
- Fixed: restored missing ACF field sanitize method
Frequently Asked Questions
Can it export WooCommerce orders with line items?
Yes — orders export with full e-commerce structure: line items, taxes, customer data, and metadata, rather than flattened post rows. Options control exporting orders once or on schedules for accounting workflows.
Does it handle ACF repeater fields?
Yes — ACF integration covers repeater and complex fields, and the 1.9.13 release specifically restored a missing ACF field sanitize method. Complex field data exports alongside standard custom fields.
Can exports run automatically on a schedule?
Yes — scheduled exports run on cron with new-or-changed-only filtering, and real-time exports trigger on events such as form submissions. The scheduling license-validation bug that affected some setups was fixed in 1.9.13.
Can I transform values during export?
Yes — the Function Editor runs PHP transformations on exported values in-flight (currency math, concatenation, conditionals), with code sendable to WPCodeBox for reuse. Validation guards against syntax errors breaking exports.
What formats does it output?
CSV and XML, with custom delimiters, BOM inclusion options, and XML element structuring for downstream systems — marketplace feeds, price engines, and ERP imports each get the shape they need.
How does it pair with the import plugin?
They are designed as a round trip: export bundles from this plugin import directly into WP All Import Pro on another site — the standard migration and staging-sync workflow between environments.




Leave a Reply