We performed a comparison between AWS Database Migration Service and Zapier based on real PeerSpot user reviews.
Find out in this report how the two Cloud Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable features of the AWS Database Migration Service are the ease of migration, beneficial storage system, security, and simple instance creation. Additionally, the cloud that is provided is more complete than other solutions."
"Support is helpful."
"The database migration services allow us to do real-time synchronization of on-premise and database to plan out our releases."
"The most valuable feature of AWS Database Migration Service is it catches all the history changes, such as inset, observe, and delete. It tracks everything."
"This solution is very good at mini-batch processing."
"AWS Database Migration Service is good for smaller workloads and provides compatibility."
"The most valuable feature of the solution is the one I use for report generation. The security risk is very low."
"The initial setup is very straightforward."
"There are a few valuable features, like the stability that it comes with and also the number of features that it offers. I've used other services like Pabbly, but they don't offer similar numbers of applications that Zapier has or allows to integrate with – it's maximum."
"Zapier handles everything under the sun that you would think you need in automation. It is the most mature integration platform and service on the market."
"The initial setup is pretty easy to do."
"Webhooks are the most valuable feature of Zapier."
"Zapier is user friendly and makes it easy to integrate different tools. It has a drag and drop functionality which makes it easy to connect environments."
"Zapier’s most valuable feature is its ability to interconnect applications or devices."
"We find it effortless to set up. We really don't have to do anything other than finding the application in the Zapier catalog. And as long as the application has been re-integrated into Zapier, they're able to then just provide the connection details and hook it up."
"With the previous CRM we were using – the Google Ads landing pages we had – we were collecting leads manually. That process was not efficient and took a sales team a lot of time to insert these leads manually. Currently, the process is smooth and we use Zapier to collect the leads for us."
"Support could be more expedient. Right now I am waiting on support for an extension."
"One area that AWS DMS can improve on is its conversion of data types. For example, in Oracle, you have a data type called RAW, but in PostgreSQL there is no such thing. Thus, AWS DMS doesn't know what type I want to use when migrating from Oracle to PostgreSQL, and when performing the migration, AWS DMS changed the RAW data type to the byte data type, which isn't what I wanted."
"The performance of data migration could be smoother."
"More endpoints need to be supported by AWS Database Migration Service. There's also a need for more control and transparency on the product, including better technical support."
"It would be helpful if the bandwidth could be independent of the network or if we could have a dedicated bandwidth for this product."
"Migrating from here and pushing the data from on-premise to AWS cloud is a big challenge and a few more services from AWS would be helpful. For example, we are currently using ILDB internet tools which move data from on-premise to the AWS cloud. A few more services would be really helpful for me to move the master data."
"The solution’s scalability and performance could be improved."
"Sometimes, the migration processes are not manageable"
"I would like to see them improve the Quickbase integration. Currently, it only allows triggering actions when records are added, but it would be more useful if we could also trigger actions when records are modified or deleted."
"I think that this solution should have more apps connected to it."
"With Zapier, improvements are required in the areas of concerns like bugs, ease of use, and documentation."
"System-to-system is fine, but when it comes to system-to-user, where Zapier is helping to communicate to a user, that's a one-way communication. If that user has to perform some action on that notification, the action isn't handled by Zapier. So there's no way to orchestrate that and it's very cumbersome."
"There is room for improvement in the support. They are not responsive, and they don't take much time to get resolved."
"At the moment, they allow a limited number of apps. I look forward to getting more apps for each package."
"Zapier could be a little faster, but that might not be possible. I would encourage Zapier to make more API endpoints for each application"
"My biggest concern with Zapier would be their pricing strategy."
More AWS Database Migration Service Pricing and Cost Advice →
AWS Database Migration Service is ranked 2nd in Cloud Data Integration with 27 reviews while Zapier is ranked 10th in Cloud Data Integration with 41 reviews. AWS Database Migration Service is rated 7.8, while Zapier is rated 8.6. The top reviewer of AWS Database Migration Service writes "A cloud solution for live replication but has stability issues". On the other hand, the top reviewer of Zapier writes "A tool for automation purposes requiring an easy initial setup while offering a very helpful technical support team ". AWS Database Migration Service is most compared with AWS Glue, Oracle GoldenGate, Qlik Replicate, Fivetran and Confluent, whereas Zapier is most compared with AWS Glue, Alteryx Designer, Coefficient, Tray.io and MuleSoft Composer. See our AWS Database Migration Service vs. Zapier report.
See our list of best Cloud Data Integration vendors.
We monitor all Cloud Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
