Connecting Your Data Warehouse to CaliberMind

General Methods of Exporting CaliberMind Data

If your data team wishes to consolidate all of your data into a single data warehouse, we support multiple methods for transferring the data. For data warehouse specific preferences, read about the most commonly connected data warehouses below.

Method

Details

Pick up data from a CaliberMind-managed BigQuery instance.

If you also have a BigQuery instance, you can use the BigQuery Data Transfer Service to transfer CaliberMind data to your own instance. Upon request, we'll provide you with a service account that has sufficient permissions to access your CaliberMind BigQuery data warehouse. Click here to see BigQuery Data Transfer Service instructions.

Pick up data from a CaliberMind-managed Google Cloud Storage bucket.

If you have a data warehouse other than Google BigQuery, we will provide you with a service account that has sufficient permissions to transfer data from CaliberMind-managed Google Cloud Storage bucket elsewhere. Your internal resources will determine what methods to use when transferring said data. Click here to access a list of allowed transfer methods.

Common Data Warehouses CaliberMind Connects With

These scenarios are primarily illustrative since each customer has a unique technological and resource footprint. We encourage you to work with you sales and customer success representatives to make sure a proper integration strategy is developed.

CaliberMind Data to Google BigQuery

Since CaliberMind is built on top of Google Cloud and BigQuery, the BigQuery Data Transfer service can be used to move CaliberMind data from a Cloud Storage Bucket to a customer’s BigQuery instance.

Click here for more details.

CaliberMind Data to Snowflake

Customers who want to manage the sync of data from CaliberMind to a Snowflake data warehouse should explore directly connecting their Snowflake to a CaliberMind-managed Google Cloud Storage bucket via a CaliberMind-provided service account.

Click here for more details.

CaliberMind Data to Amazon RedShift

Customers who want to manage the sync of data from CaliberMind to an Amazon Redshift data warehouse may wish to explore using the Amazon Glue BigQuery connector to move data from CaliberMind to AWS S3. From there they would be able to directly load the data in question into their Redshift instance.

Click here for more details on CaliberMind to AWS S3 via Glue.

Click here for more details on AWS S3 to RedShift.

Pushing Your Data Warehouse Data to CaliberMind

A common question that customers ask when evaluating CaliberMind is “Can we connect our own data warehouse to CaliberMind?” While most prefer to leverage the built-in data warehouse that comes standard with CaliberMind, we recognize that some customers have invested considerable time and resources into their own data ecosystems and want to leverage those technologies. This article aims to help explain the options available to customers who wish to connect their own data warehouse to CaliberMind.

When it comes to moving data from a customer’s data warehouse to CaliberMind, we first must consider the type of data and use case.

Is the data from a CRM?

CRM data is a core part of the CaliberMind ecosystem. Leveraging this data requires substantial cleaning, normalization, and enhancement. As such, we strongly recommend that CaliberMind is connected directly to the CRM to avoid incurring substantial customization fees.

Our preferred method is to directly connect to the customer’s CRM (e.g. Salesforce, Microsoft Dynamics) to manage inbound and outbound data connections. This enables us to provide the best customer experience possible by preventing insight and reporting issues arising from non-standard CRM data structures.

Within these CRMs, we do have the ability to handle custom fields/objects. Your customer success representative can provide best practice recommendations and consult with you to understand which data points are essential for better analytics.

Is the data imported into your data warehouse from a system we commonly connect to?

A key feature of CaliberMind is the flexibility of what data we can ingest and our growing library of easy-to-use connectors. Information about what connectors we support and how to use them can be found here.

We strongly recommend directly connecting to data sources via our standard connectors where possible. These direct integrations are preferable for a number of reasons, including:

  • Typically the easiest and cheapest option available
  • Typically requires the least amount of technical support on the customer side
  • Standardized connections allow for improved user experience through enhanced traffic monitoring and our ability to respond to source data changes (e.g. API deprecations)

Syncing Data From a Data Warehouse to CaliberMind

If you have reviewed the potential risks associated with bypassing a data source and have decided exporting data to CaliberMind from your data warehouse is still the preferred method, we can support multiple methods.

Method

Details

You manage a process that syncs data to a cloud storage bucket (Google, AWS, or Azure).

Your data warehouse manager can set up a recurring data update to a cloud storage bucket that your company manages. From there, we'll need credentials with sufficient permissions to transfer data out of the cloud storage bucket. This may introduce an additional fee for initial setup and/or an increase in monthly fees depending on the amount and frequency of data to be synced.

You export the data into a flat file (CSV) and send it to us via SFTP.

We can ingest data from SFTP. This may introduce an additional fee for initial setup and/or an increase in monthly fees depending on the amount and frequency of data to be synced.

You have a BigQuery or RedShift instance.

We can connect directly to your BigQuery or Redshift instance. Note that we may need to charge a setup fee to properly map and incorporate your data into our schema and/or an increase in monthly fees depending on the amount and frequency of data to be synced.


How did we do?


Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)