---
schema_version: "1"
id: ce2c72ea6127ea713cf9b11dad27903fea334b67855b22f3f9165479fd87b922
title: Import Notes into Salesforce
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/dataloader/dataloader-help/guides/salesforce-lightning-experience.md
canonical_url: https://developer.salesforce.com/docs/platform/dataloader/guide/salesforce-lightning-experience.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 5672ba2af8c013d5b4f7d8bd9263c55568a97a8c1fd3476274daab742d0f51f4
products:
  - Dataloader from MuleSoft
---
# Import Notes into Salesforce

In Salesforce Lightning Experience, notes are stored as **ContentNote** objects rather than classic **Note** objects. This difference affects how you structure CSV files and how many import tasks you run in Dataloader from MuleSoft.

Salesforce provides two note-related objects:

- The classic **Note** object.
- **ContentNote** (Enhanced Notes), which supports rich text. See the [ContentNote object reference](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contentnote.htm).

In Lightning Experience, new notes you create in Salesforce typically use **ContentNote**. Older notes can appear differently in the UI.

**ContentNote** links to other records differently than classic Notes. Instead of a single **Parent ID** field, the relationship uses **ContentDocumentLink**. This means importing notes requires two separate tasks: one to create the ContentNote records, and one to link them to parent records. See the [ContentDocumentLink object reference](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contentdocumentlink.htm).

## Step 1. Insert ContentNote Records

1. Create an import task for the **ContentNote** object.

2. Map the required fields (**Content** is the note body; there is no **Parent ID** on ContentNote itself) and run the task.

## Step 2. Link Notes to a Parent Object

After **ContentNote** rows exist, link them with a second import on **ContentDocumentLink**:

1. Create an import task for **ContentDocumentLink**.

2. Include at least these columns in your CSV file:
   - **Linked Entity ID**: Parent record ID (for example, Account ID).
   - **ContentDocument ID**: ID of the note from the first task.
   - **ShareType**: Permission value `V`, `C`, or `I` (see the [ContentDocumentLink object reference](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contentdocumentlink.htm)).

When the second task finishes, Dataloader links the notes to the parent records.

**tip:** To save steps, build your first CSV file with all **ContentNote** fields plus parent ID and **ShareType** as extra columns. Don't map the parent ID and ShareType columns in the **ContentNote** task.

After the first task completes, download the success file and use it as input for **ContentDocumentLink**. The success file includes **ContentDocumentId**, which you need for the link task.

## See Also

- [Importing Data into Salesforce](https://developer.salesforce.com/docs/platform/dataloader/guide/import-data.md)
- [Use Import Lookups](https://developer.salesforce.com/docs/platform/dataloader/guide/import-lookups.md)
- [Export Data from Salesforce](https://developer.salesforce.com/docs/platform/dataloader/guide/export-data.md)
- [_Salesforce Developers_: ContentNote object reference](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contentnote.htm)
- [_Salesforce Developers_: ContentDocumentLink object reference](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contentdocumentlink.htm)