From WordPress (WP Travel Engine, Yatra, WP Travel)
A WordPress travel site keeps trips as posts with plugin fields, and there is no way to import them into TripNerve directly. Draft each trip with AI instead, pasting the itinerary and price from your WordPress page under What you already know, so the draft follows your route rather than one from the web.
If your plugin or a form plugin can export enquiries or customers as CSV, those go through the customer import. Before you switch the domain, list your old trip and blog addresses and add a redirect for each one that gets visits, so your search rankings follow you. The plugins, theme updates and hosting bills stop once the domain points at TripNerve.
From Tourtify, Tourmoo or another tour builder
Builders differ in what they let you export. Where you can download customers as CSV, import them; where you can't, start with the people who have upcoming trips. Trips are drafted with AI and checked against the old pages, departures are added a season at a time, and upcoming bookings are entered with New booking so they hold their seats.
If the old builder took online payments, note that TripNerve doesn't: travellers send a booking request, you confirm it, and you take payment by bank transfer or in the office. Keep the old account open until every booking taken there has been paid and travelled.
From spreadsheets and a WhatsApp group
If the business runs on an Excel sheet of departures and a customer list, the customer list imports directly: save it as CSV or paste the cells, with a header row naming each column. Tags and custom fields such as passport number or dietary needs can be filled from columns as they come in.
Departures are quicker to add again than to clean up: a season of Saturdays is one form. Enter seats already sold on each date, and from then on the seats left come from the bookings, not from a cell someone has to remember to update.

