Introduction

You can connect to your Salesforce Data Cloud (Data 360) data from SSIS via the high-performance Salesforce Data Cloud (Data 360) ODBC Driver (powered by ZappySys JDBC-ODBC Bridge Driver). We'll walk you through the entire setup.

Let's not waste time and get started!

Prerequisites

Before we begin, make sure you meet the following prerequisite: Java Runtime Environment (JRE) or Java Development Kit (JDK) must be installed on your system.

If your JDBC Driver targets a different Java version (e.g., 11 / 17 / 21), install the corresponding or newer Java version.

If you already have a JRE installed, you can try using it too. However, if you experience any issues, we recommend using one of the distributions mentioned above (you can install an additional JRE next to the existing one; just don't forget to configure the default Java in the Windows Environment Variables).

Download Salesforce Data Cloud (Data 360) JDBC driver

To connect to Salesforce Data Cloud (Data 360), you will have to download JDBC driver for it, which we will use in later steps. Let's perform these little steps right away:

  1. Visit Salesforce Data Cloud (Data 360) website or MVN Repository.

  2. Select the appropriate JDBC driver version in Latest Versions section in MVN Repository:

    Select JDBC driver version in MVN Repository

  3. Download the JDBC driver, and save it locally, e.g. to C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar.

    Download JDBC driver JAR file in MVN Repository

  4. Done! That was easy, wasn't it? Let's proceed to the next step.

Create data source using Salesforce Data Cloud (Data 360) ODBC Driver

Video instructions

Watch this quick walkthrough to see how to configure your Salesforce Data Cloud (Data 360) ODBC data source, or scroll down for the step-by-step written guide.

While this video demonstrates how to connect to Postgres, the core concepts and setup process are exactly the same for Salesforce Data Cloud (Data 360).

Video doesn't load? Watch this video on YouTube.

Step-by-step instructions

To get data from Salesforce Data Cloud (Data 360) using SSIS, we first need to create an ODBC data source. We will later read this data in SSIS. Perform these steps:

  1. Download and install ODBC PowerPack (if you haven't already).

  2. Search for odbc and open the ODBC Data Sources (64-bit):

    Open ODBC Data Source

  3. Create a User data source (User DSN) based on the ZappySys JDBC Bridge Driver driver:

    ZappySys JDBC Bridge Driver
    Create new User DSN for ZappySys JDBC Bridge Driver
    • Create and use a User DSN if the client application runs under a User Account. This is the ideal option at design time (e.g., when developing in Visual Studio). Use it for both types of applications (64-bit and 32-bit).
    • Create and use a System DSN if the client application runs under a System Account (e.g., as a Windows Service). This is usually the required option in a production environment. If your Windows Service is a 32-bit application, you must use the 32-bit ODBC Data Source Administrator to configure this
    When deployed to production, SSIS runs under a Service Account. Therefore, for the production environment, you must create and use a System DSN.

  4. Now, we need to configure the JDBC connection in the new ODBC data source. Simply enter the Connection string, credentials, configure other settings, and then click Test Connection button to test the connection:

    SalesforceDataCloudData360DSN
    jdbc:salesforce-datacloud://login.salesforce.com
    com.salesforce.datacloud.jdbc.DataCloudJDBCDriver
    C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar
    optional for Salesforce Data Cloud (Data 360)
    optional for Salesforce Data Cloud (Data 360)
    optional for Salesforce Data Cloud (Data 360)
    JDBC-ODBC Bridge driver data source settings

    For Production (login.salesforce.com), use these values when setting parameters:

    • Connection string: jdbc:salesforce-datacloud://login.salesforce.com
    • Driver class: com.salesforce.datacloud.jdbc.DataCloudJDBCDriver
    • JDBC driver file(s): C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar
    • User name:
    • Password:
    • Client ID (Consumer Key):
    • Client Secret (Consumer Secret):
    • Data space: default

      Follow these steps to create a Salesforce External Client App (or a legacy Connected App) so the Data Cloud JDBC driver can authenticate. JDBC Bridge then exposes Data Cloud SQL to Power BI, SQL Server Linked Server via ZappySys Data Gateway, Crystal Reports, SSRS, Azure Data Factory, and other ODBC tools.

      WARNING: As of 21 Feb 2026 Salesforce no longer lets you create new Connected Apps. Use an External Client App. If you already have a Connected App, you can keep using it with username/password + consumer key/secret. Do not use a personal employee login for unattended jobs (Power BI refresh, Linked Server, ADF). Use a dedicated integration user.
      1. Sign in to Salesforce Setup as an administrator.
      2. Go to App Manager (or External Client Apps) and create a new External Client App / Connected App. Enable OAuth Settings.

      3. Callback URL (Redirect URI) must be exactly:

        https://zappysys.com/oauth

        INFO: Use this ZappySys capture page so the authorization code appears in the page title and URL during the 3-legged dance. Do not use localhost, a Salesforce "try it" page, or any other URL -- those often redirect again or drop the query string, so the code is not visible.
      4. Select OAuth scopes your org requires for Data Cloud query (typically includes Data Cloud / CDP query and API access). Save.
      5. Open Manage Consumer Details and copy Consumer Key (Client ID) and Consumer Secret (Client Secret).
      6. Paste username, password (plus security token if your org requires it), Client ID, and Client Secret into this Auth profile.
      7. If you complete a browser authorization, wait until the browser lands on https://zappysys.com/oauth and the code is in the title or address bar.
      8. Finish the wizard. Then click Test Connection on the DSN Main UI (the wizard does not run Test Connection).
      9. Done. You can query from C#, Python, PowerShell, and ODBC apps.

    For Sandbox (test.salesforce.com), use these values when setting parameters:

    • Connection string: jdbc:salesforce-datacloud://test.salesforce.com
    • Driver class: com.salesforce.datacloud.jdbc.DataCloudJDBCDriver
    • JDBC driver file(s): C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar
    • User name:
    • Password:
    • Client ID (Consumer Key):
    • Client Secret (Consumer Secret):
    • Data space: default

      Follow these steps to create a Salesforce External Client App (or a legacy Connected App) so the Data Cloud JDBC driver can authenticate. JDBC Bridge then exposes Data Cloud SQL to Power BI, SQL Server Linked Server via ZappySys Data Gateway, Crystal Reports, SSRS, Azure Data Factory, and other ODBC tools.

      WARNING: As of 21 Feb 2026 Salesforce no longer lets you create new Connected Apps. Use an External Client App. If you already have a Connected App, you can keep using it with username/password + consumer key/secret. Do not use a personal employee login for unattended jobs (Power BI refresh, Linked Server, ADF). Use a dedicated integration user.
      1. Sign in to Salesforce Setup as an administrator.
      2. Go to App Manager (or External Client Apps) and create a new External Client App / Connected App. Enable OAuth Settings.

      3. Callback URL (Redirect URI) must be exactly:

        https://zappysys.com/oauth

        INFO: Use this ZappySys capture page so the authorization code appears in the page title and URL during the 3-legged dance. Do not use localhost, a Salesforce "try it" page, or any other URL -- those often redirect again or drop the query string, so the code is not visible.
      4. Select OAuth scopes your org requires for Data Cloud query (typically includes Data Cloud / CDP query and API access). Save.
      5. Open Manage Consumer Details and copy Consumer Key (Client ID) and Consumer Secret (Client Secret).
      6. Paste username, password (plus security token if your org requires it), Client ID, and Client Secret into this Auth profile.
      7. If you complete a browser authorization, wait until the browser lands on https://zappysys.com/oauth and the code is in the title or address bar.
      8. Finish the wizard. Then click Test Connection on the DSN Main UI (the wizard does not run Test Connection).
      9. Done. You can query from C#, Python, PowerShell, and ODBC apps.

    For JWT Bearer (External Client App), use these values when setting parameters:

    • Connection string: jdbc:salesforce-datacloud://login.salesforce.com
    • Driver class: com.salesforce.datacloud.jdbc.DataCloudJDBCDriver
    • JDBC driver file(s): C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar
    • User name:
    • Client ID (Consumer Key):
    • Private key (PEM):
    • Data space: default

      JWT Bearer Flow with an External Client App (current Salesforce recommendation for JDBC). No refresh-token dance; you still register the callback URL so the app is valid.

      1. Create an External Client App in Salesforce Setup. Enable OAuth and JWT Bearer.
      2. Callback URL must be exactly https://zappysys.com/oauth (do not use localhost or another capture URL).
      3. Upload or generate a certificate. Download the private key as PEM (-----BEGIN PRIVATE KEY-----).
      4. Copy the Consumer Key (Client ID).
      5. Paste Client ID, integration username, and the full PEM into this profile. Do not check a private key into source control.
      6. Finish the wizard. Then click Test Connection on the DSN Main UI (the wizard does not run Test Connection).
      7. Done. You can query from C#, Python, PowerShell, and ODBC apps.

  5. You should see a message saying that connection test is successful:

    ODBC connection test is successful

  6. Otherwise, if you are getting an error, start by troubleshooting the JDBC connection with DBeaver in the section below:

    Jump to troubleshooter

  7. We are at the point where we can preview a SQL query. For more SQL query examples visit JDBC Bridge documentation:

    SalesforceDataCloudData360DSN
    SHOW TABLES
    JDBC ODBC Bridge data source preview 
    SHOW TABLES
    You can also click on the <Select Table> dropdown and select a table from the list.

    The ZappySys JDBC Bridge Driver acts as a transparent intermediary, passing SQL queries directly to the JDBC driver, which then handles the query execution. This means the JDBC-ODBC Bridge Driver simply relays the SQL query without altering it.

    Some JDBC drivers don't support INSERT/UPDATE/DELETE statements, so you may get an error saying "action is not supported" or a similar one. Please, be aware, this is not the limitation of ZappySys JDBC Bridge Driver, but is a limitation of the specific JDBC driver you are using.

  8. Click OK to finish creating the data source.

How to read Salesforce Data Cloud (Data 360) data in SSIS

In this section we will learn how to configure and use Salesforce Data Cloud (Data 360) Connector in the ODBC Source to get data from Salesforce Data Cloud (Data 360).

  1. Open Visual Studio and click Create a new project.

  2. Select Integration Services Project. Enter a name and location for your project, then click OK.

  3. From the SSIS Toolbox, drag and drop a Data Flow Task onto the Control Flow surface, and double-click it:

    Drag Data Flow Task onto Control Flow to use SSIS PowerPack Data Flow components

  4. Make sure you are in the Data Flow Task designer:

    Make sure you are in Data Flow designer in SSIS package

  5. From the SSIS toolbox drag and drop ODBC Source on the dataflow designer surface:

    Drag-and-drop ODBC Source onto Control Flow in SSIS

  6. Double-click on ODBC Source component to configure it.

  7. Click on New... button, it will open Configure ODBC Connection Manager window. Once it opens, click on New... button to create a new ODBC connection to Salesforce Data Cloud (Data 360) ODBC data source:

    Create ODBC Connection Manager in SSIS

  8. Then choose the data source from the list and click Test Connection button. If the connection test is successful, close the window, and then click OK button to finish the configuration:

    SalesforceDataCloudData360DSN
    Create ODBC Connection Manager in SSIS

  9. Once we configured the ODBC connection, we are ready to configure the data source. First, choose Data access mode: Table Name or SQL command. Then select a table from the list or enter your SQL query, appropriately. Finally, hit Preview... button to preview the results and click OK button to close the window.

    SalesforceDataCloudData360DSN
    "schema"."orders"
    Configuring ODBC Source in SSIS

  10. That's it, we are done! Now you can read Salesforce Data Cloud (Data 360) data in SSIS.

Load Salesforce Data Cloud (Data 360) data into SQL Server using Upsert Destination (Insert or Update)

Once you configured the data source, you can load Salesforce Data Cloud (Data 360) data into SQL Server using Upsert Destination.

Upsert Destination can merge or synchronize source data with the target table. It supports Microsoft SQL Server, PostgreSQL, and Redshift databases as targets. Upsert Destination also supports very fast bulk upsert operation along with bulk delete.

Upsert operation - a database operation which performs INSERT or UPDATE SQL commands based on record's existence condition in the target table. It inserts records that don't have matching records in the target table or updates them, if they do, by matching them by key columns.

Upsert Destination supports INSERT, UPDATE, and DELETE operations, so it is similar to SQL Server's MERGE command, except it can be used directly in SSIS package.

  1. Download and install SSIS PowerPack.

  2. From the SSIS Toolbox drag-and-drop Upsert Destination component onto the Data Flow designer background.

  3. Connect your SSIS source component to Upsert Destination.

  4. Double-click on Upsert Destination component to open configuration window.

  5. Start by selecting the Action from the list.

  6. Next, select the desired target connection or create one by clicking <New [provider] Connection> menu item from the Target Connection dropdown.

  7. Then select a table from the Target Table list or click New button to create a new table based on the source columns.

  8. Continue by checking Insert and Update options according to your scenario (e.g. if Update option is unchecked, no updates will be made).

  9. Finally, click Map All button to map all columns and then select the Key columns to match the columns on:

    Configure SSIS Upsert Destination component to merge data with SQL Server, PostgreSQL, or Redshift table

  10. Click OK to save the configuration.

  11. Run the package and Salesforce Data Cloud (Data 360) data will be merged with the target table in SQL Server, PostgreSQL, or Redshift:

    Execute Package - Reading data from API Source and load into target

  12. Done!

Deploy and schedule SSIS package

After you are done creating SSIS package, most likely, you want to deploy it to SQL Server Catalog and run it periodically. Just follow the instructions in this article:

Troubleshooting

Validating JDBC connection in DBeaver

If you are experiencing JDBC connection issues, start by testing your JDBC driver in a JDBC client tool like DBeaver. If the JDBC connection fails in DBeaver, it naturally will not work in your ODBC data source either.

Create generic JDBC driver

  1. Download and install DBeaver Community Edition.

  2. Open DBeaver.

  3. Click Database in the top menu and select Driver Manager:

    Open Driver Manager in DBeaver

  4. Click the New button to start adding a custom JDBC driver:

    Start adding new JDBC driver in DBeaver

  5. Configure the connection settings by entering the Driver Name and Class Name (com.salesforce.datacloud.jdbc.DataCloudJDBCDriver):

    Configure JDBC driver connection settings
    com.salesforce.datacloud.jdbc.DataCloudJDBCDriver

  6. Go to the Libraries tab, click Add File, and select your Salesforce Data Cloud (Data 360) driver library file(s), e.g. C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar:

    Add JAR library to JDBC driver
    Make sure to add all the required library dependencies.

  7. Your JDBC driver jar library is now added:

    JAR library added
    C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar

  8. (Optional). If required by your JDBC driver, add additional properties by going to the Default properties tab, Right-clicking on the background, and selecting Add new property:

    Add new property

  9. Click on a value to modify it, then click OK to finish:

    Set property value

We are now ready to test the connection. Let's proceed!

Test connection

  1. Click the New Database Connection icon in the toolbar:

    Create new database connection in DBeaver

  2. Select your newly created JDBC driver from the list and click Next:

    Select custom JDBC driver

  3. Enter your JDBC URL (e.g. jdbc:salesforce-datacloud://login.salesforce.com), click Test Connection to verify it works, and then click Finish:

    Configure and test JDBC connection
    jdbc:salesforce-datacloud://login.salesforce.com

  4. Finally, expand the database and table list to check the connection status:

    Confirm connection success

There are two possible outcomes from the connection test:

SUCCESS
  • Reason:
    The JDBC driver works perfectly, meaning the issue lies within your ODBC data source configuration.
  • Action:
    Double-check your ODBC data source configuration and ensure it matches the settings that successfully connected in DBeaver.
FAILURE
  • Reason:
    There is likely an issue with the JDBC driver configuration or the connection details provided.
  • Action:
    Contact the ZappySys Support Team for assistance.

If you are still experiencing issues or need further help, please contact us:

Chat with an Expert

Frequent issues and solutions

Below are some useful community articles to help you troubleshoot and configure the ZappySys JDBC Bridge Driver:

Optional: Centralized data access via ZappySys Data Gateway

In some situations, you may need to provide Salesforce Data Cloud (Data 360) data access to multiple users or services. Configuring the data source on a Data Gateway creates a single, centralized connection point for this purpose.

This configuration provides two primary advantages:

  • Centralized data access
    The data source is configured once on the gateway, eliminating the need to set it up individually on each user's machine or application. This significantly simplifies the management process.
  • Centralized access control
    Since all connections route through the gateway, access can be governed or revoked from a single location for all users.
Data Gateway
Local ODBC
data source
Simple configuration
Installation Single machine Per machine
Connectivity Local and remote Local only
Connections limit Limited by License Unlimited
Central data access
Central access control
More flexible cost

To achieve this, you must first create a data source in the Data Gateway (server-side) and then create an ODBC data source in SSIS (client-side) to connect to it.

Let's not wait and get going!

Create Salesforce Data Cloud (Data 360) data source in the gateway

In this section we will create a data source for Salesforce Data Cloud (Data 360) in the Data Gateway. Let's follow these steps to accomplish that:

  1. Search for gateway in the Windows Start Menu and open ZappySys Data Gateway Configuration:

    Open ZappySys Data Gateway Service Manager

  2. Go to the Users tab and follow these steps to add a Data Gateway user:

    • Click the Add button
    • In the Login field enter a username, e.g., john
    • Then enter a Password
    • Check the Is Administrator checkbox
    • Click OK to save
    Data Gateway - Add User

  3. Now we are ready to add a data source:

    • Click the Add button
    • Give the Data source a name (have it handy for later)
    • Then select Native - ZappySys JDBC Bridge Driver
    • Finally, click OK
    SalesforceDataCloudData360DSN
    ZappySys JDBC Bridge Driver
    Data Gateway - Add data source

  4. When the ZappySys JDBC Bridge Driver configuration window opens, go back to ODBC Data Source Administrator where you already have the Salesforce Data Cloud (Data 360) ODBC data source created and configured, and follow these steps on how to Import data source configuration into the Gateway:

    • Open ODBC data source configuration and click Copy settings:
      ZappySys JDBC Bridge Driver - Configuration [Version: 2.0.1.10418]
      ZappySys JDBC Bridge Driver - Salesforce Data Cloud (Data 360)
      Read Salesforce Data Cloud (Data 360) with SQL. Query data graphs and lake objects from Power BI, SQL Server Linked Server via ZappySys Data Gateway, Crystal Reports, SSRS, Azure Data Factory, and other ODBC tools -- almost no coding required.
      SalesforceDataCloudData360DSN
      Copy connection string for ODBC application
    • The window opens, telling us the connection string was successfully copied to the clipboard: Successful connection string copying for ODBC application

    • Then go to Data Gateway configuration and in data source configuration window click Load settings:

      SalesforceDataCloudData360DSN
      ZappySys JDBC Bridge Driver - Configuration [Version: 2.0.1.10418]
      ZappySys JDBC Bridge Driver - Salesforce Data Cloud (Data 360)
      Read Salesforce Data Cloud (Data 360) with SQL. Query data graphs and lake objects from Power BI, SQL Server Linked Server via ZappySys Data Gateway, Crystal Reports, SSRS, Azure Data Factory, and other ODBC tools -- almost no coding required.
      SalesforceDataCloudData360DSN
      Load configuration in ZappySys Data Gateway data source
    • Once a window opens, just paste the settings by pressing CTRL+V or by clicking right mouse button and then Paste option.

  5. Once done, go to the Network Settings tab and Add a firewall rule for inbound traffic:

    Data Gateway - Add firewall rule for inbound connections
    • This will initially allow all inbound traffic.
    • Click Edit IP filters to restrict access to specific IP addresses or ranges.

  6. Crucial Step: After creating or modifying the data source, you must:

    • Click the Save button to persist your changes.
    • Hit Yes when prompted to restart the Data Gateway service.

    This ensures all changes are properly applied:

    ZappySys Data Gateway - Save Changes
    Skipping this step may cause the new settings to fail, preventing you from connecting to the data source.

Create ODBC data source to connect to the gateway

In this part we will create an ODBC data source to connect to the ZappySys Data Gateway from SSIS. To achieve that, let's perform these steps:

  1. Search for odbc and open the ODBC Data Sources (64-bit):

    Open ODBC Data Source

  2. Create a User data source (User DSN) based on the ODBC Driver 17 for SQL Server driver:

    ODBC Driver 17 for SQL Server
    Create new User DSN for ODBC Driver 17 for SQL Server
    If you don't see the ODBC Driver 17 for SQL Server driver in the list, choose a similar version.

  3. Then set a Name for the data source (e.g. Gateway) and the address of the Data Gateway:

    ZappySysGatewayDSN
    localhost,5000
    ODBC driver for SQL Server - Setting hostname and port
    Make sure you separate the hostname and port with a comma, e.g. localhost,5000.

  4. Proceed with the authentication part:

    • Select SQL Server authentication
    • In the Login ID field enter the user name you created in the Data Gateway, e.g., john
    • Set Password to the one you configured in the Data Gateway
    ODBC driver for SQL Server - Selecting SQL Authentication

  5. Then set the default database property to SalesforceDataCloudData360DSN (the one we used in the Data Gateway):

    SalesforceDataCloudData360DSN
    SalesforceDataCloudData360DSN
    ODBC driver for SQL Server - Selecting database
    Make sure to type the data source name manually or copy/paste it directly into the field. Using the dropdown might fail because the Trust server certificate option is not enabled yet (next step).

  6. Continue by checking the Trust server certificate option:

    ODBC driver for SQL Server - Trusting certificate

  7. Once you do that, test the connection:

    ODBC driver for SQL Server - Testing connection

  8. If the connection is successful, everything is good:

    ODBC driver for SQL Server - Testing connection succeeded

  9. Done!

We are ready to move to the final step. Let's do it!

Access data in SSIS via the gateway

Finally, we are ready to read data from Salesforce Data Cloud (Data 360) in SSIS via the Data Gateway. Follow these final steps:

  1. Go back to SSIS.

  2. From the SSIS toolbox drag and drop ODBC Source on the dataflow designer surface:

    Drag-and-drop ODBC Source onto Control Flow in SSIS

  3. Double-click on ODBC Source component to configure it.

  4. Click on New... button, it will open Configure ODBC Connection Manager window. Once it opens, click on New... button to create a new ODBC connection to Salesforce Data Cloud (Data 360) ODBC data source:

    Create ODBC Connection Manager in SSIS

  5. Then choose the data source from the list and click Test Connection button. If the connection test is successful, close the window, and then click OK button to finish the configuration:

    ZappySysGatewayDSN
    Create ODBC Connection Manager in SSIS

  6. Read the data the same way we discussed at the beginning of this article.

  7. That's it!

Now you can connect to Salesforce Data Cloud (Data 360) data in SSIS via the ZappySys Data Gateway.

If you are asked for authentication details, use Database authentication, SQL authentication or Basic authentication option and enter the credentials you used when configuring the Data Gateway, e.g. john and your password.

Conclusion

In this guide, we demonstrated how to connect to Salesforce Data Cloud (Data 360) in SSIS and integrate your data — all without writing complex code. It's worth noting that ZappySys JDBC Bridge Driver allows you to connect not only to Salesforce Data Cloud (Data 360), but to any Java application that supports JDBC (just use a different JDBC driver and configure it appropriately).

Ready to get started? Download ODBC PowerPack now or ping us via chat if you still need help:

Download ODBC PowerPack
Chat with an Expert