SnapLogic Reviews

It's similar to other tools like Boomi. But, it's a smaller player, not as widely adopted. SnapLogic may be easier to use, with less coding, but I think that more comprehensive solutions will handle a wider range of tasks. I found it difficult to achieve what I needed with SnapLogic.

We used SnapLogic to integrate various systems and some cloud systems, including our main CRM system and Microsoft Dynamics system. There were also HR and other specialized systems involved. Tools like Boomi can do similar things.

I'd install a local Snaplex (the SnapLogic runtime engine) to access local network resources. With cloud-based Snaps, you can talk to cloud or SaaS systems like Dynamics Online or Salesforce.

SnapLogic is more user-friendly than Boomi in terms of debugging. You can move the mouse to a place, and it will record and show the data easily. 

With Boomi, you have to double-click, open it, and then choose which information you want to see. Sometimes, you don't know what information will be displayed or what information you're not seeing. You have to have experience with Boomi to be able to understand, but with SnapLogic, it's working.

It offers the same core functionalities as other integration tools. I don't see a clear differentiation. They are all competing in the same market, targeting the same customer base. I think broader technology trends make it harder to see the distinctions that may have existed previously. So, we are moving towards Boomi. We're even exploring Microsoft Azure integration services now.

There is room for improvement in customer service and support. 

I don't think the support has better knowledge about technologies and tool support. There were lots of times when we had an issue, and it took me quite a long time to explain the problem. I feel like some of the support staff don't know their product well.

I have been using it for five to six years. 

In my opinion, SnapLogic is less stable than Boomi. We've had some issues when they upgrade to new versions. Since Boomi is a bigger company, I guess they have more developer support teams deployed. 

That's why Boomi has better support and better quality. That's why Boomi's quality is better than SnapLogic. This is just my opinion.

I was the only user in my company. I was the one handling the application. 

The customer service and support were okay. Honestly, I don't think the support has better knowledge about technologies and tool support. There were lots of times when we had an issue, and it took me quite a long time to explain the problem. I feel like some of the support staff don't know their product well. That's my impression. They have significant problems understanding and capturing the key points of the problem.

My impression is that the support isn't so knowledgeable. But in the end, by combining their effort with my effort, we were always able to fix the problem. They have to fix problems; otherwise, issues will persist.

I used Boomi AtomSphere Integration. It is a marketing leader. It is more comprehensive and can handle a lot of things. We could choose a fully cloud-based version of Boomi. If you want to connect with local sources, a hybrid model is needed.

For me, I found a lot of things difficult to achieve through SnapLogic. 

The deployment was very quick, and very easy.

If you want to achieve some basic or normal cloud integration and don't want to code, it's a low-cost way to get the job done. The benefit is that you don't need a programming background to work with it - just a quick solution.

The price of SnapLogic is much cheaper. 

It is an okay product. I would rate it a five out of ten. It is suitable for small company sizes. Maybe for medium-sized as well. 

But for enterprise businesses, Boomi might be a better option. 

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.

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. 

I have been using SnapLogic for a year. 

I would rate the performance of the solution as two out of ten. 

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.

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. 

Negative

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. 

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. 

From the ROI perspective, the price is extremely high. I would rate the pricing as one out of ten. 

Presently, in our company, we are building an internal EDI conversion tool, we are planning to switch from SnapLogic to this internal product. 

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. 

SnapLogic is a combination of API management and an ETL tool, like Informatica. You can use it as an ETL tool if you want. You can create your APIs, and manage them. You can keep it as a real-time pipeline. You can have it like a scheduled one. It has many flavors. You can try whatever you want. However, mostly we use it as a real-time scheduler.

It's a not-bad, low-code solution. You can directly pull, drag and drop. Even if you have some coding to be done, you can do it on your own. You can do it in Python. It's more developer-friendly, and development can be done at a very faster phase. Once you develop, on the fly, you can see all the data and how the data is getting transformed, and how data is available. 

It's a very easy-to-use tool. Most importantly, for any new developer, if you want to onboard, it's very easy.

The initial setup is simple. 

The solution has multiple dashboards. 

Right now, they have reduced their window period. You will have periodical upgrades from them. Previously, the application used to be down for a while. If you have any real-time pipelines, you need a bridge which is a little costlier solution. You'd need to have a separate server for batching, due to these issues. Otherwise, it'll go down. Your scheduler, you can rerun it, however, in real-time, your business cannot wait. That means you'll maintain a separate server. 

However, they have reduced this significantly, with downtime down to 15 minutes from two hours. However, if they could further reduce it, that would still be better. We'd like zero downtime in the future. 

In the past two years, we have seen tremendous growth. We expect very good things in the near future. 

They, however, do not have their own cloud platform for their iPaaS in the same way AWS or Azure does. 

I've been using the solution for around five or six years. 

It's very stable. We run it 24/7 and it has never failed anywhere - and we use it in multiple regions, including the UK, India, and the United Arab Emirates. 

The scalability is straightforward. They are also like one cloud provider. They have scalability. You can do even vertical or horizontal scalability. It's flexible in that sense.

While I'm not sure exactly how many people are using the product, my understanding is that it is around 100 or so. Anyone can use it, however, mostly, it's developers, senior developers, developers, and managers.

We have used technical support many times. We might have a unique use case where we need help from the SnapLogic team, or else there can be some bugs in the snaps, that we use to work with. This happened two years back. As of late, it's a very stable product. We don't need their interaction anymore, and we are also very much more mature here in our team. The need for them has lessened over time.

That said, while the SnapLogic technical managers are very good, the support model isn't great and should improve. 

Neutral

We did use a solution previously, however, we moved in the direction of iPaaS. This product is also less costly than what we were doing before.

They have very good competition right now. I'm using SnapLogic, however, I am ultimately using ADF also, Azure Data Factory. If something is in Azure, I can use it directly in Azure, instead of pulling data from Azure, moving it to SnapLogic's cloud, and then moving it to some other place. AWS has its own iPaaS tool, which is Glue. It works the same way as Azure Data Factory. SnapLogic is in between. It can connect to any cloud. 

The initial setup is very straightforward. You just need to provision some servers. It's a UE-based tool, so you don't need to install it. Nothing is required. It's ready anytime, anywhere, any place. This is the tag which is given by SnapLogic. As it says, you just need to get your server and put the SnapLogic application inside that server.

Once it is done, you can create your number of users, and they can develop with multiple access levels, like ACL in Azure. Everything can be configured. It's very straightforward. It's not like the older days when you created a software limitation. It's an iPaaS tool, it is an integration platform as a service.

We are using the enterprise version of the solution, however, I can't speak to how the licensing is arranged. I'm not sure if we are charged monthly or yearly or what we pay. It might be yearly and we may have a three-year contract with them. 

Quarterly, we will have a release. I don't remember the exact version number we are on. However, if there is a change, usually quarterly, they will upgrade your servers. It's almost automatic.

We have a provision where it will wait for some time. Once you give a confirmation, it'll be done. That is a hard limit, is also there.  A soft limit is when they advise "Upgrade by the first of August," for example, then, by the first of August, the changes will be there, however, your system will be running in the previous version. Typically, after a week or 15 to 20 days, it'll be a hard limit. It will ask you to upgrade your system.

If a company needs to use SnapLogic, first they need to consider why they need it. If you have all your applications moving from on-premise to cloud migration, this is one of the best tools for that. You will have most of your connectivity in the cloud, and if you want to do all the transformations in the cloud, and if you need to push more data, this is the best tool.

I'd rate the solution eight out of ten. 

My major use case for SnapLogic is for ETL. It's for data migration purposes. For example, I've used it to move data from SAP systems, across SAP systems, or across Salesforce systems. I've also used SnapLogic to integrate data from Workday or from some downstream enterprise specific applications to Workday.

Snaplogic has improved the data integration part of data engineering multifolds and now we have achieved a good rhythm in data integration consumption and security of the same.

What I found most valuable in SnapLogic is the ETL feature, particularly the Transform Snap Pack, for example, any kind of reading or writing on Transform Snaps. Other than that, all the third-party connectivity tools such as the SAP Snap Pack, Salesforce Snap Pack, Workday Snap Pack, even the ServiceNow Snap Pack, I find all those are pretty useful in SnapLogic.

One area for improvement in SnapLogic is the transparency in the flow of data. It needs to have more transparency. Right now, users only have a preview option at the end of any job flow, so at the end of any Snap Pack, there is a data preview option that lets you review the data and see how it's moving. What would make the solution better is more debugging and more access to change data from the preview panel or more functionality in terms of the preview option.

What I'd like to see in the next release of SnapLogic is better debugging of errors. Another feature I'd like to see in the solution is a more in-depth data preview because currently, it just shows you what happened to the data, rather than giving you a preview of how the data gets transformed.

I've been using SnapLogic for four to five years, and I've used it within the last twelve months.

SnapLogic is a pretty stable solution. Stability-wise, access, or any minimum downtime, the solution is pretty good. No complaints on stability.

SnapLogic is a scalable solution, and all the new changes they are bringing in are making SnapLogic a plug-and-play solution. It's good for very small use cases, or even for complex or big data management use cases. The solution is pretty scalable.

I've used the technical support for SnapLogic, and on a scale of one to five, with one being bad and five being excellent, I'd rate the support four out of five. I'm happy with the response time. The technical support team solved my issues.

Positive

My company decided to use SnapLogic because of its scalability, minimal setup, and cost effectiveness.

The initial setup for SnapLogic was pretty easy. There were self-explanatory documents available, so setting the solution up was pretty easy. The deployment took less than half a day.

I'm not aware of the licensing cost for SnapLogic. My boss takes care of it.

I'm using the latest version of SnapLogic, but I don't remember the version number.

In my organization, across the board, I'm not sure how many people use SnapLogic, but at my location, there are thirty to forty users of the solution. In terms of roles, all users are developers.

My advice to first time users of SnapLogic or to anyone looking into implementing it is that if there is a requirement to move data across systems or to integrate data across different systems, I'd definitely recommend SnapLogic, because it's a tool that's pretty easy to use. Much of it is only drag and drop and it is a low code tool. I'll very much recommend SnapLogic to others.

My rating for SnapLogic is eight out of ten. There are still issues for a user like me in terms of debugging in SnapLogic. It gives very limited options for debugging, and that's a major area to work on, so I didn't give it a perfect score.

My company is a customer of SnapLogic.

I used SnapLogic for ETL purposes, particularly for automating manual activities, for example, automating validation reports, checking and generating email, etc.

The business problems solved by SnapLogic involved setting manual work or manual validation that my company runs in the backend database which is connected using Snaps, then the validation is put as a query into these Snaps, which SnapLogic validates. The solution will generate the results, then sends a report to your email ID, so activities that used to be manual are now automated.

My company also used SnapLogic for ETL processing, particularly various inputs, CSV files connected with Redshift, including databases and adjacent files inputs. The solution can do file-level processing, take data from one data source, and put it into the other data source, so small ETL projects.

You can also take advantage of the SnapLogic pipelines. When a pipeline is created, you can get the URLs from that pipeline which can be triggered from AWS Lambda or any other triggering service. A vendor will provide a set of files that need to be processed. It's not a huge file as it's like transactional data that a vendor provides every week, so my company creates a pipeline where the team configures data in Lambda, so whenever a client drops that particular file for processing, the URL gets triggered, and the SnapLogic job will also be triggered. The SnapLogic job will pick the file from AWS from three locations or any source, then it does the transformation and loads it into the Redshift database of my company, and then the data will be used for several downstream and reporting purposes.

ETL is the major purpose for SnapLogic in the company where it does the transformation by fishing data from one source and putting it into the other. Automation is another purpose.

I found SnapLogic valuable and what I found most valuable about it was its ETL feature. I also found its automation feature valuable. It can be used for automating manual activities. It can be used as a middleware for certain transactional data processing and minimal datasets and ETL activities.

What could be improved in SnapLogic is that it was not capable in terms of processing a large number of datasets, but at that point, SnapLogic was evolving. It didn't give a lot of Snaps. I heard recently there are a lot of Snaps getting added and the solution was being enhanced, particularly to connect different data sources. When I was working with SnapLogic six months to one year back, I faced the issue of it not being capable of handling a huge volume of datasets or didn't have much of Snaps, and that was the drawback.

If there is any large number of data sets, that's based on or depends on your configuration. If it is a huge volume of data, other traditional ETL tools such as Informatica and Talend can process millions and billions of records, while in SnapLogic, the Snaplex fails or it returns an error in terms of processing that huge volume of data. Informatica, Talend, or any other ETL tool can run for hours in terms of jobs, while SnapLogic jobs fail when the threshold is reached. SnapLogic isn't able to withstand processing, but I don't know if that's still an issue at present, because the solution is getting enhanced and it's been more than six months to one year since I last worked with SnapLogic.

There are now a lot of Snaps getting added to the solution, and if it can overcome the limitations I mentioned, SnapLogic could be the go-to tool because currently, it's not being used as much in organizations. It's being used comparatively less compared to other retail tools.

I've worked with SnapLogic for over a year, but it's been a few months since I last worked with the product because I've switched companies.

SnapLogic is a stable solution, particularly for scheduled activities. You can schedule activities based on timing or triggers and the solution functions well. SnapLogic, in terms of performance, was good for minimal datasets or transactional datasets. It runs in a few seconds and depending on the volume of data, a job runs for hours, but when there's a huge volume of data, the job sometimes fails.

The cloud version of SnapLogic is scalable, but I haven't personally tried scaling it.

I have never reached out to the technical support for SnapLogic because I only reached out to the administration team of my company who reach out to the SnapLogic support team.

The setup and administration for SnapLogic were taken care of by a different team, but in terms of development work where the solution was involved, we can prepare pipelines and from a lower environment those can be moved to other environments, so deployment-wise, it was quite easy particularly when we can export the pipeline into an XML file and upload it into the other environments. That portion was easy and won't take up much time. Deployment activities for SnapLogic are quite easy and doable and won't take much time depending on the number of pipelines in the project folder.

I'm not aware of the pricing for SnapLogic because I'm just an application developer.

I evaluated Informatica and Talend.

I'm not sure which cloud provider was used by my company for SnapLogic, as that was maintained by a different team. I'm just an application user.

SnapLogic requires maintenance, but the administration work or maintenance work was done by a separate team, so I'm not quite clear in terms of maintenance. There are releases I'm aware of, where I would get a notification that the product would be offline for some time because the team will be doing certain enhancements. The administration and maintenance team is given information on the new releases for this version, so my team, particularly the application development team, would test it and make appropriate changes if required. Sometimes there's a scene where one snap was getting removed and you need to replace it with a different snap, particularly a newer release or version. SnapLogic has regular maintenance, release, or version handled by a different team within my company.

There are approximately thirty to fifty users of SnapLogic within the company. There's a team dedicated to administration activities in terms of deployment, maintenance, release activities, and providing access. There's a team of application developers which I'm part of that uses the tool to create pipelines, work on SnapLogic to develop apps, and do ETL transmission.

I didn't work with the solution daily. I only worked with it whenever required.

SnapLogic is used comparatively less by multiple organizations. I would opt for other traditional tools that have a lot of other features, which have a built-in cache for faster performance and can process huge ETL load volumes, such as Informatica, Talend, including PySpark. I would rate SnapLogic less.

My advice to people looking into implementing SnapLogic is that if you have basic ETL knowledge, you can do self-study on this. There is also documentation for every snap, so even if you don't know how to build pipelines or how to work on this tool, the documentation would be really helpful. There's a help button in the tool that when clicked, directly takes you to that particular snap's documentation. You can self-study and you can create it yourself. External training is not required, and that is one pro about SnapLogic. The UI portion is also good. There is a separate window for pipeline creation and you can go to the Snaps and folder areas separately.

I'm rating SnapLogic eight out of ten.

My company is a customer of SnapLogic. It is an AWS partner, but not a SnapLogic partner.

When we get a requirement from the business, we'll get the mapping documents. Based on the mapping documents, we'll map the issues.

Everything is very good.

It's good for mapping for the company.

We have a lot of use cases that we can apply to this solution. 

They are very good at building out new aspects according to customer requirements. 

We'd like there to be more ways for users to get more comfortable and have more experience with the solution to make it easier to use. It would help with referring issues, for example. 

When we get error messages, I'd like them to be more simplified and easier to understand. 

I've been using the solution for more than seven years.

The solution is very stable. People have been using it since 2013. It's quite mature and reliable. 

The solution is scalable. It's not a problem to expand it. When we were starting out, we had some issues, however, we are very comfortable with it now. 

We have between 100 and 250 people using the solution. 

We have our own internal team, which is great. SnapLogic support is okay. When we have issues that can't be fixed internally, we call them and they can help us. If there's an issue with the platform or an issue with the component they have to fix it. It takes some time. It would be nice if it could be a bit faster. However, when we deal with them, we have to wait in a queue and they sometimes have hundreds of customers they have to share their time with. They don't really have support set up to fast-track urgent issues, for example. 

Positive

We decided to choose this product over others as it was easier and compatible with all the endpoints. The usage was faster and it's easy to understand. However, it's up to the customer and is based on their needs. 

Some colleagues are also working on Azure. 

It's both easy and difficult to set up. Sometimes, there are some issues and something which we can't fix. Only SnapLogic can fix certain platform issues. Sometimes issues will be made by the developers, integration developers, et cetera. If we get an issue with the code or something else, then we can fix it, however. If it's something we can handle, then it is very smooth. Otherwise, we have to wait and reach out for help. 

The integration is straightforward, it's easy, and based on the use cases I have dealt with. The setup is very easy.

That said, you need to know what you are doing. There are different user roles that need to be taken into account. 

Often, to finalize the deployment, we need to raise a request and they can action it within a day or within a week. That's typically how long it takes to set up the user roles. 

The solution offers moderately priced licensing. It's not overly cheap or overly expensive. That said, since last year, they have increased the price. It's based on usage. 

We do find that it is worth the cost. However, it depends on how you use it. If they give a $1 million per year contract, and if you are not even sending one integration to live then it's not useful.

Running a POC is free.

I'm a customer and an end-user. 

I'm using the latest version of the solution and just upgraded last week. 

People should try the solution and try the free POC. People should try it and compare it to others, and, if it works within the environment and the necessary integrations, it's a good solution for them. 

Right now, the product is in the process of not really adding new things, but rather enhancing all of the features they have. They're also implementing machine learning and AI right now. They're also moving towards big data. 

I'd rate the solution eight out of ten. 

SnapLogic and Pentaho are tools I use collaboratively for data integration. I have good experience with Pentaho and SnapLogic for data migration from one database to another database.

The main use cases of the tool are for data integration and migration from databases.

In most of the use cases, my company uses SnapLogic for the migration of flat files to S3 and other databases. If my company gets flat files, like CSV, PostgreSQL, and XML files, from our clients, what we do is based on some of the business logic and the implementation they send to us. For my company to apply some business logic and implement it on top of the flat files, we will transfer the file using transform logic, after which we will migrate the data into the database, like Oracle or PostgreSQL.

There are features like CSV Parser, XML Parser, File Writer Snap, and File Reader that we use in our company with the separate functionalities provided by SnapLogic, which helps us to apply transform logic and migrate data.

My company has a licensed version of SnapLogic, so we have to pay for the product when we use it in our organization. Pentaho and Talend are ETL tools that allow my company to migrate the data within a fraction of a second using open-source products, not the paid version. In SnapLogic, my company uses the product's paid version, so we have to pay for license charges.

When compared with other tools, SnapLogic needs to be given a trial version or made available as an open-source product for simple migrations, which can be helpful for many users. In Talend and Pentaho, users can migrate data by just installing the software. I just installed the UI. SnapLogic doesn't provide any on-premises software, so users have only cloud-based software to use. Just giving the email address and creating a password is enough to configure SnapLogic. Tools like Talend and Pentaho need their users to indulge in manual installation since both tools fall under the on-premises software category. That is what is actually called on-premises software. It would be great if SnapLogic office separated software to manage small migrations.

I have two years of experience in ETL tools, including SnapLogic. My company has a direct partnership with SnapLogic Intelligent Integration Platform. My company has maintained an individual partnership with SnapLogic, specifically for Cloudplex, so we can connect with cloud services like AWS and Azure. My company has a separate partnership for SnapLogic Cloudplex so that we can connect with Snowflake and cloud services like AWS or Azure.

It is a stable solution. There are no glitches in the product. It is an easy tool to use. Users don't need to have separate knowledge to learn about the product.

With SnapLogic, users can find any errors and glitches. Once users find out the issues in the product, then they can solve the problems within the tool, which is a straightforward process.

It is a scalable solution.

Around seven to eight employees in our company use the solution.

For the installation part, if you have separate software within SnapLogic and you are able to download the tool from the cloud, it will be best.

One person can manage the product's deployment phase.

The solution can be deployed in five to ten minutes.

The product's deployment phase was taken care of by the in-house team.

SnapLogic's price is high compared to the other tools available in the market.

My company can suggest Talend or Pentaho for the banking domain since both are open-source tools. But in SnapLogic, there is a security process, and we also have a different authentication process. For banking domain and health insurance, my company suggests SnapLogic. My company usually makes suggestions to others based on the requirements.

I recommend the product to security teams.

I rate the overall tool a nine out of ten.

It's useful to move data from one environment to another one, for example, from one database to another one. I can also change data types, delete some dates, update data, and clean data, for example. So it's really useful for us.

It's easy to use, capable, and offers good performance. It's a good decision to use this product in any company.

I would like to see more performance-related dashboards, ones that display the cost of a pipeline, for instance. Also, it would be helpful to have management dashboards for overseeing pipelines and connections.

I used SnapLogic for two to three months. I used the latest version. 

It is a stable solution. 

There are around two to three people in my IT team using this solution. 

The customer service and support are good. 

I used Microsoft's tool. SnapLogic is more user-friendly than Microsoft. It's easier to understand what you can do in the app.

It is on a web interface, so I didn't need to download anything. I used the web interface.  I saw this web interface, and it only linked to my environment.

I used the free trial. You need to pay for a license to use SnapLogic. The pricing is based on the number of integrations you need and the volume of data you're processing.

Overall, I would rate the solution a nine out of ten.  I would recommend SnapLogic to others, but there are a few things to keep in mind. First, SnapLogic is not suitable for big data processing. Second, the pricing can be expensive, but it's generally in line with other iPaaS platforms.