WP Import Export Lite

WP Import Export Lite is a WordPress data-movement plugin for importing and exporting posts, pages, custom post types, taxonomies, comments, users, and related data across several file formats. It supports background processing, pause and resume controls, field mapping, filters, process logs, and an add-on system for WooCommerce, ACF, multilingual plugins, cloud storage, and scheduled jobs.

More file formats than a basic CSV importer

The plugin supports CSV, XLS, XLSX, JSON, TXT, ODS, and XML for import and export, plus ZIP archives. That makes it useful when data arrives from spreadsheet software or another business system that does not produce the same format every time.

Field mapping lets you connect source data to WordPress fields, while import filters control which source rows are processed. Export filters do the reverse by limiting which WordPress records are included in an output file.

Background jobs, pause, resume, and logs

Large imports can run in the background rather than requiring one long browser request. The workflow supports pause, resume, and stop controls, and multiple jobs can be managed separately.

Process logs record import activity at the record level. This is useful when a large feed finishes with a small number of skipped or failed rows because you can investigate those records without rerunning the entire import blindly.

Free core and paid extensions

The free plugin supports normal WordPress import/export workflows and a broad set of file formats. The ecosystem extends that foundation with ACF, WooCommerce, WPML, Polylang, attributes, scheduling, and remote-storage sources.

Pro features include scheduled imports and exports plus integrations with Google Drive, Microsoft OneDrive, Dropbox, FTP/SFTP, WooCommerce, and other data sources depending on the current plan and extension set.

Current subscription model

Pricing checked: September 26, 2026. The current vendor site lists a 2-site plan at $9.99 per month, 10 sites at $29.99 per month, and 100 sites at $99.99 per month. New users are currently offered one month of access to premium features before choosing a paid plan.

This subscription model is different from lifetime import products and from unlimited-site annual licenses. Agencies should compare site count, scheduling needs, and cloud-source integrations instead of looking only at the entry price.

Who WP Import Export Lite fits

I would consider WP Import Export Lite for sites that need to move data in both directions and regularly work with Excel, JSON, XML, or ODS in addition to CSV. Background processing and pause/resume controls are also valuable when imports contain thousands of records.

It can also suit agencies that want a single import/export interface across posts, users, taxonomies, custom types, and plugin-specific extensions rather than using a different utility for each content type.

Trade-offs to consider

The extension model means the exact workflow depends on which add-ons and paid features are active. Before migrating from another importer, list the custom fields, ecommerce data, languages, cloud sources, and schedules you rely on and verify each one individually.

Large background jobs still need adequate hosting resources. Pause and resume controls help operationally, but field mapping, unique keys, update behavior, and database backups remain the main safeguards against duplicate or overwritten data.

Migration and repeat-import checks

Run a small sample before a production import and then run the same sample again with changed values. The second run shows whether matching and updates behave as expected. Save the mapping, filter, source file, and job log so the workflow can be reproduced later.

For scheduled feeds, monitor the first unattended runs. A job that works manually can still fail when remote credentials expire, a source file changes columns, or a cron schedule runs into hosting limits.

When the same dataset is both exported and re-imported, verify field names and data types before treating the file as a round-trip format. Dates, serialized values, taxonomies, relationships, and plugin-specific metadata may need different mappings on the return import. A small round-trip test is safer than assuming an exported spreadsheet can be imported unchanged into another site.

Document successful mappings for future maintenance.

Content synchronization is different from a one-time migration

WP Import Export Lite can be used for simple migrations, but its paid synchronization features are more relevant when two systems exchange data repeatedly. In that scenario, define which site is authoritative for each field, how records are matched, and whether deletions in the source should affect the destination. Without those rules, a scheduled sync can undo editorial changes or create duplicates even when the file mapping itself is correct.

For multi-site workflows, test both directions separately. An export that looks complete in a spreadsheet is not automatically a safe re-import file because serialized values, relationships, taxonomies, dates, and plugin-specific metadata may need different handling on the destination site.

Operational checks for background imports

Background processing makes large jobs easier to manage, but it does not remove hosting limits. Watch memory, execution time, remote-file availability, and cron behavior during the first scheduled runs. If a job stops, use the process log to identify the failing record or remote dependency before restarting the entire import.

Keep a known-good export and a database backup before changing mappings or add-ons. That gives you a reference point if a new plugin version, source format, or cloud credential changes the behavior of an established import workflow.

Frequently Asked Questions