How does Hotmart data replication to SQL Server work?

Kondado connects directly to your Hotmart account using your API credentials and extracts data from selected pipelines. The platform then loads this information into your SQL Server database on your configured schedule, automatically handling schema creation and incremental updates to keep your dataset current without manual intervention.

What Hotmart data can I replicate to SQL Server?

You can replicate 11 distinct pipelines including Subscribers, Subscription Transactions, Sales Commissions, Subscriber Purchases, and four Hotmart Club datasets covering student progress and engagement. Each pipeline delivers specific fields such as subscriber codes, commission values, completion percentages, and access counts that map to structured columns in your SQL Server instance.

How often does Kondado update Hotmart data in SQL Server?

Kondado offers flexible scheduling options ranging from every five minutes to daily intervals, allowing you to balance data freshness with system resources. You configure the update frequency during pipeline setup, and the platform automatically manages the extraction and loading process according to your specified timeline.

Can I combine Hotmart data with other sources in SQL Server?

Yes, SQL Server serves as a central repository where Hotmart data can coexist alongside information from other business systems. You can join your replicated Hotmart Subscribers and Sales Commissions data with datasets from PostgreSQL or cloud warehouses like BigQuery , enabling comprehensive analytics that span multiple platforms within a single database environment.

What format does Hotmart data take in SQL Server?

Hotmart data arrives in SQL Server as normalized relational structures with appropriate data types for each field, including decimal values for commissions, datetime stamps for transactions, and varchar fields for subscriber names. The platform maintains consistent schema designs that support standard SQL operations, indexing, and joins with your existing business data.

Can I use Hotmart data in SQL Server with BI tools?

Absolutely, once your data resides in SQL Server, you can connect Power BI , Looker Studio , or other visualization platforms directly to your database. This connection enables you to build custom reports that blend Hotmart sales metrics with SQL Server analytics, creating comprehensive dashboards that update automatically as new data arrives.

How do I handle Hotmart subscription changes in SQL Server?

The Subscribers pipeline captures status changes, cancellations, and renewals, updating corresponding records in SQL Server during each scheduled run. You can track subscription lifecycles by querying historical states and current statuses, enabling churn analysis and retention reporting based on accurate, timestamped data points.

Send data from Hotmart to SQL Server

Get started for free

No credit card required | 14 days | 10 million records | 30 pipelines

or sign up with your email

By signing up, you agree to Kondado’s Terms of service and Privacy policy

Replicate Hotmart Data to SQL Server Automatically

How to send Hotmart data to SQL Server? Kondado provides a direct integration that lets you replicate your digital commerce data from Hotmart to SQL Server without writing code or managing complex API connections. Simply select your data source, choose your destination database, and configure which pipelines you want to replicate based on your analytical needs. The platform handles the data transfer on your chosen schedule, whether you require updates every five minutes or prefer daily batches for resource optimization.

Kondado replicates 11 data pipelines from Hotmart to SQL Server automatically on a configurable schedule, including Subscribers, Sales Commissions, Subscription Transactions, and Hotmart Club data, delivering 202 fields of ecommerce and student progress information directly to your database.

Once your Hotmart data arrives in SQL Server, you can build custom reports, perform complex joins with other business data, and create automated workflows that keep your analytics current. This setup eliminates manual CSV exports and gives your team consistent access to subscription metrics, commission details, and student engagement data for comprehensive business intelligence and financial reporting.

Our prices start from $19 USD/month, and you can try Kondado for free for 14 days with no credit card required

Available Hotmart Pipelines for SQL Server

Your replicated Subscribers and Subscription Transactions pipelines enable detailed cohort analysis and revenue forecasting directly within SQL Server. By combining Sales Commissions data with your existing financial records, you can calculate precise profitability per digital product and optimize affiliate payout structures. The Hotmart Club pipelines, including Students and Student Progress, allow you to monitor course completion rates and identify at-risk learners by querying engagement metrics alongside sales performance.

This consolidated data supports complex SQL queries that reveal cross-platform insights, such as correlating student progress with subscription renewals or analyzing which price points drive the highest commission values. With all your Hotmart data normalized in SQL Server, you can create custom dashboards in Power BI, Looker Studio, or Google Sheets, or feed directly into your existing enterprise architecture for centralized reporting.

Try out all the features for free for 14 days

Hotmart data available for SQL Server

available pipelines

202

extractable fields

Available integrations

Integration	Description
Subscribers	Records of subscriptions include subscriber_code, subscriber_name, and status, allowing detailed analysis of active and canceled subscriptions.
Sales Commissions	Commission details include transaction, commission_value, and user_name, providing a clear view of commissions generated by each transaction.
Subscriber Purchases	Data on purchases includes subscriber_code, product_id, and price_value, allowing tracking of acquisitions made by subscribers.
Sales Price Breakdown	Detailed pricing information includes product_id, price_value, and price_currency_code, facilitating analysis of sales prices.
Sales History	Sales records include purchase_transaction, product_id, and request_date, allowing analysis of transaction history.
Hotmart Club: Students	Information about students includes subscriber_name, product_id, and status, allowing tracking of students' progress in the club.
Hotmart Club: Modules	Data on modules includes product_id, module_name, and completion_status, allowing analysis of students' progress in each module.
Hotmart Club: Student Progress	Progress records include subscriber_code, module_id, and completion_percentage, facilitating monitoring of students' performance.
Hotmart Club: Pages	Information about pages includes page_id, access_count, and last_access_date, allowing analysis of student engagement.
Products	Product data includes product_id, product_name, and price_value, allowing detailed analysis of the available product portfolio.
Subscription Transactions	Records of subscription transactions, including fields such as transaction code, product ID, and commission value.

Subscribers

Records of subscriptions include subscriber_code, subscriber_name, and status, allowing detailed analysis of active and canceled subscriptions.

Sales Commissions

Commission details include transaction, commission_value, and user_name, providing a clear view of commissions generated by each transaction.

Subscriber Purchases

Data on purchases includes subscriber_code, product_id, and price_value, allowing tracking of acquisitions made by subscribers.

Sales Price Breakdown

Detailed pricing information includes product_id, price_value, and price_currency_code, facilitating analysis of sales prices.

Sales History

Sales records include purchase_transaction, product_id, and request_date, allowing analysis of transaction history.

Hotmart Club: Students

Information about students includes subscriber_name, product_id, and status, allowing tracking of students' progress in the club.

Hotmart Club: Modules

Data on modules includes product_id, module_name, and completion_status, allowing analysis of students' progress in each module.

Hotmart Club: Student Progress

Progress records include subscriber_code, module_id, and completion_percentage, facilitating monitoring of students' performance.

Hotmart Club: Pages

Information about pages includes page_id, access_count, and last_access_date, allowing analysis of student engagement.

Products

Product data includes product_id, product_name, and price_value, allowing detailed analysis of the available product portfolio.

Subscription Transactions

Records of subscription transactions, including fields such as transaction code, product ID, and commission value.

See all available data →

Try out all the features for free for 14 days

How to send Hotmart data to SQL Server

Sync data automatically — no code, no manual exports.

Connect Your Hotmart Account

Authenticate your Hotmart data source in Kondado by entering your API credentials, allowing the platform to access your digital product sales and subscription information.

Configure SQL Server Destination

Enter your SQL Server connection details including server address, database name, and authentication credentials to establish the target location for your replicated data.

Select Pipelines and Schedule

Choose from the 11 available Hotmart pipelines such as Subscribers, Sales Commissions, and Hotmart Club data, then set your preferred update frequency to automate data delivery to SQL Server.

Try out all the features for free for 14 days