Skip to main content

​
Overview

The Data Importer allows you to upload CSV files and bulk-import leads into a database source. It supports column mapping, duplicate detection, fuzzy matching for near-duplicates, and step-by-step progress tracking — making it straightforward to bring large datasets into Pingtree without manual data entry.
Video Walkthrough: A step-by-step video guide for this feature is coming soon.
Data importer CSV upload and field mapping interface

​
Before You Start

Make sure your CSV file is ready before beginning the import:
  • File format: .csv (comma-separated values).
  • Encoding: UTF-8.
  • The first row must be a header row with column names.
  • Phone numbers should include only digits (no dashes, parentheses, or spaces).
  • Date fields should use a consistent format throughout the file (e.g., MM/DD/YYYY).
Tip: Start with a small test file of 10–20 rows before importing a full dataset. This lets you validate your column mapping and catch data issues early.

​
Step 1: Upload Your CSV File

  1. Navigate to the Data Importer tab within your database source.
  2. Click Upload CSV File.
  3. Select your file from your local machine (or drag and drop it into the upload zone).
  4. The system reads the file and extracts the column headers for mapping.
Once uploaded, the file moves to the Column Mapping step automatically.

​
Step 2: Map CSV Columns to Pingtree Fields

In this step, you align each column in your CSV file with the corresponding Pingtree field. The mapping interface shows:
ColumnDescription
CSV ColumnThe header name from your uploaded file.
Sample ValuesA preview of the first few values from that column to help confirm you are mapping the right field.
Pingtree FieldA dropdown to select which Pingtree system or custom field this column maps to.
Rules for mapping:
  • Every column must be mapped to a Pingtree field, or explicitly marked as Ignore to skip it.
  • Required fields (as configured on the source) must be mapped before the import can proceed.
  • Custom fields you have defined on the source will appear in the Pingtree Field dropdown alongside system fields.
Tip: If your CSV uses field names that match Pingtree’s field keys exactly (e.g., email, phone, first_name), the system will auto-suggest the correct mapping. Always review auto-suggestions before proceeding.

​
Step 3: Review Mapping and Start Import

Before the import begins, review a summary of your mapping:
Summary ItemDescription
Total RowsNumber of data rows detected in the CSV (excluding the header).
Mapped FieldsList of all CSV columns and their assigned Pingtree fields.
Ignored ColumnsColumns that will be skipped.
Required FieldsConfirmation that all required fields have been mapped.
Once satisfied:
  1. Click Start Import.
  2. The system queues the import job and begins processing rows.

​
How Leads Are Processed

For each row in the CSV, the importer:
  1. Validates the row against required fields and data type rules.
  2. Checks for exact duplicates using the source’s configured duplicate field (e.g., email or phone).
  3. Checks for fuzzy matches — near-duplicate leads that are similar but not identical to existing records.
  4. Creates or updates the lead record based on the outcome:
OutcomeDescription
New Lead CreatedNo match found — the row is added as a new lead.
Exact DuplicateA lead with the same duplicate field value already exists — the row is skipped.
Fuzzy MatchA similar lead was found — held for manual review before being merged or rejected.
Validation FailedThe row is missing required fields or has invalid data — logged as a failed row.

​
Fuzzy Matching During Import

Fuzzy matching identifies leads that are similar to existing records but not exact matches. The system compares key identifiers (name, email, phone) using similarity scoring. When a fuzzy match is detected, the lead is held in a pending state and appears in the Fuzzy Matches queue within the Imported Data view. For each fuzzy match, you can:
  • Merge: Combine the incoming data with the existing record.
  • Create New: Add the incoming lead as a separate record.
  • Reject: Discard the incoming lead.
Tip: Resolve fuzzy matches soon after an import completes. Unresolved fuzzy matches are not counted in the source’s total lead count until you take action.

​
Tracking Import Progress

After starting the import, you can monitor its progress from the Imported Data tab:
StatisticDescription
ProcessedNumber of rows completed so far.
New LeadsRows that resulted in new lead records.
MatchedRows that matched and updated existing records.
Fuzzy MatchesRows held for review.
DuplicatesRows skipped due to exact duplicate detection.
FailedRows that could not be processed.
A progress bar updates in real time as rows are processed.

​
Handling Failed Rows

Rows that fail validation are logged with a reason code. After the import completes:
  1. Go to Imported Data and open the import file.
  2. Click Download Failed Rows to get a CSV of only the rows that errored.
  3. The file includes an error_reason column describing why each row failed.
  4. Fix the issues in your data.
  5. Re-upload the corrected file as a new import.
Common failure reasons:
ReasonFix
Missing required fieldEnsure the column exists in the CSV and is mapped correctly.
Invalid email formatValidate and clean email addresses before upload.
Invalid phone formatStrip non-numeric characters from phone numbers.
Invalid date formatStandardize date values to the expected format.

​
Re-Importing Data

You can re-import a file at any time by uploading it again through the Data Importer. The duplicate detection settings of the source will apply, so exact duplicates from a previous import will be skipped automatically. Use re-imports to:
  • Load corrected rows after fixing validation errors.
  • Refresh data for records that have changed since the original upload.
  • Top up a source with new leads added to the same list.