Importing & Exporting Leads

Leads go in and out as CSV — useful when you are moving from another system, or handing a list to someone who does not use CeremonySync.

Importing

The importer runs in steps: upload, map, preview, import.

1. Upload

Drop in a CSV. Three fields are required for a row to import:

• Name — at least two characters
• Email — a valid address
• Source — where the lead came from

Everything else is optional: phone, wedding date, guest count, budget min and max, notes, address and venue preference.

2. Map

CeremonySync reads your header row and maps what it recognizes — a column called "Name", "Full Name", "Email", "Email Address", "Phone", "Status", "Source", "Lead Source", "Wedding Date", "Event Date", "Guest Count", "Guests", "Budget Min", "Minimum Budget", "Budget Max", "Maximum Budget", "Notes", "Address" or "Venue Preference" lands in the right place on its own.

Anything it does not recognize is set to -- Skip This Column --, which you can change. Required fields are marked with an asterisk.

3. Preview

Validate & Preview checks every row and reports four counts: Total Rows, Valid, Invalid and Duplicate. Duplicates are matched on email against leads you already have.

Rows with problems say what is wrong, and can be corrected here rather than by going back to the spreadsheet.

4. Import

Valid rows become leads. Nothing you skipped is lost from your original file — it simply is not brought across.

Exporting

Export Leads to CSV exports the leads currently in view, so filter the page first if you want a subset.

Under Column Selection you choose what to include, with Select All and Deselect All. Fourteen columns are available:

Name · Email · Phone · Status · Source · Wedding Date · Guest Count · Budget Min · Budget Max · Score · Address · Venue Preference · Created Date · Tags

That is the whole set. There is no export of tour history, response times, follow-up dates or activity — if you need those, they stay in CeremonySync.

Export CSV downloads a timestamped file, leads-export- followed by the date and time.

Practical use

• Import in small batches the first time. A hundred rows with one mapping mistake is a bad afternoon; ten rows tells you the same thing.
• Set Source properly before importing rather than after. It is required, it feeds the score, and it is tedious to fix in bulk later.
• Export before any big change to your pipeline. It is the only backup of the list that you hold.

Frequently Asked Questions

What happens to a duplicate? It is flagged in the preview by matching email, so you can decide before importing.

Can I import and update existing leads? No. The importer creates leads.

Why was my row rejected? Almost always a missing source, an invalid email, or a name under two characters. The preview says which.

Does importing calculate scores? Scores are worked out from the data whenever they are shown, so an imported lead has one as soon as it lands — on the Complete plan.