Import WP

Import WP is a WordPress CSV and XML importer/exporter built around visual field mapping and flexible data sources. The free plugin handles core WordPress content, users, taxonomies, attachments, remote files, FTP, and Google Sheets, while Pro adds custom post types, custom fields, custom taxonomies, scheduling, premium support, and integrations such as ACF and JetEngine.

Flexible CSV and XML mapping

Import WP does not require a fixed file layout. You can map CSV columns or XML nodes to WordPress fields, choose how records should be matched, and decide whether an import may insert, update, or delete records.

For XML, the importer can work with different document structures and lets you define the base path that represents one record. This is useful when supplier feeds or legacy exports do not match WordPress field names cleanly.

Remote files, FTP, and Google Sheets

Files can come from a normal upload, a remote URL, an FTP server, an existing server path, or a published Google Sheets URL. Repeat imports can skip unchanged records, which helps when the same supplier or directory feed is processed regularly.

Images and attachments can also be fetched from remote URLs, FTP, local storage, or reused from the WordPress media library. Attachment metadata such as title, caption, alt text, and description can be mapped during the import.

Free import and export coverage

The free plugin imports posts, pages, categories, tags, users, and attachments. It also includes export to CSV, XML, or JSON with field selection, record filters, customizable headings, and nested XML support.

Free add-ons extend the workflow. The WooCommerce add-on can import and export products, variations, product images, categories, attributes, prices, and stock. Other add-ons cover SEO metadata and multilingual workflows.

What Pro adds

Import WP Pro adds custom post types, custom taxonomies, custom fields, scheduled imports, premium support, and access to premium add-ons such as ACF and JetEngine. This is the point where the plugin becomes more suitable for directories, custom application data, and recurring structured feeds.

Pricing checked: September 26, 2026. Import WP Pro is currently $49.99 per site per year. The license includes 12 months of updates and support.

Who Import WP fits

I would shortlist Import WP for site owners and developers who need a flexible CSV/XML mapper but do not necessarily need a large bundle of import add-ons on day one. The free version covers more core migration work than a simple built-in WordPress importer.

It is especially practical when feeds arrive from remote URLs, FTP, or Google Sheets and when records need to be updated repeatedly. The free WooCommerce add-on also makes it relevant for product data without immediately moving into a premium ecommerce package.

Trade-offs to consider

Custom post types, custom fields, and scheduling require Pro, so a site built heavily around ACF, JetEngine, or custom application data will reach the paid boundary quickly. The license is also per site, which differs from import tools that include unlimited installations.

As with any importer, test matching rules and update behavior on staging before running a recurring production feed. A wrong unique identifier or delete setting can change many records at once.

How to evaluate a recurring import before production

For one-off content moves, field mapping is the main task. Recurring feeds need more planning. Choose a stable unique identifier, decide which fields the importer is allowed to update, and define what should happen when a record disappears from the source. Those choices determine whether a second run safely updates existing content or creates duplicates.

Remote images deserve separate testing because source servers can rate-limit downloads or change file URLs. Run a small sample first, check attachment reuse and metadata, then test a second import with changed values. A repeatable import should produce predictable updates without duplicating posts, terms, users, or media.

For client work, keep the original source file and saved mapping together so a future administrator can reproduce the import without reverse-engineering the setup.

Unique identifiers and update safety

The most important decision in a repeat import is the field used to identify an existing record. A supplier SKU, external database ID, email address, or another stable source key is safer than a title that can change. Before automating the feed, run the same sample twice and confirm that the second pass updates the original records rather than creating duplicates.

Also define field ownership. A remote catalog may be authoritative for stock and price while WordPress editors own descriptions, SEO fields, images, or categories. Restrict the import to source-owned fields so a scheduled job cannot overwrite manual improvements that are not present in the feed.

Rollback planning for large imports

Import WP can update many records quickly, so take a database backup before first-run and structural changes. Keep the source file, mapping, unique-key choice, and update settings together with the project documentation. If a mapping changes later, that record explains exactly what the previous automation was expected to do.

Frequently Asked Questions