Run an import

1. 1Open Import from the sidebar.
2. 2Upload the file. Drag and drop a CSV or Excel file here, or click to choose it. Accepted formats: .csv, .xls, .xlsx
3. 3Press Analyze File. DealJourney reads the columns and proposes a mapping.
4. 4Choose the kind of record you are importing.
5. 5Check the Mapping column by column. See "Match your columns to fields".
6. 6Decide what should happen to rows that match a record you already have. See "Avoid creating duplicates".
7. 7Continue to validation, review what it reports, and run it.Prepare the file first. Three things account for most failed imports:

• • Make sure your file has a header row with column names
• • Use descriptive column names (e.g., "First Name" instead of "col1")
• • For dates, use formats like "2024-01-15" or "15/01/2024"

• Keep files under 5,000 rows for best performance A longer list is better split into several files, and splitting also means a mistake costs one batch rather than all of it.

Always run a small slice first. Take five rows into their own file, run the whole import, then open the records it created and look at them. Everything wrong with the mapping shows up in those five rows, and fixing it there costs nothing.

Resume a draft in the new import

The new import saves the source file and your mappings as a draft, including shared values and selected owners for bulk-created records. Choose Resume import on the reminder, or open Past imports and choose Resume. Your saved mappings are restored without automatically running the AI again. If reopening fails, the error appears on the screen where you started; the saved draft remains available to retry.

If the stored file has expired, select the original file again when prompted. The saved mappings are kept so you can continue where you left off.

See which rows failed

After an import finishes, Recent imports lists it with how many records were created, updated, skipped and how many failed. When the Errors number is above zero, click it to open Rows that could not be imported: one line per row that was not saved, with the row number from your file, the reason, and the company, name or email the row belonged to.

The most common reason is a contact row with no name. A contact needs a name to be saved, so a row that only names the company is left out. Add the name in your file, keep only the failed rows, and import that small file again.

A row that cannot be saved never stops the rest of the file. Before the import runs, the check screen names those rows and why each one cannot be imported, and they are counted as skipped in the result with the same reason on the row. Everything else in the file is imported as normal, so you only ever have to re-run the handful of rows you fixed.