SnapLogic

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.

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.

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.

In the past one year.

SnapLogic is very stable.

SnapLogic is scalable.

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.

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.

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.

We did a few evaluations including Azure Data Factory, but ultimately we chose SnapLogic.

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.

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.

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.

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.

I have been using SnapLogic for around four years.

SnapLogic is very stable, much more than before.

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.

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.

Previously, we were using microservices.

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.

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.

Before choosing SnapLogic, we evaluated other options, including Boomi.

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.

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.

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.

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.

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.

I have been using SnapLogic since 2020.

SnapLogic's stability is extremely stable.

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.

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.

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.

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.

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.

We evaluated other options before choosing SnapLogic, including MuleSoft and Boomi.

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.

My main use case for SnapLogic is dragging and dropping files from one SFTP to another SFTP.

A specific example of a workflow I set up using SnapLogic is picking up files from our SFTP which our system creates and drops there, then moving them across to our reconciliation team, a third party that does our reconciliation on an automated schedule.

The best features SnapLogic offers in my experience are that once you have your head around it initially, it is quite easy to use and can take away time from the development team because people with less technical skills can use it.

The learning curve at the start took maybe a couple of weeks just to know where things were, but there was a tutorial which helped with that, so for example, displaying the documents made it easier for less technical users.

SnapLogic has impacted my organization positively because many of the automations we made with dragging and dropping files used to be done by a human, so now there is less human error and it saves the team as it requires fewer people to do the work. There are two people less from a seven-person team now thanks to SnapLogic. I would estimate maybe an hour a day is saved, although I do not have exact numbers on time saved.

The only thing I do not prefer at the minute about SnapLogic is when I go into the monitor, it can be a bit slow, so when I am trying to diagnose why something went wrong and I am searching, it can take a bit of time.

SnapLogic could be improved in the monitor performance area.

I have been using SnapLogic for about two and a half years, the whole time I have been at Vitesse.

SnapLogic has been stable in my experience with no crashes.

Regarding SnapLogic's scalability, we have not needed to scale it as it has been stable.

The customer support for SnapLogic has been good as whenever we have raised an issue, I get a response within 24 hours.

I did not previously use a different solution before SnapLogic, as SnapLogic was already in use at this company before I got here.

The learning curve at the start took maybe a couple of weeks just to know where things were, but there was a tutorial which helped with that, so for example, displaying the documents made it easier for less technical users.

I have seen a return on investment with SnapLogic.

Regarding SnapLogic's AI capabilities, it works as expected.

I would describe my experience with SnapLogic's integration capabilities as very easy; the ones I have used have been very easy.

I would rate SnapLogic's documentation and learning resources as thorough and easy to get to when you click through the snaps to access them, so they were helpful when I was getting started.

Overall, the performance and speed of SnapLogic, aside from the monitor I mentioned, have been good because I have never had any issues.

The reliability and availability of SnapLogic have been good, as there was something on our side where the node restarted, but there were no major issues I have seen.

I would describe the ease of maintenance for SnapLogic as simple to keep things running smoothly.

My advice to others looking into using SnapLogic is to take your time and go through the tutorial when starting, just to get your head around everything before making a decision. I would rate SnapLogic a 7 overall.

The main use case for using SnapLogic is to integrate external systems to Syndigo. For example, we have XML files that need to be converted into our Syndigo format to create entities in the Syndigo system.

The best features are that we can quickly consume the Snaps which are already available, so we don't need to write scalable code. We can quickly integrate our systems via SnapLogic Snaps, and that speeds up our integration process.

The pre-developed Snaps are really helpful for both non-developers and developers, and that reduces the time for integrations significantly.

Implementing the pipeline quickly, rather than developing code, has impacted us tremendously.

If we develop the same integration using any of the latest technology, it would take a minimum of one or two months. Using SnapLogic, we can develop the same logic via Snaps within two or three weeks, which provides tremendous time saving as well as cost reduction.

When we face errors in the existing scheduler run, we cannot trace the logs. Adding more logs in the existing Snaps could make it much easier to debug errors.

If more logs were added to the existing Snap, users could debug errors and view log information more effectively.

I have been using SnapLogic for the last one year.

Customer support is really good.

Previously, we were using a private app via Java logic to integrate the system.

It has really saved our time when we are using SnapLogic integration systems.

We have not validated or evaluated any other options.

SnapLogic AI capabilities have good potential, particularly with the integration and automation features.

The AI provides accurate and useful outputs, especially for common integrations.

SnapLogic is easy to learn because SnapLogic itself provides documentation for each individual Snap, making it easy to read and understand the existing Snaps.

When creating the scheduler, we provided email notifications for successful scheduler runs or failed scenarios, so whenever we receive the email notification, we go and check the monitoring tool to debug the failed scenario.

It is easy to connect with external systems via the existing Snaps, something like the 365 Snap or the API endpoint Snap.

The documentation provided by SnapLogic is really helpful, and it is all up-to-date information.

SnapLogic has a mapper Snap where we need to configure the mapping, and for simple and collection mapping as well as complex mapping transformation, there is an individual syntax to transfer the data.

We have created multiple users to provide them access only to specific project access.

SnapLogic processes a large amount of data within a shorter period of time and has good scalability for handling large integration data. I would rate this review 9 out of 10.

I have been using SnapLogic for one and a half years on various multiple projects from the perspective of data migration and ingestions.

My main use case for SnapLogic is migrating some legacy product data to our newest products.

A specific example of a migration project I handled with SnapLogic involved our legacy product, which has multiple modules within it.

Regarding my main use case and other ways I use SnapLogic, we import the data as part of the ingestion process. We edit the data into an Excel tool in an Excel sheet and, using SnapLogic, read the data from the Excel sheet and load it into our newest product.

The best features SnapLogic offers in my experience include excellent REST APIs and batch processing, which is a standout feature.

Batch processing has helped us load around five to six lakh records within two to three hours, which involves loading thousands of records in a single shot. This helped our process reduce from eight hours to a couple of hours.

SnapLogic has positively impacted my organization because the professional services team has been running the pipelines and migrations very easily without any technical knowledge or dependency on technicalities.

This has made my team more efficient and freed up time for other projects. It significantly reduced the migration timeline for multiple customers, as there is no dependency on developers to run the migrations, allowing us to move to other particular migrations from the development perspective instead of running the same pipeline and staying on the same product.

API integrations are also really good to handle from a front-end perspective or any interface perspective regarding the features.

Regarding how SnapLogic can be improved, I think the Snaplex page can be improved without any downtime. There are some updates with SnapLogic that are not very stable before the release. This can be improved so that there will be no downtime impact for us.

I have been using SnapLogic for one and a half years on various multiple projects from the perspective of data migration and ingestions.

Regarding SnapLogic's AI capabilities, the accuracy and reliability of output are 50-50, but there is a lot of scope for improvement because I cannot rely on SnapLogic or SnapLogic AI or SnapGPT for the development which I am currently handling.

Regarding SnapLogic's AI capabilities, I think the governance and security are fine, but there is some scope for improvement with respect to security and access to personal level data.

The advice I would give to others looking into using SnapLogic is that it is a low-code tool and can be helpful for people who are just getting into software engineering or data engineering. This should help developers gain much confidence before starting with coding.

I am not really sure about the details of a business relationship with SnapLogic other than being a customer, but I am sure that we are a customer of SnapLogic. I do not know what kind of business relationship exists.

I would rate this product an 8 out of 10.

My main use case for SnapLogic is importing data to my CRM. I use SnapLogic by taking data from the JustGiving platform through an import file dropped into a specific location and loading it into my CRM.

The best features SnapLogic offers include its low-code nature, which makes it relatively easy for developers to pick up, and it has a wide range of connectors.

Reusability has been important for us with SnapLogic as well as being able to build MinePlexes and reuse them. We are also getting to grips with some of the AI capability.

SnapLogic has positively impacted our organization by allowing us to remove a big risk and cost in removing a legacy integration platform, and we have built the foundations to gain significant efficiencies in our integrations.

We want to get to grips with some of the automated testing functionality in SnapLogic, but we have not had the time to do that yet.

The main frustrations for us with SnapLogic have not been the technology, but the usual things of stakeholder capacity constraints and other hold-ups to the project.

One improvement that would be beneficial is better visibility of SnapLogic's environmental credentials.

I have been using SnapLogic for 18 months.

SnapLogic has been reliable for me with no downtime or disruptions.

SnapLogic's scalability as our needs grow or change is good.

The customer support for SnapLogic is very good.

I do not have any specific outcomes or metrics to share regarding time or money saved or how my team's workload has changed.

Learning SnapLogic for my team was fairly easy.

My experience with SnapLogic's documentation and learning resources is pretty good, although it always feels as though there is more to learn.

SnapLogic's integration with my existing systems and tools is easy and good.

SnapLogic's performance and speed when handling large data volumes are good. We have hit some snags, but we believe that is more on our CRM side than SnapLogic.

My advice to others looking into using SnapLogic is to go for it. I would rate this review as a 9.

My main use case for SnapLogic is integration with other systems, and I also use SnapLogic to replace a lot of our older systems that require integration.

A specific integration I set up with SnapLogic that made a significant difference for my team is called SGM, which is a Stanford Group Manager. It was originally written in Java and worked on a very old server, so instead of migrating the code and the technology to a new server, I redeveloped it using SnapLogic. Once I redeveloped it using SnapLogic, the integration part lagged a bit, so I still had to use some Java, especially for the integration with Active Directory. Even though SnapLogic provided resources and snaps for that, it was still inefficient.

Additionally, I had to integrate new harvesters, which are the logic side where they post events and process them. As SnapLogic matured, I rewrote part of that to spawn duplicate processes to execute and run a lot of the back-end integration, really cutting down on time, and as SnapLogic continues improving and I learn more about it, I continue to upgrade our current systems to make them more efficient and outperform a lot of our old systems.

One other benefit about my main use case with SnapLogic is the harvesters, which went through about four or five revisions before I created a standard template snap where I could use a property file to achieve the same information instead of repeating the pipelines or projects. Therefore, when someone does a request and they need this simple integration, I retrieve some information from a get and then post the information to a downstream system that could have multiple authentications, which I can now do all within a property file. This enables me to spin up a new harvester in SnapLogic within half a day, saving a lot of time.

I think the best feature SnapLogic offers overall is seamless integration. I basically only have to ensure I have all the right credentials to hook up a database, and therefore I don't have to write any of the JDBC that I had to do in Java for a connection. Other features I discovered include the versatility of authentication, though not all types of authentication are still available, and I look forward to seeing this improve so I can migrate other old applications over to SnapLogic.

SnapLogic positively impacts my organization by allowing me to do more application development integration in less time. However, when something brand new starts, there is still a big learning curve on how to implement it and streamline and use the features as best as possible. SnapLogic keeps improving, and as it improves, I have to go back and redesign slightly on our pipelines to make use of all these new snaps, leading to retrofitting that takes time.

I think SnapLogic can be improved by implementing more seamless logging of information. Currently, this is done through an error, but it would be best to have logging available on each snap that you can turn on and off, allowing you to configure a logging mechanism for where it logs. By having each snap available for logging, you can log all the information instead of creating a separate pipeline for logging.

Additionally, I suggest caching for snaps that are recursively called, particularly when logging in, authenticating, doing actions, logging out, and then repeating the process, which would significantly speed up operations, especially when querying an Active Directory because retrieving many members in Java takes about five seconds, whereas in SnapLogic, it takes a minute and a half for the same operation.

Regarding the new dedupe snap, I think the default setting should be changed from the current 80% match to an exact match, allowing for changes afterward, as I ran into issues during regression testing where a minor difference led to duplicates being flagged unintentionally.

I have been using SnapLogic for about seven years now.

SnapLogic is about 90% stable in my experience. There are times when snaps fail for unknown reasons, and sometimes after an upgrade, SnapLogic itself becomes unstable, but overall, it holds a 90% stability rate.

I believe SnapLogic's scalability is defined by our available budget. The more budget we have, the more resources we can obtain, hence allowing our pipelines and work to expand, making it challenging to assess without considering other external conditions.

I find customer support for SnapLogic to be top-notch, particularly with Dwayne. Most support from Zendesk has been very helpful, although some others are less so, as we often push SnapLogic beyond its limits, which leads to suggestions for improvements and inquiries about their design.

Overall, I would rate customer support ten out of ten. Due to Dwayne's involvement, I would even consider going past ten, given his strong interest in our work.

The solution I used before SnapLogic was Java, which was the only option available at the time for doing all the work.

I was not involved in the SnapLogic evaluation. When I joined, it was just in its infancy, and I went through the training while management made the decision to use it.

My advice for others looking into using SnapLogic is to anticipate a learning curve regarding the features currently available, as there are many ways to accomplish various tasks. It is best to take the training and engage with others who use SnapLogic to gather insights on achieving different functionalities since there is always room for improvement. I would rate this product an eight out of ten.