

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."
Ensure your Microsoft Dataverse environment is properly configured. Verify that you have access to the data you intend to export. You can do this by logging into your Microsoft Power Platform account, navigating to the Dataverse section, and confirming the necessary permissions and data availability.
Use the built-in export feature in Dataverse to extract your data. Navigate to the table you want to export, click on 'Export Data', and choose the format suitable for your needs, such as CSV or Excel. Save the exported file securely on your local machine.
Convert the exported data into a format compatible with Google Firestore. If you exported your data as a CSV, you might need to write a script in Python, Node.js, or another language to transform this CSV data into JSON format, as Firestore requires data in JSON.
If you haven’t already, create a Google Cloud Platform account. Go to the Google Cloud Console, create a new project, and enable Firebase services to access the Firestore database. Ensure you set up billing as required by GCP to use Firestore.
Install the Firebase CLI and initialize Firestore in your project. Run `firebase init` in your project directory, select Firestore when prompted, and configure your Firestore rules and settings. This sets up the Firebase environment locally.
Create a script to upload your prepared JSON data to Firestore. You can use the Firebase Admin SDK in a language of your choice. The script should authenticate using your Firebase service account credentials and use Firestore's API to write data into the database. Here’s a simple outline in Node.js:
```javascript
const admin = require('firebase-admin');
const serviceAccount = require('path/to/your/serviceAccountKey.json');
admin.initializeApp({
credential: admin.credential.cert(serviceAccount)
});
const db = admin.firestore();
const data = require('path/to/your/data.json');
data.forEach(async (item) => {
await db.collection('your-collection-name').doc(item.id).set(item);
});
```
Replace `'path/to/your/serviceAccountKey.json'`, `'path/to/your/data.json'`, and `'your-collection-name'` with actual values.
After uploading the data, verify its integrity by checking your Firestore database through the Google Cloud Console. Ensure that all records are accurately transferred and that there are no discrepancies. You can write additional scripts to compare record counts or specific fields between your original data and Firestore data to confirm successful migration.
By following these steps, you should be able to move your data from Microsoft Dataverse to Google Firestore without relying on any third-party connectors.
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.
Microsoft Dataverse provides access to the org-based database on Microsoft Dataverse in the current environment This connector was anciently known as Common Data Service. Microsoft Dataverse is one kind of data storage and management engine serving as a foundation for Microsoft’s Power Platform, Office 365, and Dynamics 365 apps. It can easily decouple the data from the application, permitting an administrator to analyze from every possible angle and report on data previously existing in different locations.
Microsoft Dataverse's API provides access to a wide range of data types, including:
1. Entities: These are the primary data objects in Dataverse, such as accounts, contacts, and leads.
2. Fields: These are the individual data elements within an entity, such as name, address, and phone number.
3. Relationships: These define the connections between entities, such as the relationship between a contact and an account.
4. Business rules: These are rules that govern how data is entered and processed within Dataverse.
5. Workflows: These are automated processes that can be triggered by specific events or conditions within Dataverse.
6. Plugins: These are custom code modules that can be used to extend the functionality of Dataverse.
7. Web resources: These are files such as HTML, JavaScript, and CSS that can be used to customize the user interface of Dataverse.
Overall, the Dataverse API provides access to a wide range of data types and functionality, making it a powerful tool for developers and users alike.
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: