In our company, we used the solution to build a SnapLogic pipeline in a non-production environment. Presently, our company is releasing it to the production environment. We have used SnapLogic in our organization for integrations. An EDI pipeline is built first, and then SnapLogic is utilized to convert EDI format to JSON and vice versa.
Leveraging the internal systems in our company we are connecting to the SnapLogic API and sending the data, and then the converted files are obtained from SnapLogic.

SnapLogic
SnapLogicExternal reviews
External reviews are not included in the AWS star rating for the product.
The EDI format and performance need to be improved
What is our primary use case?
What needs improvement?
The biggest issue we have faced in our company with SnapLogic is regarding the EDI format. For instance, suppose if 20 EDIs are shortlisted then SnapLogic will convert and provide only those specific 20 EDIs. If a new version of EDI arrives later or if there is a need to use a different existing EDI version, then you need to get back to SnapLogic and complete the setup before initiating the pipeline.
For how long have I used the solution?
I have been using SnapLogic for a year.
What do I think about the stability of the solution?
I would rate the performance of the solution as two out of ten.
What do I think about the scalability of the solution?
Our company hasn't yet deployed the solution at the production end, so there are no active users. Due to its poor performance, our company is concerned about SnapLogic's scalability. Our organization adopted the solution's normal pipeline instead of the Ultra pipeline; the scalability of the normal pipeline is quite low. I would rate the solution's scalability as two out of ten.
How are customer service and support?
When communicating about the issues with the support team, they recommend using the Ultra pipeline, but it's too late for our company now, they should have suggested it earlier. I would rate customer support a two out of ten.
How would you rate customer service and support?
Negative
Which solution did I use previously and why did I switch?
In our organization, we had an internal EDI platform developed using MapForce, but there were some drawbacks, so we shifted to SnapLogic. Before shifting to SnapLogic, our company also tried to use Jitterbit, but it wasn't suitable for us.
How was the initial setup?
After setting up the pipeline for SnapLogic in our company, we found multiple bugs when the conversion process was initiated. The deployment process of the solution was complex.
One of the partners of SnapLogic was assigned to our company to assist in setting up the conversion pipelines; we did not have a good experience with the partners, and they were not friendly or gracious. SnapLogic recommends that a third party assist with the deployment. In our organization, the entire deployment process, including the pipeline building, took more than a year. The vendor handles the maintenance of the solution.
What's my experience with pricing, setup cost, and licensing?
From the ROI perspective, the price is extremely high. I would rate the pricing as one out of ten.
Which other solutions did I evaluate?
Presently, in our company, we are building an internal EDI conversion tool, we are planning to switch from SnapLogic to this internal product.
What other advice do I have?
In our company, we use the cloud version of SnapLogic as a SaaS platform, and additionally, Microsoft Azure is used as the cloud provider.
If the EDI conversion pipelines had been built properly, we could have implemented the solution in three months. Our company had to wait a year for the product setup to be completed. Based on my experience, I would not recommend SnapLogic to others. I would overall rate SnapLogic as two out of ten.
Which deployment model are you using for this solution?
Offers good UI, efficient and quick when it comes to integration and does not require much intervention from our end
What is our primary use case?
I work as a solution architect, mainly focusing on integrating new software entities. Due to a client's needs to evaluate products, SnapLogic was considered, and we conducted some Proof of Concepts and suggested its use.
So, our end customer is one of the medical equipment companies. They were looking for an integration solution, so we analyzed their requirements and determined what would best suit their business.
How has it helped my organization?
It is used for data integration projects. It is very efficient and quick, especially when compared to MuleSoft, which is a bit slower. SnapLogic had a good UI. The data we were dealing with was not extensive, so SnapLogic works well for our customers now in terms of usability and speed.
SnapLogic has the concept of pipelines, which is beneficial as it does not require much intervention from our end. If there are any minor changes needed, customers simply take a copy of the existing pipeline, customize it, and easily rebuild it. This feature is very useful for our customers.
Not much technical background is needed if we are working with SnapLogic. That is a good thing.
Coming from an integration background, it took me just one and a half months to understand it properly. However, someone new to the industry might need about three to four months to start building programs easily.
What is most valuable?
The best thing about SnapLogic is the connectors it offers and the support it provides to deal with the records. One use case involved fetching data from SAP ERP and sending it to Terradata. This process was a bit tricky with MuleSoft, but with SnapLogic, it was crisp and quick.
Despite having no prior experience in SnapLogic, we managed to build, test, and prepare it for release in just three hours, handling heavy data efficiently.
It's for CSV transformation, which is comma-separated transformations.
What needs improvement?
The problem is that SnapLogic doesn't offer a wide variety of connectors. For example, integrating with Salesforce is not that easy, unlike with MuleSoft, which is much easier and also provides a development kit allowing developers to customize or create their own connectors. But SnapLogic lacks this feature.
So, it's not easily customizable.
For very complex integrations, like those involving 10 input systems and 20 output systems with a variety of data transformations, I wouldn't recommend SnapLogic. You will feel lost somewhere.
When dealing with such complex integrations, you often encounter issues managing large datasets. SnapLogic recommends breaking the process into smaller pieces and then deploying them, but sometimes, our requirements are different and require handling multiple systems simultaneously.
In future releases, I would like to see better customization. Currently, we have certain connectors, and if we need to build on top of those— tailor them more closely to our business needs—then customization becomes necessary. But here, that process is a bit tricky. I want it to be simpler.
For how long have I used the solution?
I have been using it for two years.
What do I think about the stability of the solution?
I would rate the stability nine out of ten.
What do I think about the scalability of the solution?
It is a scalable product. I could easily manage it. So, I would rate it a nine out of ten.
We had enterprise businesses for SnapLogic.
How are customer service and support?
Some of my queries took some time to resolve, meaning we had to wait longer to get those answers.
How would you rate customer service and support?
Positive
How was the initial setup?
I would rate my experience with the initial setup an eight out of ten, with ten being easy. It is not a ten because when someone is trying to develop it, it takes time to understand their own specific keywords. They're not very standard. Initially, it takes time to set it up, but once it's set up, it runs very smoothly.
I did it on a hybrid environment where the customer used their AWS.
The deployment part is very easy. I would rate it a nine point five out of ten, with ten being easy. It just takes minutes.
You just need to create the pipelines. You can have the same pipelines in different environments. You just change the environment, and it quickly takes the values and processes them. There's not much else to do.
What's my experience with pricing, setup cost, and licensing?
I just evaluated the free version. Since SnapLogic started incorporating AI, particularly the AI version they're promoting, the price has gone up and is on the higher side. Although not much has changed, the cost has increased. However, when comparing it with solutions like Apigee or MuleSoft, it still offers better value.
So, it's still considered affordable.
What other advice do I have?
I would recommend using it. Just understand the requirement. If you need to develop something quickly and it's not too complex, then definitely opt for SnapLogic.
Overall, I would rate the solution a nine out of ten.
Which deployment model are you using for this solution?
SnapLogic IIP review : Best Integration tool
For non technical user it is quite easy to understand.
Features it provide for pipeline creation are very good.
Proper documentation is maintained about Snaplogic IIP.
Reliable and customer support is high rated.
It is less capable of handling a huge volume of datasets at a time.
Best data engineering platform.
Best Data Integration platform.
Not bad, but there are definitely better options
Easily used, confounding to master
this is what this product is, and how it works" is essential.
Snaplogic - Intelligent Integration Platform For Seamless Data Integrations And Transformations
There are numerous drag-and-drop snaps available to use suitable as per our requirement e.g Redshift Execute, S3 File Read, etc.
It is relatively easy to understand and implement our ETL pipelines.
- Snaplex Server Malfunctioning for Long Running pipelines.
- Frequent failures of Redshift Execute snap due to Connection Lost
- Sometimes it is hard to get the Root Cause of failures of pipelines from the error logs.
It is very helpful in terms of creating components to work with Ingesting File Data from Amazon S3 buckets to Redshift with minimal efforts thanks to all the easy-to-use snaps components available to complete the tasks.
With the other tools that we had been using, we were facing challenges in building complex Flow of pipelines and were hard to understand the flow of data. But, with Snaplogic it is now easier to understand and implement complex business requirements pipeline.