Skip to content

Data Import

Import writes data into WordPress destinations (posts, CPTs, products, and custom fields).

  • File: Upload JSON, CSV, or spreadsheet-style data.
  • AI: Paste unstructured text, extract records, then map/import.
  • Driver: Read from an existing WordPress driver source.

The node mapping view with source file fields on the left connected to WordPress target fields on the right

  1. Open WordPress Admin Sidebar > UMIE.
  2. In Input Source, choose File or AI.
  3. In Destination, choose WordPress.
  4. Select Destination Driver (for example Native, ACF, JetEngine, MetaBox, WooCommerce).
  5. Select Destination Target (post type, product type, CCT, or another target supported by that driver).
  6. Map fields in Node View or Table View.
  7. (Optional) If a multilingual plugin is active, select a Destination Language to assign to all imported posts.
  8. Run Start Import.

The table view showing source and target field mappings in a spreadsheet layout

For any import to WordPress, you must configure both:

  • Destination Driver: where UMIE writes data.
  • Destination Target: what structure/object type UMIE writes into.

Examples:

  • Native + post (blog posts)
  • WooCommerce + product
  • JetEngine + a specific CPT/CCT target

If you select:

  • Input Source: Driver
  • Destination: WordPress

UMIE automatically treats this as either:

  • Update (same driver + same target), or
  • Migration (different source and destination)

See:

UMIE also supports document/file assignment through a virtual source workflow.

  1. In Virtual Sources, click Upload Documents.
  2. Upload files/folders/ZIPs.
  3. Match files to records.
  4. Review assignments in Preview.
  5. Distribute files to destination file/media fields.

See:

  • File or AI input + WordPress destination => Import
  • Driver input + WordPress destination => Update or Migration
  • Driver input + File destination => Export
  • Any input + Cloud destination => Cloud Push (Pro)
  • Use Data Preview to verify rows before running import.
  • If you use AI Rewrite, run preprocessing before final import/update.
  • For large jobs, the process continues in background workers.