

Building your pipeline or Using Airbyte
Airbyte is the only open source solution empowering data teams to meet all their growing custom business demands in the new AI era.
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
- Reliable and accurate
- Extensible and scalable for all your needs
- Deployed and governed your way
Start syncing with Airbyte in 3 easy steps within 10 minutes



Take a virtual tour
Demo video of Airbyte Cloud
Demo video of AI Connector Builder
Setup Complexities simplified!
Simple & Easy to use Interface
Airbyte is built to get out of your way. Our clean, modern interface walks you through setup, so you can go from zero to sync in minutes—without deep technical expertise.
Guided Tour: Assisting you in building connections
Whether you’re setting up your first connection or managing complex syncs, Airbyte’s UI and documentation help you move with confidence. No guesswork. Just clarity.
Airbyte AI Assistant that will act as your sidekick in building your data pipelines in Minutes
Airbyte’s built-in assistant helps you choose sources, set destinations, and configure syncs quickly. It’s like having a data engineer on call—without the overhead.
What sets Airbyte Apart
Modern GenAI Workflows
Move Large Volumes, Fast
An Extensible Open-Source Standard
Full Control & Security
Fully Featured & Integrated
Enterprise Support with SLAs
What our users say

Andre Exner

"For TUI Musement, Airbyte cut development time in half and enabled dynamic customer experiences."

Chase Zieman

“Airbyte helped us accelerate our progress by years, compared to our competitors. We don’t need to worry about connectors and focus on creating value for our users instead of building infrastructure. That’s priceless. The time and energy saved allows us to disrupt and grow faster.”

Rupak Patel
"With Airbyte, we could just push a few buttons, allow API access, and bring all the data into Google BigQuery. By blending all the different marketing data sources, we can gain valuable insights."
First, ensure you have access to the Azure Storage account containing the blobs you want to transfer. You'll need the account name and access key to authenticate. You can find these in the Azure Portal under the "Access keys" section of your storage account.
Install the necessary SDKs for Azure Blob Storage and Google Firestore. You can use Python for this task, so install the Azure Storage Blob SDK and the Google Cloud Firestore SDK using pip:
```bash
pip install azure-storage-blob
pip install google-cloud-firestore
```
Use the Azure Storage Blob SDK to authenticate and establish a connection to your Azure Blob Storage account:
```python
from azure.storage.blob import BlobServiceClient
connect_str = "DefaultEndpointsProtocol=https;AccountName=your_account_name;AccountKey=your_account_key;EndpointSuffix=core.windows.net"
blob_service_client = BlobServiceClient.from_connection_string(connect_str)
```
List the blobs you want to migrate and download them locally to a temporary directory:
```python
container_client = blob_service_client.get_container_client("your_container_name")
blob_list = container_client.list_blobs()
for blob in blob_list:
blob_client = blob_service_client.get_blob_client(container="your_container_name", blob=blob.name)
with open(f"temp_directory/{blob.name}", "wb") as my_blob:
download_stream = blob_client.download_blob()
my_blob.write(download_stream.readall())
```
Set up authentication for Google Firestore. Download your service account key from the Google Cloud Console and set the `GOOGLE_APPLICATION_CREDENTIALS` environment variable:
```bash
export GOOGLE_APPLICATION_CREDENTIALS="path/to/serviceAccountKey.json"
```
Then, establish a connection to Firestore using the SDK:
```python
from google.cloud import firestore
db = firestore.Client()
```
Read the downloaded files, transform the data as necessary for Firestore, and upload it to the appropriate Firestore collections:
```python
import json
for blob in blob_list:
with open(f"temp_directory/{blob.name}", "r") as file:
data = json.load(file) # Assuming JSON format, adjust as necessary
doc_ref = db.collection("your_collection_name").document(blob.name) # Use blob name or other identifier
doc_ref.set(data)
```
Once data is successfully uploaded to Firestore, remove the locally downloaded files to free up space:
```python
import os
for blob in blob_list:
os.remove(f"temp_directory/{blob.name}")
```
This guide helps you manually move data from Azure Blob Storage to Google Firestore using Python and the respective SDKs, avoiding any third-party connectors or integrations. Adjust the code snippets as necessary for your specific data format and structure.
FAQs
What is ETL?
ETL, an acronym for Extract, Transform, Load, is a vital data integration process. It involves extracting data from diverse sources, transforming it into a usable format, and loading it into a database, data warehouse or data lake. This process enables meaningful data analysis, enhancing business intelligence.
Azure Blob Storage is a cloud-based storage solution provided by Microsoft Azure. It is designed to store large amounts of unstructured data such as text, images, videos, and audio files. Blob Storage is highly scalable and can store data of any size, from a few bytes to terabytes. It provides a cost-effective way to store and access data from anywhere in the world. Blob Storage also offers features such as data encryption, access control, and data redundancy to ensure data security and availability. It can be used for a variety of applications such as backup and disaster recovery, media storage, and data archiving.
Azure Blob Storage's API provides access to various types of data, including:
1. Unstructured data: This includes any type of data that does not have a predefined data model or structure, such as text, images, videos, and audio files.
2. Structured data: This includes data that has a predefined data model or structure, such as tables, columns, and rows.
3. Semi-structured data: This includes data that has some structure, but not enough to fit into a traditional relational database, such as JSON, XML, and CSV files.
4. Metadata: This includes information about the data stored in Azure Blob Storage, such as file size, creation date, and last modified date.
5. Access control data: This includes information about who has access to the data stored in Azure Blob Storage and what level of access they have.
6. Logging data: This includes information about the activities performed on the data stored in Azure Blob Storage, such as read and write operations, and access attempts.Overall, Azure Blob Storage's API provides access to a wide range of data types, making it a versatile and flexible storage solution for various types of applications and use cases.
What is ELT?
ELT, standing for Extract, Load, Transform, is a modern take on the traditional ETL data integration process. In ELT, data is first extracted from various sources, loaded directly into a data warehouse, and then transformed. This approach enhances data processing speed, analytical flexibility and autonomy.
Difference between ETL and ELT?
ETL and ELT are critical data integration strategies with key differences. ETL (Extract, Transform, Load) transforms data before loading, ideal for structured data. In contrast, ELT (Extract, Load, Transform) loads data before transformation, perfect for processing large, diverse data sets in modern data warehouses. ELT is becoming the new standard as it offers a lot more flexibility and autonomy to data analysts.
What should you do next?
Hope you enjoyed the reading. Here are the 3 ways we can help you in your data journey: