JageJobs Trip CSV Importer helps administrators manage trip content in WP Travel Engine using CSV files. It is an independent plugin and is not affiliated with or endorsed by WP Travel Engine.
Choose the workflow that matches your task:
- Import New Trips: upload a CSV, map its columns to supported fields, and create trips as drafts.
- Update Existing Trips: identify existing trips by Trip ID and update only fields mapped from the CSV. Blank cells and columns omitted from the CSV are left unchanged. Unknown or invalid trip IDs are skipped rather than imported as new trips.
- Export Trips: enter 1–25 existing trip IDs and select which supported fields to export. The CSV includes Trip ID and can be edited and reused with Update Existing Trips.
Supported fields include:
- Trip ID and Trip Title
- Duration
- Overview
- Itinerary
- Includes and Excludes
- Existing custom editor tabs, selected by their numeric tab number
The exporter preserves the stored HTML in supported content fields so headings, paragraphs, lists, and tables can be carried through an export/edit/import workflow. The plugin exports the content currently stored by WP Travel Engine; it does not recreate HTML that is absent from the stored value.
CSV column headers can be mapped to supported fields during import. Extra columns can be ignored. Custom tabs use the numeric tab number associated with the existing WP Travel Engine editor tab.
This plugin does not calculate prices, apply pricing formulas, convert currencies, import images, read DOC/PDF files, or assign trip categories. It is intended for content fields only.
Sample CSV files
Download the sample files to see the expected structure. Each file contains the same five fictional trips and dummy IDs.
- Sample for importing new trips — do not map the dummy Trip ID column when creating new trips.
- Sample for updating existing trips — replace every DEMO ID with a real Trip ID from your website before updating.
- Sample export-format CSV — illustrative example of the export column structure and HTML content; it is not data exported from your website. Replace dummy IDs before re-importing it as an update.
Back up your site and test on staging before bulk updates. Rows with IDs that do not match existing trips are skipped, not created as new trips.