Importing Clients, Leads & Suppliers from CSV

Switching from another CRM, or have a spreadsheet of supplier commission rates and contacts? JourneyFuse makes it easy to bulk import clients, leads, and suppliers from any CSV file. The import wizard automatically detects common column names, validates your data, and flags duplicates before anything is saved.

Starting an Import

1. Navigate to the Clients, Leads, or Suppliers page
2. Click the Import CSV button in the toolbar (next to "Add Client", "Add Lead", or "Add Supplier")
3. The import wizard opens with four steps: Upload, Map Columns, Review, and Confirm

Suppliers: export first to get a template. On the Suppliers page, click Export CSV to download your current suppliers with the exact column headers the importer expects. Even with no suppliers yet, the export gives you a header-only file to fill in. Edit that file and re-import to add new suppliers or bulk-update existing ones (suppliers are matched by name — see Handling Duplicates).

Step 1: Upload Your CSV

Drag and drop your CSV file onto the upload area, or click Choose File to browse. Requirements:

• File must be in .csv format
• Maximum 5,000 rows per import
• The first row must contain column headers

Step 2: Map Columns

JourneyFuse automatically matches your CSV columns to the correct fields using fuzzy matching. For example, "First Name", "fname", or "Given Name" all map to the first name field automatically.

If a column isn't matched correctly, use the dropdown to select the right field or choose Skip to exclude it from the import.

Supported Fields

For Clients: First Name, Last Name, Email, Phone, Address, Birthday, Anniversary, Passport Number, Passport Expiry, Known Traveler Number, Notes, Tags

For Leads: First Name, Last Name, Email, Phone, Destination, Travel Start Date, Travel End Date, Travel Type, Budget, Traveler Count, Source, Stage, Notes

For Suppliers: Name, Category, Commission Rate (%), Phone, Email, Website, Agent Portal URL, Booking Notes, and BDM details (BDM Name, Title, Email, Phone, Notes). Headers like "Commission", "Vendor", "Rep Name", or "BDM Email" are matched automatically.

Combined Name Columns

If your CSV has a single "Name" or "Full Name" column instead of separate first/last name columns, JourneyFuse will automatically split it. For example, "Mary Jane Watson" becomes First Name: "Mary Jane", Last Name: "Watson".

Tags (Clients only)

Want to carry your tags over from your old CRM? Add a Tags column and JourneyFuse turns each value into a real, filterable workspace tag. The importer auto-detects the column from any of these headers: Tags, Tag, Labels, Label, Groups, Group, or Categories.

To apply more than one tag to a client, separate the tags with a semicolon (;) — not a comma. Commas already separate columns in a CSV file, so a comma-separated list would break apart into the wrong columns.

First Name,Last Name,Email,Tags
Jane,Smith,jane@example.com,VIP; Disney; Repeat Client

That row tags Jane with three separate tags: VIP, Disney, and Repeat Client. Spaces around the semicolons are trimmed, and the same tag listed twice in one cell is only applied once.

On import, each tag is created in your workspace (if it doesn't already exist) and linked to the client — exactly like a tag you'd add by hand — so you can filter and segment by it right away. Re-running the import won't create duplicate tags.

Step 3: Review Data

Before importing, review all rows in a table with status indicators:

• Valid — Ready to import
• Warning — Minor issues (e.g., unparseable date) — the row will still import with the problematic field skipped
• Error — Missing a required field (first/last name for clients and leads, or name for suppliers) — these rows cannot be imported
• Duplicate — Matches an existing record (clients/leads by email or name, suppliers by name)

Handling Duplicates

For each duplicate row, you can choose:

• Skip — Don't import this row
• Import Anyway — Create a new record even though a match exists
• Update Existing — Merge the CSV data into the existing record

This is how you bulk-update suppliers: export your suppliers, edit the commission rates or BDM details in the file, re-import, and choose Update Existing for the matched rows.

Use the filter tabs at the top to quickly view just errors, duplicates, or warnings.

Step 4: Confirm & Import

Review the summary showing how many records will be created, updated, or skipped. For clients and leads you can optionally assign all imported records to a specific team member using the assignment dropdown (not shown for suppliers).

Click Import to complete the process. You'll see a confirmation toast with the results.

Tips

• Date formats — JourneyFuse accepts dates in most common formats: YYYY-MM-DD, MM/DD/YYYY, M/D/YYYY, and MM-DD-YYYY
• Budget values — Dollar signs and commas are automatically stripped (e.g., "$5,000" becomes 5000)
• Tags — Put multiple tags in one cell by separating them with a semicolon (e.g. VIP; Disney), not a comma
• Lead stages — Valid values are: new, contacted, proposal_sent, won, lost. Invalid stages default to "new"
• Export from your current CRM first — Most CRMs have a "Download as CSV" or "Export contacts" option in their settings

Importing clients in MyAtlas (Lite agents)

Agents on a MyAtlas (Lite) account have their own, simpler importer. Go to Contacts and click Import.

1. Upload a CSV — column names are matched automatically, same as the full importer. Maximum 2,000 rows per file.
2. Check your columns — before anything is saved you see every column in your file, a sample of its values, and where it is going. Anything we could not match shows as Skip; pick the right field from the dropdown to bring it in. If an obviously important column (an email or phone column, say) lands nowhere, a warning calls it out.
3. Choose whether to update — leave Update clients I already have checked to have matching rows update the client instead of being skipped. Matching is on email, or first and last name.
4. Import — the result shows how many were added, updated, and skipped, which columns were not imported, and any rows that could not be read.

If your file has two columns for the same thing — "Email" and "Contact Email", for example — the first one is used, and the second fills in only on rows where the first is blank.

Fixing an import that missed a column

Nothing is lost. Set the column correctly and upload the same file again with Update clients I already have checked: matching is by email, or by first and last name, so your existing clients are updated in place rather than duplicated. Only the columns in your file are touched.

Bulk-updating your client list

Use Download CSV on the same page to export your clients with the exact headers the importer reads. Edit the file in a spreadsheet, upload it back with Update clients I already have checked, and every matched client is updated at once. With no clients yet, the export gives you a blank template to fill in.

Only the columns present in your file are changed, so a file with just name and phone will not blank out addresses or birthdays you already have.

What a MyAtlas import can set

Prefix, first/middle/last name, suffix, email, phone, cell, address, apt/suite, city, state, zip, country, birthday, anniversary, client since, and notes. Tags, passport details, and marketing opt-in are not imported through MyAtlas. Anything else in your file is ignored.

Imports are scoped to you: they only ever match against, and update, your own clients, never another agent's.