SnapLogic

Our main use case for SnapLogic is the integration of student data, some finance data, and some internal Stanford data processes.

A specific example of how I use SnapLogic for integrating student or finance data is when new staff, students, or faculty join Stanford; they have to be added to different workgroups or their email has to be set up, so many processes are done via SnapLogic integration. On the finance side, it involves processing data related to the Office of Development, where some gift processing happens. Multiple teams at Stanford, including the School of Business, use SnapLogic for tasks such as booking meeting rooms.

We use SnapLogic for various integration purposes, including integration from Salesforce to Oracle, from flat files to Oracle, and integration from FileMaker to Oracle, among others. Although many more integrations are running as pipelines, these are a few I can recall as an infrastructure team member.

The best features SnapLogic offers are its ease of development for pipelines, where the authentication and account configuration are straightforward, and it allows for easy connections to sources and targets, as well as simple transformations and making multiple copies of the same data. I find the development part very easy, especially from an infrastructure perspective, since we host all Snaplexes on-premises servers; upgrades are seamless, and the impact on pipelines during rolling upgrades is minimal.

The development interface is user-friendly, making the process of connecting to sources straightforward, especially when setting up accounts using any Snap or API, which allows anyone to use it easily. Making configuration changes or moving servers between environments is also very easy.

SnapLogic has positively impacted our organization by providing an alternative to Informatica, which was challenging due to licensing and other issues. With SnapLogic, we can now connect to various SaaS and cloud products, and its usage has spread across different departments, making it a central tool for both on-cloud and on-premises ETL processes.

Areas for improvement for SnapLogic include enhancing the documentation, especially by providing more complex examples in each Snappack, to cover various use cases that different team members may encounter.

Another improvement I suggest is enhancing the monitor page on the dashboard to allow quicker and more efficient access to historical data, as it currently becomes slow and sometimes hangs when accessing older data.

I have been using SnapLogic for six to seven years.

I have been using SnapLogic for a while, and I believe the tool has become more stable, although there are still monitoring features I have had to build on my own. More robust APIs would assist anyone looking to automate processes.

My advice for others looking into using SnapLogic is to participate in training sessions provided by SnapLogic support, which can significantly help new users understand the UI and its functions through self-learning videos. I would rate my overall experience with SnapLogic a 9 out of 10.

SnapLogic serves as our primary ETL tool to replace legacy ETL tools and move data through our systems. Processing events data is our best example, where event information comes from third-party platforms that we need to incorporate into our internal data ecosystem.

SnapLogic has led to faster delivery of many pipelines that previously would have taken much more time to develop. Our organization can now process data faster and engage in many more business value-added activities that follow after importing data into our ecosystem.

SnapLogic has halved our pipeline delivery time. Given that we have fewer technical team members who are able to develop, this has been a really beneficial saving.

SnapLogic is very adaptable, and the best features are the Snap Packs that come included, the patterns, and the knowledge base, which allow us to quickly build ETL flows with all of the tools at our disposal.

These features have made everything significantly easier and smoother because we have templates to start developing standard pipelines. This creates a sense of reusability, allowing us to develop our own patterns and apply them. For instance, something that works for one third-party events platform but may require slight customization for another can be easily copied and tweaked to integrate a different source platform.

The AI Snap GPT function within SnapLogic has been really beneficial. It has allowed some of our developers who are relatively new to the tool to cut down their learning time and address the learning curve with the product.

More native support, particularly around the Agent Creator AI agent tool, would be beneficial. Expanding to have native Anthropic support would be beneficial for our organization specifically.

More native support for other large-scale LLMs such as Anthropic would be helpful. Additionally, more training to address the learning curve would be valuable. However, there is a good amount of information in the knowledge base, and Snap GPT has been extremely beneficial.

We have been using SnapLogic since the start of 2025.

SnapLogic itself has relatively good capabilities and output. Sometimes it does take a little time to learn exactly how to ask Snap GPT to get the right response, but this comes quite naturally after some trial and error.

SnapLogic is very scalable. We have been experimenting with broadening its use case and delivering an increasing level of jobs and concurrent pipelines, and none of these have faced any performance or reliability bottlenecks.

Customer service from SnapLogic has been excellent.

We previously used a solution called Scribe, which is an ETL tool that is no longer under maintenance support, and this was one of the reasons why we needed to switch.

We looked at the incumbent, Scribe, and we also evaluated Power Automate, but that did not solve all of our problems. We also looked at Talend, but the pricing was a limiting factor.

SnapLogic is a highly scalable, adaptive, and forward-thinking solution, particularly if AI agents is something you wish to develop. You can be certain that you will get a responsive customer support experience with a knowledgeable group who are very proactive about solving your business use cases. The flexibility of SnapLogic should broadly cover many use cases. I would rate this solution a 9 out of 10.

My main use case for SnapLogic is to load data into our CRM, which involves normal ETL and extensive data cleaning before putting it into the CRM.

A specific example of a project where I used SnapLogic for ETL and data cleaning is when we receive data from the bank and use that spreadsheet to find a contact in the CRM and then create income records on the spreadsheet and push it into the CRM. I use SnapLogic to execute the process, and it is all working well now, following business logic, and the process is very quick and easy.

These days we are trying to use SnapLogic to integrate it into an API to call those data and push it into the CRM instead of picking up files, and I think that is the next stage we are going into, but as it develops, we will see what more things we can use SnapLogic for.

The best features SnapLogic offers are the drag-and-drop features and the low-code capability, which is very good.

The low-code aspect of SnapLogic stands out for me because the interface is good, but the speed is exceptional. You do not need to know much to use it; I can easily train somebody without a background in coding to use a few Snaplex and connect them together with some minimal configuration and just get the job working. The ease of use is exceptional.

SnapLogic has positively impacted my organization because we have been able to cut down manual import into the CRM by over 50%, which means that the data quality is improving over time. This improvement means a lot of business processes that run on the speed at which data is available in the CRM are able to run better, improving the performance of our fundraising team in terms of reaching out to supporters and supporting supporters in any fundraising activity they want to do for us.

I think SnapLogic could be improved if the Snaplex has a way to change for people that want to write code, or to convert code to the Snaplex. There should be a way of switching the Snaplex into a base code so that you can add to the code and then save it, which would then be converted into logic on the front end. Having an alternative code injection into each Snaplex would be beneficial. For instance, in the Dynamics search Snaplex, sometimes you might want to search and filter by other entities. Right now you need to connect other entities together to accomplish that, but this should be possible if you have a way of injecting code and making SnapLogic run through the code and calling both entities together and doing the filter and pumping out results to be used, rather than each Snaplex doing only one thing.

I have been using SnapLogic for a little over a year now.

SnapLogic is stable in my experience.

SnapLogic's scalability has been very good, as we have not had any issues around scalability, whether it is a very small import or a very large import. We have not seen any depreciation of service speed due to load or quantity.

The customer support for SnapLogic has been great; they have always been there to take us through whatever we need.

Before SnapLogic, we previously used Tibco Scribe internally, and one of the main reasons why we switched is that Scribe was at the end of life and being discontinued. Additionally, Scribe is a bit rigid in terms of the way it works, and we needed something that does not require someone with technical knowledge to use.

We have seen lots of time saving in our approach using SnapLogic, and the number of people needed to do import is now reducing because we are able to automate everything, and things can be manipulated and tweaked as needed. This automation frees up a lot of time for other people to do something else, meaning we do not need to recruit more staff; we can use the hands internally to accomplish whatever we need to accomplish.

Before choosing SnapLogic, we evaluated other options, including Blackboard and a few others I have forgotten now.

My advice to others looking into using SnapLogic is that it is a very good product to use, but you have to consider your scenario and business case, and ensure that you research Groundplex and the Cloudplex so that you know which one is actually better for your organization and which one actually suits your organization in terms of implication, application, and the governance approach in terms of the UK approach versus the US-based product which SnapLogic is.

I have additional thoughts about SnapLogic, and I think it is been a great product, something I will recommend.

Regarding SnapLogic's AI capabilities, I think it has been good, but over time it will improve further; the accuracy of the result is good, but it can always be better.

I give this product a rating of 9 out of 10.