Overview

Product video
CData Sync is a universal data pipeline platform that enables automated, continuous data flows between SaaS, on-premises, and cloud applications and your choice of database, warehouse, or data lake. Replicate data for analytics, hydrate data lakes, migrate legacy workloads, or operationalize insights across business systems without coding or rigid pipelines. Sync supports more than 250 enterprise sources, including CRM and ERP systems like Salesforce, Microsoft Dynamics 365, NetSuite, Oracle ERP, and SAP; IT and collaboration tools like ServiceNow, Microsoft SharePoint, and Jira; financial applications such as QuickBooks Online and Sage Intacct; marketing platforms including HubSpot, Marketo, and Oracle Marketing Cloud; and leading databases and warehouses such as Amazon Redshift, Amazon S3 (with Parquet or Delta), Databricks, Snowflake, SQL Server, and PostgreSQL.
Why AWS users choose CData Sync:
- AWS-ready: Load to or from Redshift, land append-only Parquet or Delta data in Amazon S3, or integrate with hybrid AWS environments.
- Change Data Capture (CDC): Keep destinations updated in near real time without taxing source systems.
- Reverse ETL: Push enriched warehouse data back into operational systems to drive action.
- Point-and-click configuration: Build, schedule, and monitor pipelines with a no-code interface.
- Schema control: Define exactly how your data lands with full visibility and control. No black-box normalization.
- Enterprise-grade security: TLS/SSL encryption and granular access controls.
This listing is for the Professional tier, which includes support for up to 10 connections.
Highlights
- Replicate data from 250+ SaaS, on-prem, and cloud sources to Redshift, S3 (Parquet/Delta), Databricks, and more with no-code configuration and flexible deployment options.
- Keep data fresh with incremental updates and low-latency syncs. CData Sync supports Change Data Capture (CDC), hybrid environments, and high-throughput pipelines.
- Power AI, analytics, and operations with structured, query-ready data. Reverse ETL and append-only landing formats enable intelligent action across your AWS ecosystem.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Cost/hour |
|---|---|
m5d.large Recommended | $3.492 |
r5d.large | $3.492 |
r5d.4xlarge | $4.858 |
r5d.2xlarge | $4.251 |
m5d.4xlarge | $4.858 |
m5d.2xlarge | $4.251 |
c5d.large | $3.492 |
c5d.xlarge | $3.795 |
c5d.4xlarge | $4.858 |
c5d.2xlarge | $4.251 |
Vendor refund policy
We do not currently support refunds, but you can cancel at any time.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Additional details
Usage instructions
- In your web browser, type https://<this_instance_ip_address> . If the connection fails then you should either try again in a few minutes, or double check the Security Group (EC2 Dashboard > Network & Security > Security Groups) assigned to this image, ensuring that HTTPS is added and that your IP address is allowed.
- If you get a security warning in your browser, select the option to proceed. The browser is simply alerting you to the fact that the SSL certificate used by the site is self-signed (not signed by a Certificate Authority), and thus untrusted.
- To login, use "admin" for the username, and the instance id for the password, prefixed with "Sync26:".
For more details, please refer to https://cdn.cdata.com/help/ASN/sync/AWS-AMI-Edition.html
Resources
Vendor resources
Support
Vendor support
We provide standard technical support via email. We do our best to answer the messages quickly, so you can get your job done. Support is prioritized in favor of people who have purchased the premium support package and the product in question. support@cdata.com
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

Standard contract
Customer reviews
Automated data replication has streamlined analytics workflows and supports flexible ETL and ELT
What is our primary use case?
During the project, I used CData Sync majorly to achieve automated data replication, continuously moving data from source systems into a data warehouse we were working on at the time, and I also used it for ETL and ELT pipelines.
For the project, we were pulling CRM data from Oracle Eloqua into MySQL for analytics and BI reporting, and we made use of the native Eloqua connector which handled the integration seamlessly with operations that we set around it, so for the most part, we did not have to write code, as we just used their native picker and the custom settings to achieve what we wanted within the pipeline.
For the major part, we did not have to write code, which I found fascinating, as we had a good understanding of the source, the structure of the data, the source environment, and then the warehouse where we were sending the data, and given that understanding, we were able to use CData Sync 's features to connect to Eloqua and the other side, leading to seamless replication of data from the CRM software.
What is most valuable?
CData Sync offers source connectors that feel unlimited, as it has nearly every single connector needed, especially regarding databases and native software that help in collecting data, such as the unique Eloqua connector, and the interface does not require writing any code since it is primarily a point-and-click interface, allowing you to build, schedule, and monitor data pipelines without coding. I appreciate the Change Data Capture feature which replicates only what changes in your data since the last synchronization, avoiding automatic overwrites of entire tables. The Change Data Capture feature made a significant difference for us in efficiency because we did not have to worry about wrong data overwriting the correct data that had already been uploaded, and CData Sync just looked out for true changes that were made, requiring less time for uploads since it is not rewriting everything but including only the changes, thereby saving both resources and time in monitoring the whole process.
What needs improvement?
The first improvement I would like for CData Sync is the user interface, which sometimes does not allow for custom sorting of jobs, making pipeline management cumbersome at scale, especially when you want to do custom sorts or filters, plus the limited transformation capability means that since CData Sync is primarily a replication tool, complex transformations require external tools.
To add to that, the customization of the UI is sometimes limited when you want to build a custom job template, finding yourself restricted to their pre-built job templates without the ability to create a fully custom configuration independently.
For how long have I used the solution?
I used CData Sync for a project that lasted for four months, and that was where I used CData Sync.
What other advice do I have?
CData Sync offers ETL, ELT, and reverse ETL support, allowing us to replicate data from our CRM software into the target environment, and in a special case, we had to do reverse ETL where we pulled out data from the target environment and loaded it back into the CRM for a follow-up the sales team needed, with the data populated into the CRM software enabling the sales team to proceed with their campaign seamlessly.
Regarding productivity, during the project time, we were able to eliminate manual data extraction tasks since we did not have to write much code to monitor the pipeline or perform a lot of manual data connections and data mapping, and for cost savings, I relate that to time savings, as we did not spend much time and mental resources on new software or unnecessary expenditures; we focused our energy on ensuring the source and target environments were duly set up while deploying CData Sync to handle the connection and transmission.
Without CData Sync, I estimate that the project would have taken us about six or seven months, but given that we had CData Sync, we were able to conclude the project within four months.
In terms of governance and security for CData Sync's capabilities, transaction logging is built in, which logs all replication activities for audit trails, making it reputable in terms of governance, and connections to sensitive source systems are managed centrally within CData Sync's configuration, providing more transparency regarding role-based access and credential management, which is a positive sign for security; also, the on-premises deployment option gives us full control over where data lands, significantly aiding in monitoring data footprints of datasets and databases.
CData Sync is primarily a data movement tool rather than an AI inference tool, so discussing accuracy and reliability pertains to its data replication capabilities, which are very accurate in extracting data and replicating it in the target environment, and the Change Data Capture ensures that only changes are replicated, making it reliable; additionally, automated schema change management means that structural changes in source systems do not silently break pipelines, with the schema being adaptable and smart, so even slight changes in the source environment do not disrupt the pipeline at the target environment.
I would rate this product an 8 out of 10.
Data workflows have become automated and unified while support and security still need improvement
What is our primary use case?
The main use case is that the stack is MongoDB, with the main data source from Mongo. CData Sync comes as a third party that is layered on Mongo.
Power BI is directly connected to CData Sync , so we can stream the data from Mongo and visualize it.
The other unique thing about our use case is that aside from streaming live transactional data for informed decisions, we are in multiple markets at the moment in several African countries. This has been challenging because streaming data for different currencies and different local currencies, then accumulating everything in USD, makes everything look muddled up. However, it has been good with CData Sync since we can have everything in one currency.
What is most valuable?
The beautiful thing about CData Sync is that you can preview the data directly on their UI. The data that is settled in the database can be previewed on CData Sync before actually ingesting it into the BI tool.
That is one feature I appreciate. You can actually pick a particular column or drop a particular column. CData Sync's preview feature speeds up my workflow because at that layer of preview, I already know what I want into my pipeline and what I don't want. The SQL query at that level would also help to filter whatever I don't want.
What needs improvement?
There are times when you are streaming and trying to connect that CData Sync fails. However, the team has been very helpful. There is a particular technical support person that has usually come to my aid whenever there are issues. For improvement, I think the turnaround time for support can increase, especially on weekends.
I want to discuss the security of CData Sync. It is not something I actually have visibility to, but I think if CData Sync could give users the opportunity to put their own security layer on this, that would be beneficial. If CData Sync is compromised, who do we hold responsible? So security is an area for improvement.
CData Sync's interface is good. For integration with other tools, I think CData Sync could do well by integrating with other providers, especially AI agents so that one can easily integrate CData Sync to more agents out there.
For how long have I used the solution?
I have been using CData Sync for about four months.
What do I think about the stability of the solution?
CData Sync is stable. Our transactional data is not a lot so far, so I can say CData Sync is stable.
What do I think about the scalability of the solution?
For CData Sync data scalability regarding the increasing amount of data, our data is not a lot right now, so I think CData Sync handles it perfectly. Maybe later when transactional data grows significantly, we might be able to ask for better plans, especially regarding a scalable plan.
How are customer service and support?
Customer support is great. Sonja is a great helper. Technical support from David has been helpful. I can tell you that CData Sync is stable and their customer support is trying.
For customer support at CData Sync, I would give them an eight. I would not give them a ten because on weekends the reply is slow. Another thing I thought about is they need to consider users that are not in their region. I think it is a time difference issue.
Which solution did I use previously and why did I switch?
I did not purchase CData Sync through the AWS Marketplace . I saw CData Sync's ad on LinkedIn. I then reached out to a particular agent. That agent put me through their customer support team. That agent sent me an email and copied their team members. Since then, we have been discussing.
We had been doing everything manually. We saw that the manual way was not scalable. We then had to go the automation route.
How was the initial setup?
I think the startup cost is fine for us.
What about the implementation team?
I was able to integrate CData Sync easily with the help of CData Sync's technical staff.
What was our ROI?
Money has been saved with CData Sync. If we had gone through the route of a larger engineering effort for our pipeline, we would have spent more. In spending more, we might also have needed to employ a data engineer. So we have saved money on the technical side and on the staffing side. As an analyst, I was able to handle the integration.
What's my experience with pricing, setup cost, and licensing?
For startup cost, I think it is still fair. Although we are a startup with a lean budget, if the startup cost was expensive, we might not have considered CData Sync at all.
Which other solutions did I evaluate?
We thought about using Zapier or other automation tools. We could have automatically used Selenium to download and scrape web pages and then store them in Google Drive . That is how we did it before.
What other advice do I have?
I gave CData Sync a rating of seven because I have weighed the downsides and the upsides. CData Sync is solving my use case and I am able to use it, which already puts it past five. The usefulness and the simplicity in the technicality are things I also love about CData Sync, so that adds one to the five, making six. Looking at everything overall, including the support, the cost, and everything else, that makes it seven. I think seven is a good rating for me.
