Documentation
Everything the plugin does, and the exact limits of each promise. Start with the five-minute guide; come back to the field reference when a column will not map the way you expect.
Install
- Install and activate the plugin from Plugins → Add New, or upload the ZIP.
- Go to Importundo in the admin menu, or Tools → Import → CSV.
- Drop in a CSV file, check the column mapping, and look at the preview.
- Run the import.
If your file is larger than PHP's upload limit, upload it to wp-content/uploads by FTP and give the importer the server path instead. Nothing is copied, and a file you supplied that way is never deleted.
Requirements
| WordPress | 6.4 or newer, tested to 7.0 |
| PHP | 7.4 or newer |
| Database | Four tables are created on activation and removed on uninstall |
| Capability | Importing requires the ability to edit and publish the post type in question |
| WooCommerce | Optional. Product support appears only when WooCommerce is active; nothing from it is bundled or modified |
| Advanced Custom Fields | Optional. ACF fields appear on the mapping screen only when ACF is active. ACF Pro adds repeaters and galleries; nothing from either is bundled or modified |
| Outbound network | Only to download the image URLs in your own CSV, and only if you map an image column |
Where to go
The two rules everything else follows
The preview predicts the import. Any field the importer can write, the preview shows resolved exactly as it will be written — because the preview, the whole-file dry run and the importer's own has anything actually changed? check all ask the same object the same question. A feature that wrote something the preview did not show would have broken the product, not merely a feature.
Rollback is exact. Any table the importer can write, an import followed by its rollback leaves byte-identical to the state before, verified by table diff on every fixture in the test corpus. The one permitted exception is auto-increment counters, which MySQL does not rewind.