Troubleshooting

CSV Import & Data Hygiene: Required Fields, Mapping, and Deduplication

Learn how to properly structure CSV files, map fields, and apply deduplication to ensure clean imports, seamless enrichment, and accurate CRM syncing in Jeeva.

Gaurav Bhattacharya

CEO, Jeeva AI

Oct 23, 2025

CSV import is a critical step in running campaigns and enrichment with Jeeva.ai. Following the right format and maintaining clean data will help avoid upload failures and duplicates.

  1. CSV Requirements for Campaign Uploads

  • File must be in CSV format (Excel/XLSX files will not work).

  • Mandatory columns: First Name (or Full Name), Company Name, and Email Address.

  • File must be under 5MB and contain no more than 5,000 leads.

  • Ensure there are no blank rows, merged cells, or special characters in headers.

  1. CSV Requirements for Lead Enrichment

  • File must have less than 500 rows.

  • Proper headers are required (Full Name, Company Name, Company Website, LinkedIn URL, etc.).

  • After upload, map fields correctly so Jeeva can recognize them.

  • Add enrichment columns such as Email or Mobile and then run enrichment to fetch the data.

  1. Deduplication and Matching

  • Always set at least one matching criterion (Email for contacts, Website for companies).

  • Use Exact Match for critical fields to avoid mismatches.

  • Enable Waterfall Logic to improve matching accuracy.

  • After exporting, check logs for issues and resolve mis-mapped fields.

  1. Common Issues and Fixes

  • Upload fails: Confirm file is CSV, under size limit, and includes required headers.

  • Pagination mismatch: Remove blank rows or hidden formatting.

  • Mapping mistakes: Re-check field mappings before saving.

  • Records not syncing: Make sure unique identifiers (Email, Website) are included.

  • If fields are null or empty in your CSV, those values will not get exported.

  1. Best Practices

  • Clean CSV files before upload by removing duplicates and validating emails.

  • Keep column names consistent with Jeeva’s required fields.

  • Run enrichment in smaller batches (less than 500 leads) for accuracy.

  • Monitor export logs regularly.

  • Enable “Optimize for Enrichment” if you want to enrich records from your CRM.
    Summary: By preparing clean CSV files, mapping correctly, and enabling deduplication, you can ensure smooth data import and accurate campaign execution.

    HubSpot Mapping Gotchas and Mapping Mistakes
    When connecting Jeeva.ai with HubSpot, correct field mapping is crucial for ensuring accurate data sync. Mistakes in this step often cause failed exports, duplicate records, or missing information.

  1. Mandatory Field Mapping
    Contacts Object:

  • First Name → First Name

  • Last Name → Last Name

  • Company Name → Company Name

  • Website → Website URL

  • LinkedIn → LinkedIn URL

  • Work Email → Email

  • Jeeva ID → Create a custom field in your HubSpot contact object (e.g., “Jeeva ID”) and map it to the Jeeva ID field. This helps Jeeva track leads exported to your CRM.

Companies Object:

  • Company Name → Company Name

  • Website → Website URL

  • City/State/Country → City/State/Region

  1. Matching Criteria

  • For Contacts, use Email as the unique identifier (CRM Field = Email, Jeeva Field = Work Email, set as Exact Match).

  • For Companies, use Website/Domain as the unique identifier (CRM Field = Company Domain Name, Jeeva Field = Website, set as Exact Match).

  • Always enable Waterfall Logic to improve matching accuracy.

  1. Common Mapping Mistakes

  • Forgetting to map mandatory fields like Email (for contacts) or Website (for companies).

  • Mapping the wrong Jeeva field to HubSpot (e.g., mapping LinkedIn URL to Email).

  • Leaving fields unmapped, which prevents proper sync.

  • Using partial matches instead of Exact Match, causing duplicates.

  • If fields are null or empty in your data, they will not be exported to HubSpot.

  1. HubSpot-Specific Gotchas

  • HubSpot requires unique identifiers. If Email or Website fields are missing or incorrectly mapped, records will not sync.

  • Updates only work if “Enable Updates for Matching Records” is turned on in Data Flow Settings.

  • If Company and Contact mappings are not both configured, you may see incomplete data syncing.

  1. Best Practices

  • Double-check mappings before saving.

  • Test with a small batch before large imports.

  • Use logs to identify mis-mapped fields quickly.

  • Keep mapping consistent across projects for reliability.

  • Enable “Optimize for Enrichment” if you plan to enrich CRM records.
    Summary: Proper mapping ensures Jeeva.ai and HubSpot stay aligned. Always verify your mandatory fields, enable Exact Match, and review logs to prevent data mismatches or duplicates.

Related to

Was this article helpful?