Wir helfen Unternehmen seit 18 Jahren,
bessere Software zu finden

Integrate.io
Was ist Integrate.io?
Xplenty ist eine Datenübertragungsplattform, mit der Organisationen den Wert ihrer Daten entsperren können. Mit über 100 Integrationen können die Teams nun Insight in Marketingkampagnen-Daten, Vertriebspipeline-Statistiken, Kundendaten, Nutzungsanalyse und vieles mehr erhalten.
Wer verwendet Integrate.io?
Xplenty dient einer Vielzahl von Teams aus einer Vielzahl von Unternehmen und Branchen: Marketing, Vertrieb, BI, Produkt- und Finanzteams verwenden Xplenty, von Fortune 500-Unternehmen, kleine und mittlere Unternehmen und Startups
Du bist nicht sicher, ob Integrate.io das Richtige ist?
Mit einer beliebten Alternative vergleichen

Integrate.io
Bewertungen über Integrate.io

ETL for agile analysts
Kommentare: There are mostly two types of ETL as a service on the market: one is super easy to use and can migrate your data across services and databases but lacks transformation capabilities, while the other needs full-time data engineers to operate but tailored solutions are available programmatically. Xplenty sits in the golden middle letting analysts and engineers deploying custom transformation jobs in minutes even based on multiple data sources. The UI is intuitive but you can always use SQL to filter your sources or to create new sets in scheduled packages. Also, there are plenty of built-in functions available. Running costs are not comparable of running your own services on Heroku or Google cloud but its intuitive features save a lot of engineering hours. I would recommend Xplenty for agile teams having multiple sources of data where data analysts frequently needs custom datasets to deliver insights.
Vorteile:
- wide variety of sources and destinations - visual editor makes creating packages quick and easy - SQL transformations - great, quick, responsive support - free unlimited hours of sandbox - Slack integration
Nachteile:
- expansive for hourly jobs - error logs are not always informative - transforming JSON or other nested data is not trivial
Antwort von Integrate.io
vor 5 Jahren
Thank you for your detailed review! We appreciate your comments and will work on your listed cons. Great explanation of who will likely benefit from using Xplenty. Thanks!
In Betracht gezogene Alternativen:
No-SQL to SQL
Vorteile:
We have a complex and highly nested no-sql DB. Xplenty was the only ETL solution that allowed us get out data into tabular format for analysis
Nachteile:
None. Its been great. Haven't had any issues.
Antwort von Integrate.io
vor 5 Jahren
Glad to hear!
No code ETL pipelines
Kommentare: We stopped using xplenty when we started creating complex pipelines which required joined across data schemas.
Vorteile:
Drag and drop interface easy to use for simple pipelines. Coding skills not needed to create and setup a pipeline. Very prompt support.
Nachteile:
The same drag and drop interface becomes extremely tough to use for complicate pipelines. Deployment of pipelines quite confusing.
Highly recommend
Kommentare: My entire team loves it. Our rep actually goes out of his way to meet with us quarterly even years after set up to make sure we are aware of all the enhancements. You can use the product whether you are tech savvy or not. It is necessary for our tech stack to work.
Vorteile:
I like the ease of use. We have never ran into a problem with it. And if we have a question their support is AMAZING!! They actually teach you how to use it and don’t just send you an article. I love their business support model. More companies should do it!
Nachteile:
I actually don’t dislike anything about it. It’s the only tech solution I have no complaints about which doesn’t ever happen..
In Betracht gezogene Alternativen:
Great ETL solution with responsive technical support
Kommentare: One of the key benefits is how technically capable their support staff is. They do a great job supporting a technical product.
Vorteile:
We used Xplenty for 3 years as our ETL. It was easy and flexible to setup and was the only solution on the market that could handle MongoDB to Redshift with a very nested structure.
Nachteile:
Nothing I disliked. When we had an ETL (now on ELT) it was great and exactly what we needed.