When integrating data from Marketing Cloud Engagement to Salesforce CRM (Sales/Service), the appropriate method depends on your specific requirements regarding data volume and timing.
This article details the differences between using Data Loader for batch processing versus using Journey Builder via Marketing Cloud Connect.
To synchronize data, consider one of the following two approaches based on your use case.
This method is highly stable and best suited for periodically updating large volumes of data. It involves exporting data from Marketing Cloud and importing it into CRM using tools like Salesforce Data Loader.
Example Steps
The following is a common example. You can combine automation tools or scripts to fit your operational environment.
Automation Studio: Create a Data Extract activity to extract data from the target Data Extension.
File Transfer: Use a File Transfer activity to move the extracted file to the FTP server.
Import: Retrieve the CSV file from the FTP server and import it into Salesforce CRM using Data Loader.
Note: The import process on the Sales side can be automated using the Data Loader Command Line Interface (CLI).
Benefits and Considerations
Benefits: High stability. Capable of processing large records in bulk with predictable system load. Allows for complex data transformation before import.
Considerations: Not real-time. Updates occur at scheduled intervals (e.g., daily).
Related Resources:
・Data Extension Extract in Automation Studio
・Configuration procedure when using Data Loader in batch mode
This method is suitable for updating CRM records with relatively high immediacy (near real-time) based on individual customer actions. It utilizes the Object Activity within Journey Builder.
Example Steps:
Create or edit a journey in Journey Builder.
Drag and drop the Object Activity from the Sales & Service (formerly Sales Cloud & Service Cloud) section onto the canvas.
Configure the activity to select the target object and the action (e.g., Create, Update).
Benefits and Considerations
Benefits: Updates CRM data in near real-time, triggered by customer behavior.
Considerations:
Not for High Volume: Journey Builder is not optimized for bulk data updates. For high-volume record updates, Method 1 (Data Loader) is strongly recommended.
Performance Impact: Injecting a massive number of contacts solely for updates may affect the performance or processing speed of other active journeys in the account.
Billable Contact Count: Contacts entering a journey are added to All Contacts in Marketing Cloud. This may increase your Billable Contact Count, even if no emails are sent.
API Limits: Each record processed consumes API calls. High volume usage risks hitting Salesforce CRM API Limits.
Related Resources:
|
Feature |
Data Loader (Batch) |
Marketing Cloud Connect |
|
Timing |
Periodic (e.g., Daily/Weekly) |
Relatively High Immediacy (Trigger-based) |
|
Recommended Volume |
High Volume (10,000+ records) |
Low to Medium Volume |
|
Stability |
High (Recommended for bulk data) |
Medium (Subject to API limits and throughput) |
005232944

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.