Navigation

Importing Contacts via JSON

For rich imports with notes, profile data, and nested structures

Before You Begin

  • A JSON file with contact data

JSON import is designed for situations where CSV falls short — particularly when migrating from another CRM and you need to preserve notes, profile data, communication history, or other nested data that does not fit into flat CSV columns.

Access it from Sales > CRM > Contacts > Import Contacts > JSON Import.

Steps

Prepare your JSON file

The file should contain an array of contact objects. Each object can include standard fields, custom fields, and nested data:

  • Standard fields: `first_name`, `last_name`, `primary_email`, etc.
  • Custom fields: keyed by their smart tags
  • Notes: as an array of note objects with content and visibility
  • Profile data: as key-value objects with source labels
Notes and profile data can only be imported via JSON. If you need to preserve these from your existing system, JSON is the required format.

Upload and process

The JSON import follows a similar flow to CSV: upload, field mapping confirmation, duplicate review, and processing with AI contextualization.

Nested data (notes, profile records) is processed separately from the flat contact fields — each creating its own record linked to the contact.

Result

Contacts are imported with their full data hierarchy intact — notes threaded, profile data stored, and custom fields populated. The AI contextualizer processes each record for additional enrichment.

Tip: When exporting from another CRM, request the export in JSON format if available. Many CRMs support JSON export and it preserves the nested data structures that CSV loses — particularly notes, tags, and custom field groupings.

Continue Reading

Was this article helpful?

NotebookLM Overviews