Import clients, leads, guides, and bookings
Bring your existing spreadsheet in — clients and leads, or full bookings with the payments already recorded against them.
You don't have to start empty. Import a spreadsheet of clients and leads to seed your CRM, or a full bookings import that carries clients, bookings, and the payments already made against them — the move for outfits switching off a spreadsheet mid-season.
Bookings import
Each row becomes a client, a booking, and its payment history — deposit and balance recorded exactly as your spreadsheet says, not regenerated from a payment schedule. No confirmation emails go out for hunts that already happened, and no payment schedule is invented on top of what you're importing.
Money amounts have to be unambiguous — plain digits with a period as the decimal point (3896.48, not 3.896). A figure the importer can't read with certainty is refused rather than guessed, so nothing gets billed for the wrong amount.
Re-running a file is safe
If an import fails partway through, fix the errors and upload the same file again. Rows that already succeeded are recognized and skipped — only what's missing or wrong gets written. A booking that landed with no payment rows because of an earlier hiccup gets its payments filled in on the re-run rather than being duplicated.
A row whose dates don't fall inside any existing season is an error with a message telling you why — nothing is auto-created to make it fit. A guide name that doesn't match anyone on your team is dropped with a note rather than failing the whole row; the booking and its money still import.
Bookings import is on the Solo, Pro, Business, and Elite plans. Bookings import requires an owner or admin.