MongoDB to Snowflake: 3 Easy Methods

Organizations often need to integrate data from various sources to gain valuable insights. One common scenario is transferring data from a NoSQL database like MongoDB to a cloud data warehouse like Snowflake for advanced analytics and business intelligence.

However, this process can be challenging, especially for those new to data engineering. In this blog post, we’ll explore three easy methods to seamlessly migrate data from MongoDB to Snowflake, ensuring a smooth and efficient data integration process.

Mongodb realtime replication to Snowflake ensures that data is consistently synchronized between MongoDB and Snowflake databases. Due to MongoDB’s schemaless nature, it becomes important to move the data to a warehouse-like Snowflake for meaningful analysis.

In this article, we will discuss the different methods to migrate MongoDB to Snowflake.

Note: The MongoDB snowflake connector offers a solution for real-time data synchronization challenges many organizations face.

Introduction to MongoDB

MongoDB is a popular NoSQL database management system designed for flexibility, scalability, and performance in handling unstructured or semistructured data. This document-oriented database presents a view wherein data is stored as flexible JSON-like documents instead of the traditional table-based relational databases. Data in MongoDB is stored in collections, which contain documents. Each document may have its own schema, which provides for dynamic and schema-less data storage. It also supports rich queries, indexing, and aggregation.

Key Use Cases

• Real-time Analytics: You can leverage its aggregation framework and indexing capabilities to handle large volumes of data for real-time analytics and reporting.
• Personalization/Customization: It can efficiently support applications that require real-time personalization and recommendation engines by storing and querying user behavior and preferences.

Introduction to Snowflake

Snowflake is a fully managed service that provides customers with near-infinite scalability of concurrent workloads to easily integrate, load, analyze, and securely share their data. Its common applications include data lakes, data engineering, data application development, data science, and secure consumption of shared data. 

Snowflake’s unique architecture natively integrates computing and storage. This architecture enables you to virtually enable your users and data workloads to access a single copy of your data without any detrimental effect on performance.

With Snowflake, you can seamlessly run your data solution across multiple regions and Clouds for a consistent experience. Snowflake makes it possible by abstracting the complexity of underlying Cloud infrastructures.

Advantages of Snowflake

• Scalability: Using Snowflake, you can automatically scale the compute and storage resources to manage varying workloads without any human intervention.
• Supports Concurrency: Snowflake delivers high performance when dealing with multiple users supporting mixed workloads without performance degradation.
• Efficient Performance: You can achieve optimized query performance through the unique architecture of Snowflake, with particular techniques applied in columnar storage, query optimization, and caching.

Understanding the Methods to Connect MongoDB to Snowflake

These are the methods you can use to move data from MongoDB to Snowflake:

• Method 1: Using Hevo Data to Move Data from MongoDB to Snowflake
• Method 2: Writing Custom Scripts to Move Data from MongoDB to Snowflake
• Method 3: Using Native Cloud Tools and Snowpipe for MongoDB to Snowflake

Method 1: Using Hevo Data to Move Data from MongoDB to Snowflake

You can use Hevo Data to effortlessly move your data from MongoDB to Snowflake in just two easy steps. Go through the detailed illustration provided below of moving your data using Hevo to ease your work.

Learn more about Hevo

Step 1: Configure MongoDB as a Source

Hevo supports 150+ sources, including MongoDB. All you need to do is provide us with acces to your database.

Step 1.1: Select MongoDB as the source.

Step 1.2: Provide Credentials to MongoDB – You need to provide details like Hostname, Password, Database Name and Port number so that Hevo can access your data from the database.

Step 1.3: Once you have filled in the required details, you can enable the Advanced Settings options that Hevo provides.

Once done, Click on Test and Continue to test your connection to the database.

Step 2: Configure Snowflake as a Destination

After configuring your Source, you can select Snowflake as your destination. You need to have an active Snowflake account for this.

Step 2.1: Select Snowflake as the Destination.

Step 2.2: Enter Snowflake Configuration Details – You can enter the Snowflake Account URL that you obtained. Also, Database User, Database Password, Database Name, and Database Schema.

Step 2.3: You can now click on Save Destination.

After the connection has been successfully established between the source and the destination, data will start flowing automatically. That’s how easy Hevo makes it for you.

With this, you have successfully set up MongoDB to Snowflake Integration using Hevo Data.

• Learn how to set up MongoDB as a source.
• Learn how to set up Snowflake as a destination.

Here are a few advantages of using Hevo:

• Easy Setup and Implementation – Hevo is a self-serve, managed data integration platform. You can cut down your project timelines drastically as Hevo can help you move data from SFTP/FTP to Snowflake in minutes.
• Transformations – Hevo provides preload transformations through Python code. It also allows you to run transformation code for each event in the pipelines you set up. You need to edit the event object’s properties received in the transform method as a parameter to carry out the transformation. Hevo also offers drag-and-drop transformations like Date and Control Functions, JSON, and Event Manipulation to name a few. These can be configured and tested before putting them to use.
• Connectors – Hevo supports 150+ integrations to SaaS platforms, files, databases, analytics, and BI tools. It supports various destinations including Google BigQuery, Amazon Redshift, Snowflake Data Warehouses; Amazon S3 Data Lakes; and MySQL, MongoDB, TokuDB, DynamoDB, and PostgreSQL databases to name a few.  
• 150+ Pre-built integrations – In addition to SFTP/FTP, Hevo can bring data from 150+ other data sources into Snowflake in real-time. This will ensure that Hevo is the perfect companion for your business’s growing data integration needs.
• Complete Monitoring and Management – In case the FTP server or Snowflake data warehouse is not reachable, Hevo will re-attempt data loads in a set instance ensuring that you always have accurate, up-to-date data in Snowflake.
• 24×7 Support – To ensure that you get timely help, Hevo has a dedicated support team to swiftly join data has a dedicated support team that is available 24×7 to ensure that you are successful with your project.

Simplify your Data Analysis with Hevo today! 

SIGN UP HERE FOR A 14-DAY FREE TRIAL!

Method 2: Writing Custom Scripts to Move Data from MongoDB to Snowflake

Below is a quick snapshot of the broad framework to move data from MongoDB to Snowflake using custom code.

The steps are:

• Step 1: Extracting data from MongoDB Collections
• Step 2: Optional Data Type conversions and Data Formatting
• Step 3: Staging Data Files
• Step 4: Copying Staged Files to Snowflake Table
• Step 5: Migrating to Snowflake

Let’s take a detailed look at all the required steps for MongoDB Snowflake Integration:

Step 1: Extracting data from MongoDB Collections

mongoexport is the utility coming with MongoDB which can be used to create JSON or CSV export of the data stored in any MongoDB collection.

The following points are to be noted while using mongoexport :

• mongoexport should be running directly in the system command line, not from the Mongo shell (the mongo shell is the command-line tool used to interact with MongoDB)
• That the connecting user should have at least the read role on the target database. Otherwise, a permission error will be thrown.
• mongoexport by default uses primary read (direct read operations to the primary member in a replica set) as the read preference when connected to mongos or a replica set.
• Also, note that the default read preference which is “primary read”  can be overridden using the –readPreference option

Below is an  example showing how to export data from the collection named contact_coln to a CSV file in the location /opt/exports/csv/col_cnts.csv

mongoexport --db users --collection contact_coln --type=csv --fields empl_name,empl_address --out /opt/exports/csv/empl_contacts.csv

• To export in CSV format, you should specify the column names in the collection to be exported. The above example specifies the empl_name and empl_address fields to export.

The output would look like this:

empl_name, empl_address

Prasad, 12 B street, Mumbai

Rose, 34544 Mysore

• You can also specify the fields to be exported in a file as a line-separated list of fields to export – with one field per line. For example, you can specify the emplyee_name and employee_address fields in a file empl_contact_fields.txt :

empl_name,

empl_address

Then, applying the –fieldFile option, define the fields to export with the file:

mongoexport --db users --collection contact_coln --type=csv --fieldFile empl_contact_fields.txt --out /opt/backups/emplyee_contacts.csv

• Exported CSV files will have field names as a header by default. If you don’t want a header in the output file,–noHeaderLine option can be used.
• As in the above example –fields can be used to specify fields to be exported. It can also be used to specify nested fields. Suppose you have post_code filed with employee_address filed, it can be specified as employee_address.post_code

Incremental Data Extract From MongoDB

So far we have discussed extracting an entire MongoDB collection. It is also possible to filter the data while extracting from the collection by passing a query to filter data. This can be used for incremental data extraction. –query or -q is used to pass the query.
For example, let’s consider the above-discussed contacts collection. Suppose the ‘updated_time’ field in each document stores the last updated or inserted Unix timestamp for that document.

mongoexport -d users -c contact_coln -q '{ updated_time: { $gte: 154856788 } }'  --type=csv --fieldFile employee_contact_fields.txt  --out exportdir/emplyee_contacts.csv

The above command will extract all records from the collection with updated_time greater than the specified value,154856788. You should keep track of the last pulled updated_time separately and use that value while fetching data from MongoDB each time.

Step 2: Optional Data Type conversions and Data Formatting

Along with the application-specific logic to be applied while transferring data, the following are to be taken care of when migrating data to Snowflake.

• Snowflake can support many of the character sets including UTF-8. For the full list of supported encodings please visit here.
• If you have worked with cloud-based data warehousing solutions before, you might have noticed that most of them lack support constraints and standard SQL constraints like UNIQUE, PRIMARY KEY, FOREIGN KEY, NOT NULL. However, keep in mind that Snowflake supports most of the SQL constraints.
• Snowflake data types cover all basic and semi-structured types like arrays. It also has inbuilt functions to work with semi-structured data. The below list shows Snowflake data types compatible with the various MongoDB data types.

MongoDB Data Type	Snowflake Data Type
DOUBLE	DOUBLE,   DOUBLE PRECISION
STRING	STRING, TEXT
BINARY DATA	BINARY
OBJECTID	STRING, TEXT
BOOLEAN	BOOLEAN
DATE	DATE
NULL	NULL
32-BIT INTEGER	INTEGER
TIMESTAMP	TIMESTAMP
64-BIT INTEGER	INT64
DECIMAL128	DECIMAL

• As you can see from this table of MongoDB vs Snowflake data types, while inserting data, Snowflake allows almost all of the date/time formats. You can explicitly specify the format while loading data with the help of the File Format Option. We will discuss this in detail later. The full list of supported date and time formats can be found here.

Step 3: Staging Data Files

If you want to insert data into a Snowflake table, the data should be uploaded to online storage like S3. This process is called staging. Generally, Snowflake supports two types of stages – internal and external.

Internal Stage

For every user and table, Snowflake will create and allocate a staging location that is used by default for staging activities and those stages are named using some conventions as mentioned below. Note that is also possible to create named internal stages.

• The user stage is named ‘@~’
• The name of the table stage is the name of the table.
• The user or table stages can’t be altered or dropped.
• It is not possible to set file format options in the default user or table stages.

Named internal stages can be created explicitly using SQL statements. While creating named internal stages, file format, and other options can be set which makes loading data to the table very easy with minimal command options.

SnowSQL comes with a lightweight CLI client which can be used to run commands like DDLs or data loads. This is available in Linux/Mac/Windows. Read more about the tool and options here.

Below are some example commands to create a stage:

Create a names stage:

create or replace stage my_mongodb_stage

copy_options = (on_error='skip_file')

file_format = (type = 'CSV' field_delimiter = '|' skip_header = 2);

The PUT command is used to stage data files to an internal stage. The syntax is straightforward – you only need to specify the file path and stage name :

PUT file://path_to_file/filename internal_stage_name

Eg:

Upload a file named emplyee_contacts.csv in the /tmp/mongodb_data/data/ directory to an internal stage named mongodb_stage

put file:////tmp/mongodb_data/data/emplyee_contacts.csv @mongodb_stage;

There are many configurations to be set to maximize data load spread while uploading the file like the number of parallelisms, automatic compression of data files, etc. More information about those options is listed here.

External Stage

AWS and Azure are the industry leaders in the public cloud market. It does not come as a surprise that Snowflake supports both Amazon S3 and Microsoft Azure for external staging locations. If the data is in S3 or Azure, all you need to do is create an external stage to point that and the data can be loaded to the table.

To create an external stage on S3, IAM credentials are to be specified. If the data in S3 is encrypted, encryption keys should also be given.

create or replace stage mongod_ext_stage url='s3://snowflake/data/mongo/load/files/'

credentials=(aws_key_id='181a233bmnm3c' aws_secret_key='a00bchjd4kkjx5y6z');

encryption=(master_key = 'e00jhjh0jzYfIjka98koiojamtNDwOaO8=');

Data to the external stage can be uploaded using respective cloud web interfaces or provided SDKs or third-party tools.

Step 4: Copying Staged Files to Snowflake Table

COPY INTO is the command used to load data from the stage area into the Snowflake table. Compute resources needed to load the data are supplied by virtual warehouses and the data loading time will depend on the size of the virtual warehouses

Eg:

To load from a named internal stage

copy into mongodb_internal_table

from @mngodb_stage;

To load from the external stage :(Here only one file is specified)

copy into mongodb_external_stage_table

from @mongodb_ext_stage/tutorials/dataloading/employee_contacts_ext.csv;

To copy directly from an external location without creating a stage:

copy into mongodb_table

from s3://mybucket/snow/mongodb/data/files

credentials=(aws_key_id='$AWS_ACCESS_KEY_ID' aws_secret_key='$AWS_SECRET_ACCESS_KEY')

encryption=(master_key = 'eSxX0jzYfIdsdsdsamtnBKOSgPH5r4BDDwOaO8=')

file_format = (format_name = csv_format);

The subset of files can be specified using patterns

copy into mongodb_table

from @mongodb_stage

file_format = (type = 'CSV')

pattern='.*/.*/.*[.]csv[.]gz';

Some common format options used in COPY command for CSV format :

• COMPRESSION – Compression used for the input data files.
• RECORD_DELIMITER – The character used as records or lines separator
• FIELD_DELIMITER -Character used for separating fields in the input file.
• SKIP_HEADER – Number of header lines to skip while loading data.
• DATE_FORMAT – Used to specify the date format
• TIME_FORMAT – Used to specify the time format

The full list of options is given here.

Step 5: Migrating to Snowflake

While discussing data extraction from MongoDB both full and incremental methods are considered. Here, we will look at how to migrate that data into Snowflake effectively.

Snowflake’s unique architecture helps to overcome many shortcomings of existing big data systems. Support for row-level updates is one such feature.

Out-of-the-box support for the row-level updates makes delta data load to the Snowflake table simple. We can extract the data incrementally, load it into a temporary table and modify records in the final table as per the data in the temporary table.

There are three popular methods to update the final table with new data after new data is loaded into the intermediate table.

1. Update the rows in the final table with the value in a temporary table and insert new rows from the temporary table into the final table.

UPDATE  final_mongodb_table t

SET t.value = s.value

FROM  intermed_mongdb_table in

WHERE t.id = in.id;


INSERT INTO final_mongodb_table (id, value)

SELECT id, value

FROM  intermed_mongodb_table

WHERE NOT id IN (SELECT id FROM final_mongodb_table);

 2. Delete all rows from the final table which are also present in the temporary table. Then insert all rows from the intermediate table to the final table.

DELETE .final_mogodb_table f

WHERE f.id IN (SELECT id from intermed_mongodb_table);

INSERT final_mongodb_table (id, value)

SELECT id, value

FROM intermed_mongodb_table;

3. MERGE statement – Using a single MERGE statement both inserts and updates can be carried out simultaneously.  We can use this option to apply changes to the temporary table.

MERGE into final_mongodb_table t1 using tmp_mongodb_table t2 on t1.key = t2.key

WHEN matched then update set value = t2.value

WHEN not matched then INSERT (key, value) values (t2.key, t2.value);

Limitations of using Custom Scripts to Connect MongoDB to Snowflake

Even though the manual method will get your work done but you might face some difficulties while doing it. I have listed below some limitations that might hinder your data migration process:

• If you want to migrate data from MongoDB to Snowflake in batches, then this approach works decently well. However, if you are looking for real-time data availability, this approach becomes extremely tedious and time-consuming.
• With this method, you can only move data from one place to another, but you cannot transform the data when in transit.
• When you write code to extract a subset of data, those scripts often break as the source schema keeps changing or evolving. This can result in data loss.

The method mentioned above has a high scope of errors. This might impact Snowflake’s availability and accuracy of data.

Method 3: Using Native Cloud Tools and Snowpipe for MongoDB to Snowflake

Snowpipe, provided by Snowflake, enables a shift from the traditional scheduled batch loading jobs to a more dynamic approach. It supersedes the conventional SQL COPY command, facilitating near real-time data availability. Essentially, Snowpipe imports data into a staging area in smaller increments, working in tandem with your cloud provider’s native services, such as AWS or Azure.

For illustration, consider these scenarios for each cloud provider, detailing the integration of your platform’s infrastructure and the transfer of data from MongoDB to a Snowflake warehouse:

AWS: Utilize a Kinesis delivery stream to deposit MongoDB data into an S3 bucket. With an active SNS system, the associated successful run ID can be leveraged to import data into Snowflake using Snowpipe.

Azure: Activate Snowpipe with an Event Grid message corresponding to Blob storage events. Your MongoDB data is initially placed into an external Azure stage. Upon creating a blob storage event message, Snowpipe is alerted via Event Grid when the data is primed for Snowflake insertion. Subsequently, Snowpipe transfers the queued files into a pre-established table in Snowflake. For comprehensive guidance, Snowflake offers a detailed manual on the setup.

Limitations of Using Native Cloud Tools and Snowpipe

• A deep understanding of NoSQL databases, Snowflake, and cloud services is crucial. Troubleshooting in a complex data pipeline environment necessitates significant domain knowledge, which may be challenging for smaller or less experienced data teams.
• Long-term management and ownership of the approach can be problematic, as the resources used are often controlled by teams outside the Data department. This requires careful coordination with other engineering teams to establish clear ownership and ongoing responsibilities.
• The absence of native tools for applying schema to NoSQL data presents difficulties in schematizing the data, potentially reducing its value in the data warehouse.

MongoDB to Snowflake: Use Cases

• Snowflake’s system supports JSON natively, which is central to MongoDB’s document model. This allows direct loading of JSON data into Snowflake without needing to convert it into a fixed schema, eliminating the need for an ETL pipeline and concerns about evolving data structures.
• Snowflake’s architecture is designed for scalability and elasticity online. It can handle large volumes of data at varying speeds without resource conflicts with analytics, supporting micro-batch loading for immediate data analysis. Scaling up a virtual warehouse can speed up data loading without causing downtime or requiring data redistribution.
• Snowflake’s core is a powerful SQL engine that works seamlessly with BI and analytics tools. Its SQL capabilities extend beyond relational data, enabling access to MongoDB’s JSON data, with its variable schema and nested structures, through SQL. Snowflake’s extensions and the creation of relational views make this JSON data readily usable with SQL-based tools.

Additional Resources for MongoDB Integrations and Migrations

• Stream data from mongoDB Atlas to BigQuery
• Move Data from MongoDB to MySQL
• Connect MongoDB to Tableau
• Sync Data from MongoDB to PostgreSQL
• Move Data from MongoDB to Redshift

Conclusion

In this blog we have three methods using which you can migrate your data from MongoDB to Snowflake. However,  the choice of migration method can impact the process’s efficiency and complexity. Using custom scripts or Snowpipe for data ingestion may require extensive manual effort, face challenges with data consistency and real-time updates, and demand specialized technical skills. 

For using the Native Cloud Tools, you will need a deep understanding of NoSQL databases, Snowflake, and cloud services.  Moreover, troubleshooting can also be troublesome in such an environment. On the other hand, leveraging Hevo simplifies and automates the migration process by providing a user-friendly interface and pre-built connectors.

VISIT OUR WEBSITE TO EXPLORE HEVO

Want to take Hevo for a spin?

SIGN UP to explore a hassle-free data migration from MongoDB to Snowflake. You can also have a look at the unbeatable pricing that will help you choose the right plan for your business needs.

Share your experience of migrating data from MongoDB to Snowflake in the comments section below!

FAQs to migrate from MongoDB to Snowflake