title	description	services	documentationcenter	author	manager	ms.reviewer	ms.service	ms.workload	ms.tgt_pltfrm	ms.devlang	ms.topic	ms.date	ms.author
Copy data from and to Salesforce by using Azure Data Factory \| Microsoft Docs	Learn how to copy data from Salesforce to supported sink data stores or from supported source data stores to Salesforce by using a copy activity in a data factory pipeline.	data-factory		linda33wj	craigg	douglasl	data-factory	data-services	na	na	conceptual	10/17/2018	jingwang

Copy data from and to Salesforce by using Azure Data Factory

[!div class="op_single_selector" title1="Select the version of Data Factory service you are using:"]

Version 1

Current version

This article outlines how to use Copy Activity in Azure Data Factory to copy data from and to Salesforce. It builds on the Copy Activity overview article that presents a general overview of the copy activity.

Supported capabilities

You can copy data from Salesforce to any supported sink data store. You also can copy data from any supported source data store to Salesforce. For a list of data stores that are supported as sources or sinks by the Copy activity, see the Supported data stores table.

Specifically, this Salesforce connector supports:

Salesforce Developer, Professional, Enterprise, or Unlimited editions.
Copying data from and to Salesforce production, sandbox, and custom domain.

The Salesforce connector is built on top of the Salesforce REST API, with v39 for copy data from and v40 for copy data to.

Prerequisites

API permission must be enabled in Salesforce. For more information, see Enable API access in Salesforce by permission set

Salesforce request limits

Salesforce has limits for both total API requests and concurrent API requests. Note the following points:

If the number of concurrent requests exceeds the limit, throttling occurs and you see random failures.
If the total number of requests exceeds the limit, the Salesforce account is blocked for 24 hours.

You might also receive the "REQUEST_LIMIT_EXCEEDED" error message in both scenarios. For more information, see the "API request limits" section in Salesforce developer limits.

Get started

[!INCLUDE data-factory-v2-connector-get-started]

The following sections provide details about properties that are used to define Data Factory entities specific to the Salesforce connector.

Linked service properties

The following properties are supported for the Salesforce linked service.

Property	Description	Required
type	The type property must be set to Salesforce.	Yes
environmentUrl	Specify the URL of the Salesforce instance. - Default is `"https://login.salesforce.com"`. - To copy data from sandbox, specify `"https://test.salesforce.com"`. - To copy data from custom domain, specify, for example, `"https://[domain].my.salesforce.com"`.	No
username	Specify a user name for the user account.	Yes
password	Specify a password for the user account. Mark this field as a SecureString to store it securely in Data Factory, or reference a secret stored in Azure Key Vault.	Yes
securityToken	Specify a security token for the user account. For instructions on how to reset and get a security token, see Get a security token. To learn about security tokens in general, see Security and the API. Mark this field as a SecureString to store it securely in Data Factory, or reference a secret stored in Azure Key Vault.	Yes
connectVia	The integration runtime to be used to connect to the data store. If not specified, it uses the default Azure Integration Runtime.	No for source, Yes for sink if the source linked service doesn't have integration runtime

Important

When you copy data into Salesforce, the default Azure Integration Runtime can't be used to execute copy. In other words, if your source linked service doesn't have a specified integration runtime, explicitly create an Azure Integration Runtime with a location near your Salesforce instance. Associate the Salesforce linked service as in the following example.

Example: Store credentials in Data Factory

{
    "name": "SalesforceLinkedService",
    "properties": {
        "type": "Salesforce",
        "typeProperties": {
            "username": "<username>",
            "password": {
                "type": "SecureString",
                "value": "<password>"
            },
            "securityToken": {
                "type": "SecureString",
                "value": "<security token>"
            }
        },
        "connectVia": {
            "referenceName": "<name of Integration Runtime>",
            "type": "IntegrationRuntimeReference"
        }
    }
}

Example: Store credentials in Key Vault

{
    "name": "SalesforceLinkedService",
    "properties": {
        "type": "Salesforce",
        "typeProperties": {
            "username": "<username>",
            "password": {
                "type": "AzureKeyVaultSecret",
                "secretName": "<secret name of password in AKV>",
                "store":{
                    "referenceName": "<Azure Key Vault linked service>",
                    "type": "LinkedServiceReference"
                }
            },
            "securityToken": {
                "type": "AzureKeyVaultSecret",
                "secretName": "<secret name of security token in AKV>",
                "store":{
                    "referenceName": "<Azure Key Vault linked service>",
                    "type": "LinkedServiceReference"
                }
            }
        },
        "connectVia": {
            "referenceName": "<name of Integration Runtime>",
            "type": "IntegrationRuntimeReference"
        }
    }
}

Dataset properties

For a full list of sections and properties available for defining datasets, see the Datasets article. This section provides a list of properties supported by the Salesforce dataset.

To copy data from and to Salesforce, set the type property of the dataset to SalesforceObject. The following properties are supported.

Property	Description	Required
type	The type property must be set to SalesforceObject.	Yes
objectApiName	The Salesforce object name to retrieve data from.	No for source, Yes for sink

Important

The "__c" part of API Name is needed for any custom object.

Example:

{
    "name": "SalesforceDataset",
    "properties": {
        "type": "SalesforceObject",
        "linkedServiceName": {
            "referenceName": "<Salesforce linked service name>",
            "type": "LinkedServiceReference"
        },
        "typeProperties": {
            "objectApiName": "MyTable__c"
        }
    }
}

Note

For backward compatibility: When you copy data from Salesforce, if you use the previous "RelationalTable" type dataset, it keeps working while you see a suggestion to switch to the new "SalesforceObject" type.

Property	Description	Required
type	The type property of the dataset must be set to RelationalTable.	Yes
tableName	Name of the table in Salesforce.	No (if "query" in the activity source is specified)

Copy activity properties

For a full list of sections and properties available for defining activities, see the Pipelines article. This section provides a list of properties supported by Salesforce source and sink.

Salesforce as a source type

To copy data from Salesforce, set the source type in the copy activity to SalesforceSource. The following properties are supported in the copy activity source section.

Property	Description	Required
type	The type property of the copy activity source must be set to SalesforceSource.	Yes
query	Use the custom query to read data. You can use Salesforce Object Query Language (SOQL) query or SQL-92 query. See more tips in query tips section. If query is not specified, all the data of the Salesforce object specified in "objectApiName" in dataset will be retrieved.	No (if "objectApiName" in the dataset is specified)
readBehavior	Indicates whether to query the existing records, or query all records including the deleted ones. If not specified, the default behavior is the former. Allowed values: query (default), queryAll.	No

Important

The "__c" part of API Name is needed for any custom object.

Example:

"activities":[
    {
        "name": "CopyFromSalesforce",
        "type": "Copy",
        "inputs": [
            {
                "referenceName": "<Salesforce input dataset name>",
                "type": "DatasetReference"
            }
        ],
        "outputs": [
            {
                "referenceName": "<output dataset name>",
                "type": "DatasetReference"
            }
        ],
        "typeProperties": {
            "source": {
                "type": "SalesforceSource",
                "query": "SELECT Col_Currency__c, Col_Date__c, Col_Email__c FROM AllDataType__c"
            },
            "sink": {
                "type": "<sink type>"
            }
        }
    }
]

Note

For backward compatibility: When you copy data from Salesforce, if you use the previous "RelationalSource" type copy, the source keeps working while you see a suggestion to switch to the new "SalesforceSource" type.

Salesforce as a sink type

To copy data to Salesforce, set the sink type in the copy activity to SalesforceSink. The following properties are supported in the copy activity sink section.

Property	Description	Required
type	The type property of the copy activity sink must be set to SalesforceSink.	Yes
writeBehavior	The write behavior for the operation. Allowed values are Insert and Upsert.	No (default is Insert)
externalIdFieldName	The name of the external ID field for the upsert operation. The specified field must be defined as "External Id Field" in the Salesforce object. It can't have NULL values in the corresponding input data.	Yes for "Upsert"
writeBatchSize	The row count of data written to Salesforce in each batch.	No (default is 5,000)
ignoreNullValues	Indicates whether to ignore NULL values from input data during a write operation. Allowed values are true and false. - True: Leave the data in the destination object unchanged when you do an upsert or update operation. Insert a defined default value when you do an insert operation. - False: Update the data in the destination object to NULL when you do an upsert or update operation. Insert a NULL value when you do an insert operation.	No (default is false)

Example: Salesforce sink in a copy activity

"activities":[
    {
        "name": "CopyToSalesforce",
        "type": "Copy",
        "inputs": [
            {
                "referenceName": "<input dataset name>",
                "type": "DatasetReference"
            }
        ],
        "outputs": [
            {
                "referenceName": "<Salesforce output dataset name>",
                "type": "DatasetReference"
            }
        ],
        "typeProperties": {
            "source": {
                "type": "<source type>"
            },
            "sink": {
                "type": "SalesforceSink",
                "writeBehavior": "Upsert",
                "externalIdFieldName": "CustomerId__c",
                "writeBatchSize": 10000,
                "ignoreNullValues": true
            }
        }
    }
]

Query tips

Retrieve data from a Salesforce report

You can retrieve data from Salesforce reports by specifying a query as {call "<report name>"}. An example is "query": "{call \"TestReport\"}".

Retrieve deleted records from the Salesforce Recycle Bin

To query the soft deleted records from the Salesforce Recycle Bin, you can specify readBehavior as queryAll.

Difference between SOQL and SQL query syntax

When copying data from Salesforce, you can use either SOQL query or SQL query. Note that these two has different syntax and functionality support, do not mix it. You are suggested to use the SOQL query which is natively supported by Salesforce. The following table lists the main differences:

Syntax	SOQL Mode	SQL Mode
Column selection	Need to enumarate the fields to be copied in the query, e.g. `SELECT field1, filed2 FROM objectname`	`SELECT *` is supported in addition to column selection.
Quotation marks	Filed/object names cannot be quoted.	Field/object names can be quoted, e.g. `SELECT "id" FROM "Account"`
Datetime format	Refer to details here and samples in next section.	Refer to details here and samples in next section.
Boolean values	Represented as `False` and `True`, e.g. `SELECT … WHERE IsDeleted=True`.	Represented as 0 or 1, e.g. `SELECT … WHERE IsDeleted=1`.
Column renaming	Not supported.	Supported, e.g.: `SELECT a AS b FROM …`.
Relationship	Supported, e.g. `Account_vod__r.nvs_Country__c`.	Not supported.

Retrieve data by using a where clause on the DateTime column

When you specify the SOQL or SQL query, pay attention to the DateTime format difference. For example:

SOQL sample: SELECT Id, Name, BillingCity FROM Account WHERE LastModifiedDate >= @{formatDateTime(pipeline().parameters.StartTime,'yyyy-MM-ddTHH:mm:ssZ')} AND LastModifiedDate < @{formatDateTime(pipeline().parameters.EndTime,'yyyy-MM-ddTHH:mm:ssZ')}
SQL sample: SELECT * FROM Account WHERE LastModifiedDate >= {ts'@{formatDateTime(pipeline().parameters.StartTime,'yyyy-MM-dd HH:mm:ss')}'} AND LastModifiedDate < {ts'@{formatDateTime(pipeline().parameters.EndTime,'yyyy-MM-dd HH:mm:ss')}'}

Data type mapping for Salesforce

When you copy data from Salesforce, the following mappings are used from Salesforce data types to Data Factory interim data types. To learn about how the copy activity maps the source schema and data type to the sink, see Schema and data type mappings.

Salesforce data type	Data Factory interim data type
Auto Number	String
Checkbox	Boolean
Currency	Decimal
Date	DateTime
Date/Time	DateTime
Email	String
Id	String
Lookup Relationship	String
Multi-Select Picklist	String
Number	Decimal
Percent	Decimal
Phone	String
Picklist	String
Text	String
Text Area	String
Text Area (Long)	String
Text Area (Rich)	String
Text (Encrypted)	String
URL	String

Next steps

For a list of data stores supported as sources and sinks by the copy activity in Data Factory, see Supported data stores.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

connector-salesforce.md

connector-salesforce.md

Copy data from and to Salesforce by using Azure Data Factory

Supported capabilities

Prerequisites

Salesforce request limits

Get started

Linked service properties

Dataset properties

Copy activity properties

Salesforce as a source type

Salesforce as a sink type

Query tips

Retrieve data from a Salesforce report

Retrieve deleted records from the Salesforce Recycle Bin

Difference between SOQL and SQL query syntax

Retrieve data by using a where clause on the DateTime column

Data type mapping for Salesforce

Next steps

Files

connector-salesforce.md

Latest commit

History

connector-salesforce.md

File metadata and controls

Copy data from and to Salesforce by using Azure Data Factory

Supported capabilities

Prerequisites

Salesforce request limits

Get started

Linked service properties

Dataset properties

Copy activity properties

Salesforce as a source type

Salesforce as a sink type

Query tips

Retrieve data from a Salesforce report

Retrieve deleted records from the Salesforce Recycle Bin

Difference between SOQL and SQL query syntax

Retrieve data by using a where clause on the DateTime column

Data type mapping for Salesforce

Next steps