
SnapLogic
Data migration projects have saved time and cost but the interface still needs to improve for newcomers
What is our primary use case?
My main use case for SnapLogic is for different projects involving data migrations. We need to migrate data from our old SQL database to SnapLogic. I am mainly using it for this purpose and am currently learning the platform. Data migration is the primary project we are using SnapLogic for at this time.
How has it helped my organization?
SnapLogic has positively impacted my organization by optimizing time management. Previously, we were spending more time on these processes, but now we are using significantly less time compared to our previous methods. It has been very helpful in the management of time. Our customers are also happy with the results. SnapLogic is saving time and cost for us, which creates a win-win situation.
What is most valuable?
SnapLogic offers many valuable features including Snaps, which provides different methods, exception handling, error handling, and a good user interface. I find Snaps to be the most helpful feature. Snaps are excellent because they offer drag and drop functionality that we can use easily. We can utilize different Snaps for various purposes, which I have found to be helpful.
Regarding SnapLogic's governance and security capabilities, I believe they are very secure and good. The security is excellent. Regarding SnapLogic's accuracy and reliability of output, I find it to be reliable. SnapLogic uses AI power, so we can trust the output.
What needs improvement?
I feel SnapLogic can be improved, particularly on the user interface side. While it is good, I believe we can improve the GUI further. This improvement would help newcomers by making the interface more user-friendly. This is my suggestion at this time.
For how long have I used the solution?
I have been using SnapLogic for six months. I am relatively new to SnapLogic, having started using this technology just recently within the past six months.
What other advice do I have?
SnapLogic is a powerful tool that is easy to use. It is more beneficial, more secure, and more stable compared to other tools I have used previously. I can recommend this to everyone. I have rated SnapLogic a seven out of ten because there are some improvements that I feel need to be done, but otherwise everything is good. I chose seven out of ten for this reason since everything requires some improvements.
Reliable data pipelines have doubled weekly timesheet processing without extra staff
What is our primary use case?
My main use case for SnapLogic is data ingestion. We have lots of data, but the main one is connecting out to APIs and SQL databases, bringing them into all the various system sources that we have within the business.
A specific example of a process or workflow I run with SnapLogic for data ingestion is that we recently built a data lakehouse within Databricks. We use SnapLogic to connect to all of the system data sources, and with a little bit of logic, we create Parquet files for Databricks ingestion.
How has it helped my organization?
SnapLogic has positively impacted my organization in that unlike other tools that we have used, no one in the business really notices or worries that SnapLogic is handling data. We don't get failures, we don't get issues, and we don't get week on week issues with the processes; it just works.
This reliability has translated into measurable outcomes for my team. The amount of timesheets that we deal with now without issues week on week is probably double what it originally was. It has gone from 5,000 timesheets a week to 10,000 timesheets a week with no noticeable impact from the business.
What is most valuable?
The best features SnapLogic offers include a good range of connectors that is very broad. We have not found any systems that we cannot use SnapLogic to connect to either to pull data from or push data to. Additionally, SnapLogic has good professional services that are very supportive if we have issues or if we have use cases that we want to discuss with them to make sure that we are doing things in the appropriate way.
The support from SnapLogic's professional services has made a difference for my team and projects because they basically keep us on a solid footing. They make sure that we are not missing out on features within SnapLogic, and they are always open to discussing with us what we are currently working on.
SnapLogic integrates with other tools or platforms in my tech stack very well.
SnapLogic handles data transformation and mapping for my use cases very well.
I would describe the documentation and learning resources provided by SnapLogic as really good.
What needs improvement?
SnapLogic can be improved by not keeping some of the connectors that would be very useful as a premium connector.
I handle monitoring and alerting for my SnapLogic pipelines by noting that the issue with SnapLogic is that you have to be an environment admin to be able to see the monitoring. This makes it quite difficult to do it from within the software. We have to bring the alerts out into a SQL database and report from there.
For how long have I used the solution?
I have been using SnapLogic for four years.
What do I think about the stability of the solution?
SnapLogic is stable.
What do I think about the scalability of the solution?
SnapLogic's performance when dealing with large-scale or high-volume data processes is very good.
SnapLogic's scalability has never presented an issue, as our initial setup has been the same, and we have never had an issue.
How are customer service and support?
The customer support for SnapLogic is very good, as tickets get resolved within SLA.
I would rate the customer support on a scale of one to ten as a ten.
Which solution did I use previously and why did I switch?
Before SnapLogic, I previously used several solutions such as Power Automate and SSIS packages. We had many different processes trying to do the same job, so we were able to consolidate this within SnapLogic.
What was our ROI?
I have seen a return on investment. There are not exact metrics, but the fact that we can process so many without additional people in the business has been a bonus.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is generally good, but the frustration is that some of the snap packs that we would like are held behind a kind of premium additional cost, which is frustrating.
Which other solutions did I evaluate?
Before choosing SnapLogic, I evaluated other options such as Power Automate and PagerDuty.
What other advice do I have?
I would rate SnapLogic overall as a nine out of ten. I choose nine out of ten because it has been far better than anything else that I have used previously. The fact that it just works is a massive bonus, and the only mark that I have against it is that some of the connectors are an additional cost because they class them as premium.
Regarding SnapLogic's AI capabilities, from what I know, its governance and security seem to be very well thought out. I don't actually use the AI features very much.
SnapLogic is deployed in my organization in a hybrid cloud and on-premise setup.
It was fairly easy for my team to learn SnapLogic since it is low code, so it was not very difficult.
SnapLogic supports compliance requirements in my organization since we don't use SnapLogic to store any data, so there are no issues with that.
My advice to others looking into using SnapLogic is to look at the premium snaps that you know you think you need, not just the initial cost.
Automation has replaced manual banking file work and now empowers non-coders to handle data
What is our primary use case?
My main use case for SnapLogic is to automate SFTP pickups and banking integrations, and I also use it for data formatting, changing CSVs into different types of files, filling out data, and completely changing it for all sorts of data work.
A specific example of a workflow I automate with SnapLogic is when we receive a file from a bank about different transactions in US dollars and in Philippine currency as a text file in an old bank style format that needs to be converted into an Excel sheet for one of our other platforms.
In this example, I first transform the file and remove any unnecessary data. Since the file is a text file without proper spreadsheet formatting and no real columns, I must ensure that I am reading and formatting the file correctly into columns and rows so that it displays properly for our other platforms.
In addition to my main use cases with SnapLogic, I also use it in a couple of places to work with our internal APIs as a company, where clients want to provide us data, whether it may be a list of customers or a list of accounts that they work with, and they want to give it to us in a CSV format and do not feel comfortable using an API and calling it.
How has it helped my organization?
The process of transforming that file takes less than sixty seconds with SnapLogic, and before I started using the platform, we would have to do it by hand by copying and pasting content from the text file into Excel, which was a very manual workflow.
SnapLogic has impacted my organization positively by removing a lot of manual work from people who were doing that tedious work, allowing them to focus on tasks that require more skill and are better uses of their time.
While I do not have any cost numbers or time-saved numbers, I believe we went from approximately five or six platforms that we were using for different purposes to being able to use SnapLogic in place of those.
What is most valuable?
Some of the best features SnapLogic offers include the visual coding approach with small blocks that I can write without needing any programming knowledge, whereas a lot of what we were doing, if it was not done manually, would have to be done by writing scripts of some sort.
It has meant that getting new users into using SnapLogic has been incredibly easy, and while there is going to be a learning curve with every platform, SnapLogic has really simplified the process and has meant that people who would not necessarily have been able to do some of this work can be trained to do it because it is quite simple once they get the hang of it.
One feature that deserves a mention is that whenever I need to write an expression for any of my snaps, there is an autofill option that attempts to guess what I am working with, pulling data from any of the snaps to either side of it to try and determine what I am doing.
What needs improvement?
I do think some of the documentation could be improved as it can be a bit hard to parse, and sometimes there are simply not as many examples of things or ways to use some of the snaps as there could be.
The interface recently got an upgrade which was very needed because before it was very dated and a bit clunky, and it definitely looks a lot better now, and the speed has never really been an issue.
I think the documentation issue is what keeps SnapLogic from being perfect for me, along with some instances where snaps for things such as joining tables or filtering things do not work exactly how one might think they do intuitively.
For how long have I used the solution?
I have been using SnapLogic for about two and a half years.
What do I think about the stability of the solution?
From what we have experienced, I would think SnapLogic is stable.
What do I think about the scalability of the solution?
I think SnapLogic's scalability is pretty decent, but we have not had to scale it up massively since I am in quite a small startup, so I do not know if it is hugely applicable.
How are customer service and support?
Customer support for SnapLogic has been really good.
I would rate the customer support a nine on a scale of one to ten.
Which solution did I use previously and why did I switch?
I did not previously use a different solution before SnapLogic that was very similar.
Which other solutions did I evaluate?
I believe we also looked at Zapier before choosing SnapLogic, but our other options were mainly continuing what we were doing with manual and scripting work.
What other advice do I have?
I would give SnapLogic a nine on a scale of one to ten.
I think SnapLogic's accuracy and reliability of output is pretty accurate.
In terms of SnapLogic's AI capabilities, I think it is pretty good, but I am not particularly well-versed in that area, so I cannot give a very strong answer on it.
My advice for others looking into using SnapLogic is to think about what you are going to use it for because there are so many things you can do, and make sure you understand what they are before bringing it on board.
Integrated people and financial data have streamlined vendor reporting and ongoing ETL workflows
What is our primary use case?
My main use case for SnapLogic involves all the ETL applications where I need to get data from sources and then perform transformations and either send it to downstream applications within our firm or to any external vendors that need specific data sets.
For one of those ETL processes, I can give a specific example where some applications need data related to people and some of their transactions, which we hold in different applications. For people data, we use SnapLogic to connect to Workday and get their information such as first name, surname, preferred surname, and HR number, while their transactions, which are the things they actually work on, do not exist in Workday. These transactions are stored in a different application called 3E. In the same integration, SnapLogic gets people data from Workday and financial data from 3E, which is related to different users, and then we map them together by using joins and send all the user-related data along with their related financial transactions. We group them together, and each of the user data will be sent to an external vendor.
This main use case is our primary use case in most of the integrations.
How has it helped my organization?
SnapLogic has positively impacted our organization because over time, we have only started building more and more integrations within SnapLogic. Although about three or four integrations have been decommissioned, within that time span, we have built at least ten or fifteen more integrations, so I can see it is only growing bigger.
Regarding the outcomes I have seen, recently since AI tools have picked up, there was SnapGPT within SnapLogic, which understands everything specifically to SnapLogic, and that has helped me a lot. It also builds the pipelines for me and does the mappings when I use basic English to explain what I want as an output from the data that is going into the snaps, making it quite helpful in using SnapGPT.
What is most valuable?
The best features SnapLogic offers make it very simple to use, so it only took me around two or three months to get used to the interface, and in the past five to six years, I have noticed that there have not been many big changes. It is nothing very difficult to learn, as it has always been very simple with the interface and everything being quite easy to learn.
I would add that all the connectors we have include the basic set of Snap Packs, and I am very much familiar with them. Over time we did purchase some premium Snap Packs because we wanted to connect to different applications which were not offered by default, such as Azure Service Bus and Databricks, and we do have documentation available online, which helps us understand clearly without actually having to reach out to support to understand how to use them.
What needs improvement?
SnapLogic can be improved by generating SQL queries within SnapGPT, including the variables, as it would be very useful because lately, I have been using other AI tools such as Claude or ChatGPT to generate SQL queries. If SnapLogic SnapGPT can do that efficiently, then that would be very helpful.
It would be easier if there were a support chat option within the pipeline so that we do not have to raise a ticket on the portal to explain what is happening and then grant access. If by default, in the test environment and dev, not in prod, we could add a chat option where a live chat person can actually be contacted within SnapLogic itself, that would be very helpful.
For how long have I used the solution?
I have been using SnapLogic for six years.
What do I think about the stability of the solution?
In my experience, SnapLogic is stable.
What do I think about the scalability of the solution?
SnapLogic's scalability measures are evident as we use it for small integrations that run under thirty seconds and some integrations that run for about five to six hours as well. So far, I do not think anything has caused any issues, so it is stable. Scalability-wise, I think we can go from small minimum integrations to a massive one.
How are customer service and support?
SnapLogic customer support is quite helpful, and we have a customer success manager who increases the priority on our tickets when we say something is really important and we want a resolution as soon as possible. Overall, support and our CSM have been very helpful. On a scale of one to ten, I rate SnapLogic customer support a nine.
Which solution did I use previously and why did I switch?
Before SnapLogic, I do not think we used any other solutions or similar applications, as I believe it has been about eight years since we introduced SnapLogic. Prior to that, we had SAP and Workday, with all different applications sitting on their own without connecting many applications, from what I know. SnapLogic was the first application of its kind that we introduced in our firm.
Which other solutions did I evaluate?
Before choosing SnapLogic, I was not there eight years ago, so I would not know if they evaluated other options.
What other advice do I have?
SnapLogic is deployed in our organization where all our SnapLogic nodes are on-premises, so we have not migrated to the cloud yet. The advice I would give to others looking into using SnapLogic is that it is very simple to use. I understand this is a low-code platform, but being a low-code platform, it is quite efficient, and I could recommend it to anyone. I rate SnapLogic an overall nine out of ten.
Faster data migrations have transformed delivery times and now improve customer satisfaction
What is our primary use case?
My main use case for SnapLogic is creating pipelines for data migration projects.
A specific example of a pipeline I have built for a data migration project is when we have our old product in a different technology that we are moving to the new product. For that, we are moving the data from SQL to the Next Gen SQL database. We are creating pipelines through which we are moving the data from the old product to the new product.
As of now, we are only using SnapLogic for data migration projects.
How has it helped my organization?
SnapLogic has positively impacted my organization in terms of revenue and customer satisfaction.
The faster delivery is one significant point, and our customers were very happy. Earlier, we used other tools that took around a year, and because of SnapLogic, we were able to complete tasks within months, so they were very satisfied with this tool.
What is most valuable?
The best features SnapLogic offers include various Snaps we use, such as Get, Get Post, and error handling, which is a very good feature. Error handling allows us to easily identify if we have any errors in our migration pipelines.
The error handling feature has helped me during my migrations because when we moved a lot of data, we opened our error log and could easily identify all the areas that had errors, which was very helpful for us in resolving the issues.
There are many features that are truly helpful, including Union, Joins, and various Snaps, so everything is very useful based on our project, and it really helps us speed up our work.
Regarding SnapLogic's governance and security capabilities, I think they are very good compared to others; there is no doubt about security, as it is a very good tool for security.
As for SnapLogic's AI capabilities regarding accuracy and reliability of output, I can say we currently have eighty percent reliability and accuracy, which I think is good, and it would be better if we could improve more, but currently it is eighty percent from my perspective.
What needs improvement?
Although SnapLogic is already a very good tool, it can be improved by making the GUI part, particularly the user interface, more usable, which would be more helpful for users.
Apart from that, I think it is fine and good, and once we use it more, I will provide feedback on other things as well.
As of now, I do not have any other improvements for SnapLogic that come to mind, but once I think of something, I will surely update.
For how long have I used the solution?
I have been using SnapLogic for the past one year.
What do I think about the stability of the solution?
SnapLogic is very stable.
What do I think about the scalability of the solution?
SnapLogic's scalability is excellent; we can easily scale, and it is straightforward to do so.
How are customer service and support?
The customer support is very good; we can easily access the support team on demand whenever we need help, and they are helpful.
I would rate the customer support ten out of ten.
Which solution did I use previously and why did I switch?
I previously used a different solution, specifically the SSIS tool, which is a Microsoft tool, and now we have switched to SnapLogic.
What was our ROI?
I have seen a return on investment; although I do not have specific numbers, we saved time by completing tasks in months instead of years, which indicates that if we saved time, we obviously saved money too.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is such that as a developer, we are not aware of much of these things; we are more focused on the technical side.
Which other solutions did I evaluate?
Before choosing SnapLogic, we evaluated other options such as Azure Data Factory and AWS Glue, and ultimately we found SnapLogic very helpful, so we opted for that one.
What other advice do I have?
My advice to others looking into using SnapLogic is to switch to this tool, explore various features, and it will be helpful; it is a good tool for them to choose. I would rate SnapLogic an eight out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Data migrations have become faster and training new team members is simple and efficient
What is our primary use case?
My main use case for SnapLogic is performing data migration. A specific example of a data migration project I've done with SnapLogic involves dealing with the EHR system, where we are using SnapLogic to migrate our environments, and we have the migration projects as well. Along with SSIS, we are working with SnapLogic, and we basically deal with health and safety.
What is most valuable?
I feel amazed to provide feedback on this particular tool for our main use case of data migration, as compared to any other SSIS or migration tools. The drag-and-drop feature that SnapLogic provides and the recently introduced SnapGPT are really helping us in our daily needs, and that is an amazing thing.
In my experience, the best features SnapLogic offers include its logic capability and an abundance of connectors with no limitation on input connectors, and I mainly want to highlight SnapGPT. Regarding the features of SnapLogic, I feel it is up-to-date in the market and has everything at this point in time.
SnapLogic has positively impacted our organization by enabling us to reach our delivery within our timeline. Moreover, it is easy to train any new interns or newcomers who are transitioning from other technologies, as they typically work in different cloud domains. It is easy to adapt.
The impact on timelines and training is noticeable, as both new joiners training and the knowledge transfer transformation to other teams are easy to adapt, which I want to highlight. Secondly, the drag-and-drop method and support for numerous features mean we do not need to do major manipulations for this kind of activity, which positively affects the delivery timeline.
What needs improvement?
Regarding improvements for SnapLogic, I feel the new GUI should be more readable for my team, as we find ourselves needing to zoom in and zoom out when there are too many things on the screen. I personally believe that if they enhance the GUI effect, it would be easier and handier for users. The GUI part is the only improvement I feel is necessary for SnapLogic; other than that, I find it awesome.
For how long have I used the solution?
I have been using SnapLogic for close to four years.
What do I think about the scalability of the solution?
When it comes to handling large volumes of data or high-throughput workloads, I have mixed opinions. We are sometimes able to manage huge amounts of data, but at other times, the pipeline execution feels a bit slow with large volumes.
What other advice do I have?
SnapLogic's integration capabilities with other tools or platforms are quite good as compared to other migration tools, where scripting is often necessary for handling use cases. SnapLogic provides many features without enforcing that we write or script on one particular page.
SnapLogic's flexibility in handling different data formats or sources is excellent. I find SnapLogic's monitoring and alerting features very helpful for our team, as we rely on them completely when working with production data to find any error messages or to obtain any statistical information.
Maintaining and updating pipelines in SnapLogic is easy compared to any other tool, from my personal perspective. SnapLogic's error management and troubleshooting capabilities are helpful for my team, as the ability to read the error log itself aids us. When we validate or execute pipelines, the error message pinpointing the exact issue rather than generalizing is really supportive.
My team reported that with their experience on other tools, onboarding new users is not taking too long; it generally takes about one to two weeks to integrate them into production projects. I rate this review an eight out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Secure data migrations have become faster and logging now simplifies error resolution
What is our primary use case?
My main use case for SnapLogic is for data migrations, where I am building pipelines. A specific example of a data migration project I handled with SnapLogic is moving our legacy product, EHSS Pria, to the new one by building pipelines with the base being the SQL database.
What is most valuable?
The best feature SnapLogic offers in my experience is logging, which is a great help in my projects. The logging feature is helpful because I can easily identify errors in our pipelines.
SnapLogic has impacted our organization positively as it is a great help for us. I am easily able to migrate the complete project without many difficulties. I saved time as a specific outcome, and it is easy to do.
What needs improvement?
I do not have much idea on how SnapLogic can be improved, but UI-wise, if the user interface is improved to be more user-friendly, it would be more helpful.
For how long have I used the solution?
I have been using SnapLogic for the past one year.
What do I think about the stability of the solution?
SnapLogic is very good and stable.
What do I think about the scalability of the solution?
SnapLogic's scalability is good and scalable.
How are customer service and support?
Customer support is nice, and I do not have any concerns from that side. I would rate the customer support a 10 out of 10.
Which solution did I use previously and why did I switch?
Earlier, I was using SSIS packages, but I switched to SnapLogic because it was not that much secure and governance-wise, it was not that good. I moved to SnapLogic due to its security features.
What was our ROI?
While I do not have specific metrics, my organization definitely got the benefits because I was able to deliver the project, and they received a good amount from the customers as I completed a few projects through SnapLogic.
Which other solutions did I evaluate?
I did evaluate a few other options, such as Azure Data Factory, but at last, I chose SnapLogic.
What other advice do I have?
My advice to others looking into using SnapLogic is to use it because it is very good for their company, especially security-wise, as customers focus more on security features. It has very nice security features, so compared to the other tools, it is a good choice if they choose SnapLogic.
SnapLogic is a very good tool; usability-wise, it is excellent as well. Learning-wise, I can easily learn it, and if someone has worked on any other data migration tools, for them, it is very easy to learn SnapLogic. It is really helpful for their organization and learning purpose, and it is a demanding tool, which is very good for their future professionalism.
Regarding SnapLogic's AI capabilities, I think its governance and security features are very good. The accuracy and reliability of output is around 80%. I would rate this review a 9 out of 10.
Logging has simplified complex data migrations and supports secure project delivery
What is our primary use case?
For data migrations, we are building pipelines with SnapLogic. We have our legacy product, EHSS Pria, and from there we move to the new one by building pipelines with the base being the SQL database, which we handle with SnapLogic. I have provided details about my main use case and ways I am using SnapLogic.
What is most valuable?
Logging is the best feature I found with SnapLogic, and it is a great help in my projects.
We can easily identify the errors in our pipelines with SnapLogic's logging feature, making it very helpful for my projects.
SnapLogic is a great help for our organization, and with it, we are easily able to migrate the complete project without much difficulty.
We saved time with SnapLogic, and it is easy to use.
What needs improvement?
I do not have much idea on how SnapLogic can be improved, but from a user interface perspective, if it were improved in a more user-friendly way, it would be more helpful.
I do not have any suggestions other than that regarding SnapLogic.
For how long have I used the solution?
In the past one year.
What do I think about the stability of the solution?
SnapLogic is very stable.
What do I think about the scalability of the solution?
SnapLogic is scalable.
How are customer service and support?
Customer support with SnapLogic is nice, and we do not have any concerns from that side.
I would rate the customer support of SnapLogic ten out of ten.
Which solution did I use previously and why did I switch?
Earlier we were using SSIS packages, but that was not as good from a security and governance perspective, so we moved to SnapLogic due to its security features.
What was our ROI?
We do not have specific ROI metrics, but as we were able to deliver our project through SnapLogic, our organization certainly got the benefits and received a good amount from customers as we completed several projects.
Which other solutions did I evaluate?
We did a few evaluations including Azure Data Factory, but ultimately we chose SnapLogic.
What other advice do I have?
I advise others to use SnapLogic as it is very good for their company. Security-wise, customers focus more on security features these days, and SnapLogic has very nice security features, making it a better choice compared to other tools.
SnapLogic is a very good tool, and from a usability perspective, it is excellent. Learning-wise, we can easily learn it. If someone has worked on any other data migration tools, learning SnapLogic is very easy, and it is truly helpful for their organization and learning purposes. SnapLogic is a demanding tool, which is good for future professionalism.
I would rate this product nine out of ten.
Automation has transformed order to cash and now connects our systems in minutes
What is our primary use case?
My main use case for SnapLogic is integrating multiple systems.
For integrating those systems, I am using SnapLogic to integrate the whole order-to-cash flow where the quote originates or an opportunity originates from Salesforce, goes through a whole lifecycle with SAP and multiple internal systems, and comes back to Salesforce as an order for revenue generation.
In addition to integrating the whole order-to-cash flow, I am using SnapLogic to connect multiple systems including multiple APIs, DBs, MySQL DBs, Cloud Spanner DBs, GCP, Pub/Sub, Vertex AI, and APIs.
What is most valuable?
The best features SnapLogic offers include the inbuilt Snaps which you can use to create connections between multiple systems, and I would say that is one of the best features. The UI is very intuitive.
What I appreciate about the Pin Snaps is that they help me identify the correct Snap for each and every integration, and it is easy to drag and drop the Snaps into the canvas, which speeds up the integration considerably faster than traditional coding.
SnapLogic has positively impacted my organization by helping me increase revenue substantially by automating the flow between the order-to-cash, which I have already mentioned.
Since using SnapLogic, I have seen specific outcomes where creating an order or opportunity in Salesforce and syncing it to SAP, which used to take around a day to complete, is now being done in minutes.
What needs improvement?
SnapLogic can be improved, but as a product, it is a mature product now compared to what it was four years ago, and the team is improving with every release, so I am satisfied with that.
Even if it is a small thing, I have asked them to create a new public API to create pipeline versions programmatically, rather than creating it manually, as that will help us in our CICD process.
For how long have I used the solution?
I have been using SnapLogic for around four years.
What do I think about the stability of the solution?
SnapLogic is very stable, much more than before.
What do I think about the scalability of the solution?
SnapLogic's scalability on the cloud is very good, as I have seen nodes spin up automatically, and on every restart, a new node is spinning up; scalability on Groundplex is also fair, but it involves a few manual activities.
How are customer service and support?
I would say customer support is on point; whenever I raise a query, they respond properly, and if I ask for a working session, they are always ready to hop on a call and help us with the issues, resolving it within a day or two maximum.
Which solution did I use previously and why did I switch?
Previously, we were using microservices.
How was the initial setup?
My experience with pricing, setup cost, and licensing was very smooth during negotiations with the team, and we recently renewed our contract, so it was a very smooth process overall.
What was our ROI?
I have seen a return on investment, as previously there were around five to six developers, but now we are using only one to two developers, which is a great return on investment.
Which other solutions did I evaluate?
Before choosing SnapLogic, we evaluated other options, including Boomi.
What other advice do I have?
I would rate SnapLogic a 10 out of 10.
I chose a 10 because SnapLogic helps me automate multiple things, and I have automated a whole bunch of flows using SnapLogic that reduces much of my time and effort, which is why I gave it the highest rating, along with its ease of use.
Regarding SnapLogic's AI capabilities, I think its governance and security are good, as every chat is new and, similar to ChatGPT chats, every time I open a session, it is new and the previous sessions are not saved.
For SnapLogic's AI capabilities, I would say its accuracy is around 85 to 90 percent, and reliability is also around the same, meaning I cannot blindly trust the output and should always review and improve it if required.
My advice to others looking into using SnapLogic is that it is a very intuitive platform that is easy to use and set up, with a lot of capabilities to integrate with multiple systems, and with its AI capabilities, it has gone one step further as well.
Citizen developers have transformed integrations and governance across our data landscape
What is our primary use case?
SnapLogic is used within my team for scheduled integrations of software, ETL loads, batch integrations, and real-time integrations between one of the main systems, Salesforce, and our more traditional SQL databases and Oracle Fusion ERP platform. We connect to mainly structured JSON data or semi-structured data within SnapLogic.
How has it helped my organization?
SnapLogic has positively impacted our organization by reducing my need for an external developer to build integrations; we can now handle that within the team. There is definitely a monetary value saved, and it has also positively impacted the performance of the technology and operations teams to monitor all these integrations in real time. We can monitor the whole performance of the application in one layer. We have a dedicated team to monitor that, while also having federated teams able to build their own pipelines, linking up with the centralized SnapLogic team, which gives us the ability to work really effectively.
Our internal teams have built about 15 integrations within the Salesforce team alone, and across ITV, we have over 100 integrations being built. The savings are in the tens of thousands of pounds.
What is most valuable?
The best features SnapLogic offers include its user interface, which is really intuitive to use. It is easy to see exactly where the bottlenecks are when building a new pipeline, what is taking a long time, and to fine-tune those bottlenecks as well. The account management and the support we receive is pretty good; we really feel as a partner across ITV's business. The user interface is the main thing; it is just really intuitive, and many of our teams who are not traditional developers or integration experts can pick up the platform and become citizen developers across ITV.
The intuitive user interface has significantly impacted our teams and workflows; we have basically eliminated the need to use statements of work and external contractors to build integrations. Now, the Salesforce Administration team can build integrations as a first port of call, and we are hoping to expand this to other support users from other teams to manage and build more integrations.
The mix of connectors SnapLogic offers is impressive; the bespoke connectors are really easy to use. For example, we use the Salesforce connector, which is a premium connector, but it is super easy to use and comes with a range of logical Snaps that are easy to use. This makes it really quick to build the pipeline, so we do not have to use standard REST connectors; it is great.
What needs improvement?
To improve SnapLogic, the error messaging functionality needs enhancement; when there is an error with a pipeline, sometimes the errors are a little generic. Some sort of recommendations on how to fix these errors would be more useful to the team. A little more in terms of testing features and unit testing functionality would also enhance our experience, but generally, we are very happy with the product.
I prefer that many of the training courses for support be much more publicly available so that anyone can train up on the platform without having to access SnapLogic University.
For how long have I used the solution?
I have been using SnapLogic since 2020.
What do I think about the stability of the solution?
SnapLogic's stability is extremely stable.
What do I think about the scalability of the solution?
We have had to scale up or down with SnapLogic; for example, we have needed to increase nodes when more data goes through. Our account manager works with us very well to scale up temporarily for a project, showing that it is really flexible in that area.
How are customer service and support?
The customer support from SnapLogic is really good. We have not had to use them too much because we have an internal support team that handles specific issues. When we have used their forums, they are very helpful, and when we have had to escalate issues with our account manager, we have always received a good response.
Which solution did I use previously and why did I switch?
Before SnapLogic, we used Dell Boomi for our Salesforce integrations, and we switched because other parts of the business were considering SnapLogic. When I looked at the user interface, I thought it was a no-brainer to move to SnapLogic; it seemed way more intuitive to use, and we were at the early stage in our Boomi journey, so it was easier to make that jump, and we are really happy we did.
How was the initial setup?
My experience with SnapLogic's pricing, setup cost, and licensing is that it was reasonably transparent. That is handled by a different department, but I look after the Salesforce connector side of things, which has also been straightforward.
What was our ROI?
We have seen a return on investment in terms of increasing the use of citizen developers and not having massive amounts of legacy unsupported integrations. This shift allows different people within the business to pick up integrations more easily, saving time and increasing governance around our data, our integrations, and our tech infrastructure.
Which other solutions did I evaluate?
We evaluated other options before choosing SnapLogic, including MuleSoft and Boomi.
What other advice do I have?
My advice for others looking into using SnapLogic is to start small and build it out. Get buy-in from different parts of the business rather than focusing on just one small team. Try to establish a federated model of citizen developers paired with a centralized model of administrators to oversee the platform and ensure there is a proper framework and guidance for building. You do not want people building things that take up all the memory usage across different pipelines. Start small, build up, get feedback from different people, and build iteratively. I would rate this product a 9 out of 10.