SnapLogic

My main use case for SnapLogic involves migrating data from legacy to the latest product. We are migrating heritage products to the latest products using SnapLogic.

One specific example of how I used SnapLogic in these migrations is that we take data from the source using SQL views, perform some transformations in SnapLogic, and once transformations are completed, we move data into an interim database, and from there we push that data to the target system using APIs.

The best features SnapLogic offers include being lightweight and easy to integrate, allowing us to easily move data from source to target. Compared to other tools I have used, such as SSIS which is quite complex, SnapLogic has straightforward snaps that allow us to easily join to other snaps and push the data.

Additionally, SnapGPT is one of the best features currently, as it helps us review existing pipelines and obtain documentation and test cases from SnapGPT.

SnapLogic has positively impacted our organization, as we are using this tool to migrate existing legacy products to the latest products, which has also increased our revenue.

Using SnapLogic saves a lot of time when we develop pipelines. Once we hand over those pipelines to the professional services team, they run them to migrate the legacy products to the latest products, which takes one or two days. Importing data from Excel systems, especially when dealing with thousands of records, takes minimal time thanks to SnapLogic. Customer satisfaction improves as professional services teams successfully migrate legacy products to the latest ones.

SnapLogic currently offers SnapGPT with more capabilities compared to earlier versions, but there is still room for improvement compared to other AI tools, particularly in areas such as viewing historical data and automatic file reading which would be very useful.

The interface still has options for improvement. While it has been enhanced in recent versions, it is often difficult to identify snaps when developing large pipelines, requiring a lot of zooming. A simpler option to see the snaps would be beneficial.

After execution, it is challenging to know how much data has been processed, and there is a need for better AI integration since it lags behind other tools.

I have been using SnapLogic for around two years.

SnapLogic is stable in my experience.

SnapLogic's scalability depends on how we configure the Snaplex. If there are options to scale up or down on demand, that would definitely be a great feature for SnapLogic.

I can give 70 out of 100 for customer support.

I previously used SSIS before switching to SnapLogic.

I did not switch from SSIS to SnapLogic intentionally. Rather, after building the data marts with SSIS, we had the opportunity to work on SnapLogic.

I have seen a return on investment with SnapLogic, particularly because we are successfully migrating legacy products to the latest products, which increases our revenue.

I was not involved in the pricing, setup cost, and licensing, so I cannot provide details about that.

I advise others looking into using SnapLogic to definitely give it a try, as it is lightweight, easy to learn and integrate, making it simple to migrate data between systems without needing to save anything into SnapLogic itself.

Improving customer support and AI capabilities will help SnapLogic excel in the future. I would rate this product 8 out of 10.

My main use case for SnapLogic is developing pipelines to transfer data from a source into our Dynamic CRM. We are thinking about using APIs and more with AI within our pipelines, and hopefully, in the future, we want to develop pipelines to write into our data warehouse once we have that implemented.

SnapLogic offers excellent features based on my experience. The snaps are very easy to work with, and it is straightforward to understand what the different kinds of snaps are available and when to use them. I specifically like SnapGPT, which has been very useful. As a solo developer at Mind, having SnapGPT to perform code checks or identify any risks within my pipeline has been invaluable.

SnapLogic has positively impacted my organization because our previous ETL tool called Scribe was going to be decommissioned, and we really needed a different way of transferring data from a source, mainly a CSV file, into CRM. Without it, we would not be able to import any of our CRM data into our Dynamics, which would prevent our CRM users from performing supporter relations, handling our supporters, and thanking them.

Regarding my experience with SnapGPT, I always ask it if my pipeline has any risk. When there are risks, such as not catching a certain data type, it lets me know that perhaps instead of returning an empty string, it should return null. It has been useful for helping me develop code. Recently, I wanted to take a string where it identifies the first part as address line one, and I wanted to search for the postcode within the long string. SnapGPT was able to give me an expression that allowed me to take part one as address line one, and because the UK postcode has a certain way of being written, it was able to identify where the postcode is within the string.

SnapLogic could improve its notification system. When a pipeline fails, the notification sometimes comes back as not very useful. I had a recent case where it just told me that a snap had failed unexpectedly without providing any reason, which is not helpful for troubleshooting, especially on the live system. To resolve this, I had to manually validate the pipeline to find the issue, which allowed me to see the data running into those individual snaps and what the error was. I would like to see if the execution can show the data flowing into those individual snaps and provide the same kind of error that I receive when validating, as that would be much more useful.

I would give SnapLogic a higher rating if the error handling and notification were more specific and user-friendly to read. Apart from that, I do not think there is anything else that I can identify.

I have been using SnapLogic for a year and three months.

In my experience, SnapLogic is very stable.

The scalability of SnapLogic is good. We develop our pipelines to be quite robust so they can be scalable in the future if users want more complex pipelines. Mind is quite early in using data, so the data we currently work with does not have that much complexity.

The customer support for SnapLogic is excellent.

SnapLogic has positively impacted my organization because our previous ETL tool called Scribe was going to be decommissioned, and we really needed a different way of transferring data from a source, mainly a CSV file, into CRM. Without it, we would not be able to import any of our CRM data into our Dynamics, which would prevent our CRM users from performing supporter relations, handling our supporters, and thanking them.

While I do not have any metrics, SnapLogic has definitely saved a lot of time because of how easy it is to implement designs for our data transfer. It has definitely saved time and streamlined many ways of working. Previously, a person would drop a file and then have to perform a lot of data manipulation within the file to push it into our Scribe process and then into CRM. SnapLogic saves a lot of users' time and reduces potential errors that could occur from a person manually updating the data.

If others are looking into using SnapLogic for Dynamics 365, my advice is that there is a significant learning curve in understanding how SnapLogic and Dynamics should communicate with each other. There is not really much documentation regarding using SnapLogic and Dynamics together, so there are quite a lot of nuances to figure out before being able to connect the mappings to the correct fields in Dynamics, using the OData bind functionality, and sometimes needing to know whether to use null or empty strings for certain fields. This knowledge would have been valuable to have at the beginning. I would rate this review an 8 out of 10.